How Does IBM Do Agile
•
19 j'aime•14,374 vues
How Does IBM Do Agile presentation that I presented at the Software Development Conference in Wellington, New Zealand at 22 March 2011.
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à How Does IBM Do Agile
Similaire à How Does IBM Do Agile (20)
Plus de Alan Kan
Plus de Alan Kan (14)
How Does IBM Do Agile
- 1. How IBM Does Agile Alan Kan – Technical Manager, IBM Rational 22/3/2011
- 2. How we used to work
- 3. How we work now
- 5. Essential attributes of Jazz Deliver real-time insight into programs, projects and resource utilization. Report Automate non-creative tasks with automated processes and workflows Automate Improve knowledge and practice maturity with an environment that develops individual and team talent. Deliver transparency of teams and projects for continuous, context-sensitive collaboration Collaborate
- 6. CLM supports effective team collaboration across lifecycle Quality Professional Product Managers Collaborative Lifecycle Management Project Team Developers Quality Management Requirements Development
- 7. The distributed Jazz Team
- 8. Our Reality – Agile Scaling Challenges Domain Complexity Straight -forward Intricate, emerging Compliance requirement Low risk Critical, audited Enterprise discipline Project focus Enterprise focus Technical complexity Homogenous Heterogeneous, legacy Flexible Rigid Organizational complexity Team size Under 10 developers 1000’s of developers Co-located Geographical distribution Global Organization distribution (outsourcing, partnerships) Collaborative Contractual Agility @ Scale
- 11. Adaptation of development practices iterative development API first end game retrospectives always have a client continuous integration community involvement new & noteworthy adaptive planning continuous testing consume your own output drive with open eyes validate reduce stress learn attract to latest transparency validate update feature teams show progress enable validate live betas feedback sign off End of iteration demos/reviews Ranked Product Backlog Burndown Stories Daily Standup independent testing exploratory testing Definition of Done
- 13. Our Rhythm endgame release M1 plan develop stabilize 4-6 weeks warm-up retrospective initial release plan decompression M2 plan develop stabilize … plan develop stabilize sign-off sign-off sign-off 4-6 weeks 4-6 weeks fix - spit & polish test fix test Retrospective New&Noteworthy End of iteration demo
- 16. Daily Scrum
- 17. Keep track of work
- 18. Collaborate with team Instant collaboration / share context Various levels of work planification Discuss/exchange work with members
- 19. Elaborate user stories Product Backlog User Stories, Epics Defects, Change Requests
- 20. Advanced source code management Easily suspend and resume work Reproduce the exact workspace of any build Work in parallel without making branch copies
- 21. Managing integrations from multiple teams
- 23. Test management
- 24. Trace tests to user stories CLM Traceability Queries Linked Test Case
- 26. Project status at a glance Burndown charts Various project health dashboards Team communication
- 29. IBM becomes more Agile 8500+ users
- 30. Learn more on www.Jazz.net
Notes de l'éditeur
- Show what’s been done – roles. Process adaptations: PMC within Rational to ensure project funnel IBM product delivery process. Print them on DVDs. Agile
- Common agile practices: iterative, reflect, adapt, incremental, feedback Practices inspired by agile practices, scrum, xp, some custom ones, that work for us
- Distributed development: planning an iteration takes longer
- Chickens – give feedback, also support dev team (pigs) doing the complete job. Light adaptation – in scrum – architects on the pigs side usually. This time we have them in chickens becoz ibm architects get info from customers, present to customers, very customer focused. At the same time building things.
- 2 reasons for these slides – 1. use terminology well know. 2. trying to apply things as they should. Less developers asking for strange things, etc. apply as much as agile as poosible. It’s a big change for IBM, but we are willing to adapt agile, not mixture. We’re doing what we can to become more agile. For a while, we mixed 2 teams, so all coming from RTCz and RTCp. Originally 2 project owners. Now have just one enterpirse extension team. Still have 2 project owners. To ensure actual release. In 3.0.1 only Guy -> from NZ. Guy Slade.