Using RUP As A Scaling Framework For Scrum
•Télécharger en tant que PPT, PDF•
15 j'aime•3,497 vues
This talk was presented for the first time at Agile 2008 in Toronto
![Where to go for the presentation ,[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
En vedette
En vedette (17)
Plus de Mike Cottmeyer
Plus de Mike Cottmeyer (20)
Dernier
Dernier (20)
Using RUP As A Scaling Framework For Scrum
- 1. Using the Unified Process as a Scaling Framework for Scrum
- 7. If you are part of a small team running agile on whiteboards…
- 10. Most teams are looking for advice that resonates
- 13. What is a product of products? Payments Services Risk Services Business Intelligence Corporate Financials Online Banking X X X X Phone Banking X X X Payment Processing X X Remittance Processing X X
- 14. Complex product architecture Partner Communication Payments Risk Bus Intel/ Reporting Business Intelligence Corporate Financials
- 17. Agile offers only partial coverage Mike Griffiths, Leading Answers http://www.leadinganswers.com
- 18. Teams are trying to find a way to get the value of agile …
- 19. … but don’t fit the agile profile
- 21. Devise and execute the best processes possible based on their skills, experience , and the situation in which they find themselves
- 30. Most teams are making tradeoffs, lets be intentional about managing those tradeoffs and understanding the risks
- 33. Bad process is bad process no matter what methodology you are using
- 36. Do the simplest thing that could possibly work
- 42. What UP stuff will definitely go away?
- 43. Introduce elements of UP that reduce risk
- 46. UP phases explained Construction Elaboration Inception Transition Lifecycle Objective Milestone Lifecycle Architecture Milestone Initial Operational Capability Milestone Product Release Milestone Are the technical risks mitigated? Are the logistical risks mitigated? Are the business risks mitigated? Are we really ready to ship a complete robust product to market?
- 47. Effort and duration by phase Inception Elaboration Construction Transition Inception Elaboration Construction Transition Effort 5% 20% 65% 10% Schedule 10% 30% 50% 10%
- 48. A more Agile representation? Internal Release* Iteration Zero Iteration H Iteration 1 Iteration 2 Iteration 3
- 49. Phases are time boxes for dealing with risk
- 53. Collaborative Model Project Manager
- 58. Scrum of Scrums Epic/ System Perspective Feature/ Subsystem Perspective Story/ Component/ Design Perspective
- 59. Business Level Use Case
- 61. Primary and alternate flows
- 63. Design level use case
- 65. Data
- 77. Keep it simple