AGILE -- YOU CAN GO BIG -- HOW TO DO IT WELL WITH STEVE ADOLPH!
•Transferir como PPTX, PDF•
1 gostou•521 visualizações
Can Agile be adapted to large scale projects? We know it works well in small environments where project ownership is clearly defined, timelines and scope are also well-defined. What happens when there are multiple teams across time zones and complex needs change over the course of the project? Steve Adolph, Agile consultant and President of Development Knowledge provides acute insights that are both entertaining and educational!
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (19)
Semelhante a AGILE -- YOU CAN GO BIG -- HOW TO DO IT WELL WITH STEVE ADOLPH!
Semelhante a AGILE -- YOU CAN GO BIG -- HOW TO DO IT WELL WITH STEVE ADOLPH! (20)
Mais de XBOSoft
Mais de XBOSoft (20)
Último
Último (20)
AGILE -- YOU CAN GO BIG -- HOW TO DO IT WELL WITH STEVE ADOLPH!
- 1. WELCOME XBOSOFT Software Quality Knowledge Center is proud to partner with and introduce Steve Adolph President Development Knowledge
- 2. Go Big with Agile –The Good, The Bad and The Beautiful An Overview Steve Adolph & Jan Princen
- 3. Housekeeping • Everyone is muted except the speaker • Questions welcome! Please post them using the gotowebinar control on the right side of your screen • General Q & A at the end of the webinar • Look for updates on the webinar recording and other exciting news from Xbosoft and Development Knowledge
- 4. XBOSoft Founded in 2006 Dedicated to software testing excellence Software QA consulting Software testing services Global presence N. America --Santa Clara, CA Asia – Beijing Europe – Oslo and Amsterdam
- 5. Development Knowledge Founded 2014 Established with a mission to provide best-in-class eLearning content for software development process improvement To set the standard that e-learning is not a cheaper alternative to in-class learning but a superior one
- 6. About the Speakers Steve Adolph President Development Knowledge steve@developmentknowledge.com Jan Princen Managing Director XBOSoft Jan.princen@xbosoft.com
- 7. The World Runs On Software Copyright (c) 2014 Development Knowledge Technologies Inc
- 8. But Our Methodologies Have Not Kept Up with Demand Copyright (c) 2014 Development Knowledge Technologies Inc
- 9. We’ve had a lot of hope for Agile And some success with Agile methodologies at the team level… Version 7 9
- 10. Cinderella Scrum Copyright (c) 2014 Development Knowledge Technologies Inc
- 11. But this is your project… Photo by Jose Luis Ruiz 11
- 12. ….but what if you are building this? Copyright (c) 2014 Development Knowledge Technologies Inc
- 13. Bigger Projects Require Bigger Methodologies - - Alistair Cockburn Copyright (c) 2014 Development Knowledge Technologies Inc
- 14. “If only a few drivers cross a large parking lot at night, when there are no other cars, it doesn't matter where they drive. The few drivers can arrange to avoid each other. As the number of cars moving through the parking lot increases, eventually it does matter. With increasing number of drivers, it becomes more important that they establish and follow conventions about parking, driving lanes, and stop signs” - Wayne Stevens 14
- 16. The Scaling Up Approach Copyright (c) 2009 WSA Consulting Inc Version 7 16
- 17. Scaling Up Agile Bigger Time Box Copyright (c) 2014 Development Knowledge Technologies Inc
- 18. We need more people Copyright (c) 2014 Development Knowledge Technologies Inc
- 19. Scrum Guidance for Scaling Copyright (c) 2014 Development Knowledge Technologies Inc
- 20. We Need a Bigger Story Copyright (c) 2014 Development Knowledge Technologies Inc
- 21. Story Cards? Copyright (c) 2014 Development Knowledge Technologies Inc
- 22. Epics, Features, and Stories Backlog Item Realized by Realized by Epic 0,1 1..* Feature UML Model Courtesy Dean Leffingwell Copyright (c) 2014 Development Knowledge Technologies Inc 0,1 1..* Story
- 23. Epics, Features, and Stories AND Tests Backlog Item Non Functional Requirements Constrained by System Quality Tests Realized by Epic 0,1 Realized by Feature 1..* Feature Acceptance UML Model Courtesy Tests Dean Leffingwell Story 0,1 1..* Story Acceptance Tests Copyright (c) 2014 Development Knowledge Technologies Inc
- 24. Epics, Features, Stories Copyright (c) 2014 Development Knowledge Technologies Inc
- 25. Team Backlog Team Backlog Program Backlog Team Backlog Copyright (c) 2014 Development Knowledge Technologies Inc
- 26. We need a bigger time box Copyright (c) 2014 Development Knowledge Technologies Inc
- 27. “Releases” or “PSIs” Extended Range Planning: PSI Roadmap PSI 1 Vision PSI 2 Mid Range Planning: PSI of Sprints ITERATION 1 ITERATION 2 ITERATION 3 ITERATION 4 Copyright (c) 2014 Development Knowledge Technologies Inc PSI 3
- 28. A Roadmap of Releases PSI 1 PSI 2 PSI 3 Vision Theme: Prove “?” For X, this Proof release provides <what value> Key Features: 1. Feature A 2. Feature B 3. Feature C Theme: Trial with critical existing customers Theme: Upgrade Alpha and expand to new customers For <who>, this Alpha release provides <what value> For <who>, this Beta release provides <what value> Key Features: 4. Feature B’ 5. Feature C’ 6. Feature D Key Features: 7. Feature B’’ 8. Feature D’ 9. Feature E Copyright (c) 2014 Development Knowledge Technologies Inc
- 29. Synchronize Teams Copyright (c) 2014 Development Knowledge Technologies Inc
- 30. The Program Level PSI 1 Copyright (c) 2014 Development Knowledge Technologies Inc PSI 2
- 31. the Matrix Analysts Architects Copyright (c) 2014 Development Knowledge Technologies Inc Developers Testers
- 32. Escape the Matrix Bring the Work to the Team Copyright (c) 2014 Development Knowledge Technologies Inc
- 33. Feedback, Inspect and Adapt Sprint Goals Copyright (c) 2014 Development Knowledge Technologies Inc Inspect and Adapt Retrospectives PSI 2 PSI 1
- 34. So Where Is the Test Engineer? When do we test? ? Copyright (c) 2014 Development Knowledge Technologies Inc
- 35. With Every Team, All the Time – Continuous Testing Continuous Release PSI 1 Copyright (c) 2014 Development Knowledge Technologies Inc Inspect and Adapt Test, test, test, test, PSI 2
- 36. Hardening: A Remedial Action PSI 2 Copyright (c) 2014 Development Knowledge Technologies Inc
- 37. Release Planning Meeting The Release Planning Meeting is the “pacemaker” of the Agile enterprise. Two days every 8-12 weeks Everyone attends in person if at all possible Copyright (c) 2014 Development Knowledge Technologies Inc
- 38. Copyright (c) 2014 Development Knowledge Technologies Inc
- 39. Questions
- 40. Follow: @XBOSoft Questions: services@xbosoft.com 408-350-0508 Follow: #agilevancouver Questions:
- 41. Thank You! Steve Adolph President Development Knowledge steve@developmentknowledge.com Jan Princen Managing Director XBOSoft Jan.princen@xbosoft.com
Notas do Editor
- We thought the agile methods would a possibllity, but do not provide guidance for large scale projects….
- * Jennitta Andrea is credited with the term Cinderalla project. It is the ideal project suited for agile software development, the agile sweet spot as others call it. Small co-located teamGeneric skillsJava or smalltalk basedExpert engaged customer at your beck and callClear terms of referenceShort duration ( <12 months)Web based, user centricDedicated on-site customer or subject matter expert (SME)Clear project visionAbility to articulate the visionDedicated team members (not shared with other projects)Green field* - Jennitta Andrea Better Software Sept 2005These are the projects most people write about, talk about and study.
- Photo by Jose Luis RuizCompeting customer demands (if you lucky to even have them return your phone calls)Distributed teams (half of whom do not speak the same language) across multiple non ovelappingtimezonesStaff often working on multiple projectsComplex ApplicationCorporate ArchitectureHigh level of staff specializationLegacy systemLarge Scale, Ultra Large ScaleConstraints:Corporate project governance policiesQuality standardsIt does not sit in the sweet spot,
- Sculpting certainly requires more skill…If any of us besides a skilled sculptor started hammering on this marble we’re likely to leave it alone – too scared to break it. Only in the hands of an expert will it become a think of beauty without becoming groteseque or a pile of rubble on the floor.Problem: RUP is a large comprehensive process framework that required a knowledgeable software process engineer to tailor itResult: practices suitable for a national air traffic control system are often used for small team projectsNet result: Most developer’s ignore the process
- Be agile in your method design, Start with a minimal process, and scale up“Demand Scaling”Lower cognitive load on process designersDon’t try to anticipate every contingency your process may have to cope with….
- Compare little story to feature or epic,
- But even a fairy godmother will have difficulty creating a backlog for a large complex engineering project:John Deere series 8000 tractor goes here complex system of systems….planning horizon is longer than a sprint, and features are not described in increments of two or three days worth of work
- Epic, many other terms used to describe epics, Features, themes, sagas, tomes….
- Slide showing how product backlog feeds team backlogs…..Need to emphasize what the significance of this is – highlights bring the work to the team. Use to form teams around projects, now they are formed around a backlog – maybe back to basic scrum. Something which is exploited in SAFe, no 50% team members…
- Sprint versus release
- Slide needs to be updated to have product backlog and tam backlogPredictableManage dependencies
- Slide needs to be updated to have product backlog and tam backlogPredictableManage dependencies
- Slide needs to be updated to have product backlog and tam backlogPredictableManage dependencies
- Caboose at the end of the flow???
- Slide needs to be updated to have product backlog and tam backlogPredictableManage dependencies
- Sprint planning in the large….