Ravit Danino HP - Roles and Collaboration in Agile


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ravit Danino HP - Roles and Collaboration in Agile

  1. 1. Roles and Collaborationin AgileDanino Ravit – Chief functional architect HP ALM managementDate: 11.4.2010©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
  2. 2. So did Agile really changeOUR world ? Apparently it did
  3. 3. So , What has changed ?
  4. 4. Break the wallDeveloper Business QA Docs Analyst
  5. 5. Break the walls The whole team works along the whole sprint !
  6. 6. “ 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 LasordaLos Angeles Dodgers baseball team ABC Company
  7. 7. 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
  8. 8. Incremental delivery Iteration 2 Iteration 1 Iteration 3 Iteration 4
  9. 9. Personas role through the lifecycle Waterfall Security ? Business Developer Developer PCOE Analyst Tester Requirements Design Implementation Verification Maintenance Project Manager
  10. 10. Personas role through the lifecycleAgile Program Managers Customer Backlog Sprint Planning Retrospective Reporting PCOE Agile Product Eng owner Validations Developers QA Business Eng Analyst
  11. 11. Collaboration points Analyze Plan next Design iterations New requirements Feedback Coding Incremental Testing Delivery
  12. 12. AnalyzeIteration 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
  13. 13. AnalyzeIteration coding Plan next Design iterations• Coffee testing Feedback Coding• Architects team Incremental• Nightly build Delivery Testing• Scheduled end to end testing• Monster Click
  14. 14. AnalyzeIteration handoff Plan next Design iterations Feedback Coding• Sanity handoff Incremental• Demo Delivery Testing• Retrospective• Move from management to leadership
  15. 15. Customers become a key enablerWe need to be creative with the methods wechoose to involve our customers• Internal use of the software• Design Partner• Public Beta & Beta
  16. 16. Roles andResponsibilities
  17. 17. Roles definition – Whats changing ?
  18. 18. Ideal team structure
  19. 19. Small agile team structure Developers Product Owners Project Owners Tester SME Tech Experts Testers ( security / performance )
  20. 20. Large agile team structure Project Owners Team Product Owners Team Architecture Team Developers Domain Expert Testers Tech Experts ( security / performance )
  21. 21. 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 ReviewProductOwners 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. 23. Resistance?• How will I maintain my role ?• How will I test the partial delivery ?• How will I know where the red line is ?
  24. 24. 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)
  25. 25. 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 andsolve them as a team
  26. 26. Thank you !