1. Roles and Collaboration
in Agile
Danino Ravit – Chief functional architect HP ALM management
Date: 11.4.2010
©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

3. So did Agile really change
OUR world ?
Apparently it did

4. So , What has changed ?

5. Break the wall
Developer Business
QA Docs
Analyst

6. Break the walls
The whole team
works along the
whole sprint !

7. “ My responsibility is to get my twenty five guys
playing for the name on their front of their shirt
and not the one on their back” (LaFasto and
Larson 2011,100)
Tommy Lasorda
Los Angeles Dodgers baseball team ABC Company

8. Whole team
• The team should work as a unit and not as a set
of individuals
• renew the team members commitment
• Not everybody are motivated in the same leve
• Explain to each player the relevance to the project goal

9. Incremental delivery
Iteration 2
Iteration 1
Iteration 3
Iteration 4

10. Personas role through the lifecycle
Waterfall Security ?
Business Developer Developer PCOE
Analyst
Tester
Requirements Design Implementation Verification Maintenance
Project
Manager

11. Personas role through the lifecycle
Agile
Program Managers
Customer
Backlog Sprint
Planning
Retrospective
Reporting
PCOE Agile Product
Eng owner
Validations
Developers
QA Business
Eng Analyst

12. Collaboration points
Analyze
Plan next
Design
iterations
New
requirements
Feedback Coding
Incremental
Testing
Delivery

13. Analyze
Iteration planning Plan next
iterations
Design
Feedback Coding
• Joint planning Incremental
Delivery
Testing
• Acceptance test as part of planning
• Manage user stories versus tasks
Common language between Dev, QA & Business

14. Analyze
Iteration coding
Plan next
Design
iterations
• Coffee testing Feedback Coding
• Architects team
Incremental
• Nightly build Delivery
Testing
• Scheduled end to end testing
• Monster Click

15. Analyze
Iteration handoff
Plan next
Design
iterations
Feedback Coding
• Sanity handoff
Incremental
• Demo Delivery
Testing
• Retrospective
• Move from management to leadership

16. Customers become a key enabler
We need to be creative with the methods we
choose to involve our customers
• Internal use of the software
• Design Partner
• Public Beta & Beta

17. Roles and
Responsibilities

18. Roles definition – What's changing ?

19. Ideal team structure

20. Small agile team structure
Developers Product Owners
Project Owners
Tester
SME Tech Experts
Testers
( security / performance )

21. Large agile team structure
Project Owners Team Product Owners Team Architecture Team
Developers
Domain Expert Testers Tech Experts
( security / performance )

22. Product Backlog Persona
involvement
Performance
Architecture, Design
Guidelines & Code Review
Measuring , Testing , Tuning
Continues Performance
Integration test
User Acceptance Test Specification
Threat Assessment, secure
Security
Architecture, Design Penetration Test
Backlog discussion & prioritization
Guidelines & Code Review
Product
Owners
Build
Build
User Acceptance Test
Specification
Tester
Automate Test Automate Test
Developer
Design , Code , review , unit / component test Design , Code , review , unit /
component test

23. CHANGE WE BELIEVE IN
?

24. Resistance?
• How will I maintain my role ?
• How will I test the partial delivery ?
• How will I know where the red line is ?

25. How can we overcome the resistance
?
• Start with small project
• Engage the management level
• Empower the team as a team
• Fast feedback
• Add fun ( gaming dynamics)

26. Resistance is an analogy to pain
• A pain something in the body is wrong .
• The resistance something in the
process is not working correctly .
use it to understand the problems and
solve them as a team

27. Thank you !