Webinar presentation http://www.returnonintelligence.ru/webinars/shared-position-project-testing-analysis/

1. Core Systems Transformation Solutions
2013
Shared position in a project:
testing and analysis
Polina Vorobieva

2. 1
Agenda
• Resource allocation
• Testing phase
• Analysis phase
• Common responsibilities
• Difference in points of view
• Shared position: pros and cons

3. 2
Resource allocation: Example
• Team
 Manager
 2 developers and Tech Lead
 2 testers and Test Lead
 Analyst
• PBL
Story Release Status
Story 7 1 Done
Story 8 1 Sprint 100 (implementation)
Story 9 1 Sprint 100 (implementation)
Story 10 2 Sprint 100 (analysis)
Story 11 2 No requirements
Story 12 2 No requirements

4. 3
Resource allocation: Example

5. 4
Resource allocation: Example
Story Release Status
Story 10 2 Sprint 101 (implementation)
Story 11 2 Sprint 101 (analysis)
Story 12 2 Sprint 101 (analysis)
Story 13 2 Sprint 101 (analysis)

6. 5
Resource allocation: Statistics
Stage small/big story, h Average, h
Analysis 18-92 35-50
High Level Design 10-36 25-30
Implementation (Coding and Testing) 15-60 20-60
Analysi
s35 % Design
20 %
Code &
Test
45%
Small story
Analysi
s45 %
Design
30 %
Code &
Test
25%
Big story

7. 6
Resource allocation: RISKS
• Diseases
• Vacations
• Attrition
• Ramp down
• Project demands
• Demotivation

8. 7
Resource allocation: progress
• Growth
o Lead/Manager
o Improve technical skills
o Improve analytical skills

9. 8
Testing phase
• What are the Tester’s responsibilities?
o Requirements analysis
o Test planning
o Test development
o Test execution
o Test result analysis
o Defect Tracking

10. 9
Analysis phase
• What are the Analyst’s responsibilities?
o Requirements planning and management
o Requirements communication and analysis
o Solution assessment and validation
o Document the requirements
o Test cases review
o Improvements of process

11. 10
Common responsibilities
• Requirements analysis/Requirements testing
• The main question: How it should work?
(Output for Analyst and Input for Tester)
• Collaboration:
• Communication with Customer
• Determination of Customer needs
• Requirements clarification
• Integration (and other non-functional testing)
• Acceptance testing/UAT team
• Knowledge sharing

12. 11
Difference in points of view
• Paint the rose

13. 12
Difference in points of view
• Feasibility determination
• Solution for implementation
 Impact assessment
 Analysis of all options
 Responsibility
 ‘Common language’
 Effective communication
 Identification of Customer’s needs
 Increase Customer’s satisfaction

14. 13
Difference in points of view
• Requirements analysis
• Test approach
• Test scenario/cases
• Test execution

15. 14
Difference in points of view
• Main items to pay attention for Tester:
o Technical aspects, details of implementation
o Domain knowledge
o Assess of impact

16. 15
Difference in points of view
Analyst Tester
What for?
Can we do it?
How should we do it?
Can we propose anything? What are the requirements?
What is the potential impact for the
whole system?
How was it done?
What is the impact?
How do we test it?
What is the impact of each issue? How many issues do we have?

17. 16
Shared positions
• Pros
 Interchangeability
 Sharing knowledge
 Team work
 Responsibility
 Growth
 Motivation
 Risk reduction
 Effectiveness
• Cons
 Individual
 Switch between tasks
• Issues
 High load
 Possibility of miscommunication

18. 17
Conclusion
• Benefits if applicable

19. 18
Questions