Responsibility | Tasks | Role | Delivery |
Capacity planning | 1. Current user pattern/distribution 2. Gap analysis 3. Predict trend of usage 4. Top slow transactions 5. Top usage of transactions | QA lead, Performance QA(owner) PM, OPS(supportive) SDM, TL(consultant) | Access log analysis result RFP distribution pattern |
Performance Environment Setup | 1. Setup Performance environment 2. Data preparation 3. Server configuration | SCM/Dev (owner) Performance QA (supportive) | Testable performance environment |
Performance test planning and design | 1. Performance test strategy design 2. Performance testing scripts/scenario design 3. Keep performance test scripts/ load distribution update to date | Performance QA(owner) Performance Dev(supportive) SDM, TL, QA lead(consultant) | Performance test scripts/ scenarios |
Code review and design inspection | 1. code review and Performance inspection checklist | Performance Dev , TL(owner) Performance QA(supportive) Arch(consultant) | Code review retro |
Performance testing Execution | 1. User-story based performance test 2. Weekly performance test 3. Release performance testing 4. End-end performance test 5. Performance initiatives 6. Performance test report | Performance QA(owner) Performance Dev(supportive) | Performance test result report |
Performance result analysis | 1. Server log issues analysis 2. Performance test result analysis 3. Conclusion of performance Grade and suggestion of further investigation | Performance Dev(owner) Performance QA(supportive) | Identify any potential Performance bottlenecks Escalate Performance issues to the team |
Performance improvement planning | 1. making follow up plan for escalated performance issues | SDM, TL, QA lead(owner) Performance QA/Dev(supportive) | Create tech user stories for each performance issue Triage the priority of each performance user story |
Performance tuning | 1. Java back-end performance tuning 2. DB tuning 3. Front-end performance tuning 4. Performance Validation | SDM, TL, Dev (owner) Performance QA(supportive) | Tuning analysis summary Performance improvement comparison result Code review Check-in code into new release |
Production Performance issues Follow up | 1. Log performance issue in Rally 2. Server log analysis 3. Reproduce performance issue on local 4. Find the root cause of bottleneck | Performance Dev(owner) Performance QA(supportive) | Performance issue analysis result Reproduce suggestions |
Wednesday, December 23, 2009
Performance engineering internal group(team) responsibility
Here is a draft of internal performance group(team) responsibility chart in my mind, so much things to do, we need to prioritize each section better to maximum its value :
Subscribe to:
Post Comments (Atom)
This comment has been removed by a blog administrator.
ReplyDelete