Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Agility with Use Cases when User Stories aren't enough
Semelhante a Agility with Use Cases when User Stories aren't enough (20)
Mais de DiVetro
Mais de DiVetro (7)
Último
Último (20)
Agility with Use Cases when User Stories aren't enough
- 1. Creating winning teams. www.ivarjacobson.com Agility with Use Cases When User Stories Aren’t Enough Graham Marsh, Ivar Jacobson International Dennis Geluk, DiVetro
- 2. Creating winning teams. Use Case History 1969 2016Leading the industry for 45 years • Coaching, training and consulting in IT system development best practices • Focus on agile transformation and self sustainability • Practice agnostic, solution based on engagement requirements • Accelerating and de-risking change • “Creating winning teams” through skills and knowledge transfer • Helping organisations do it Better, Faster, Cheaper, Happier ‘86 ‘04
- 3. Creating winning teams. Context is everything – especially when things scale
- 4. Creating winning teams. Context is everything – especially when things scale NFR’s
- 5. Creating winning teams. Driving development with slices Start of use case End of use case Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Alt 1 Alt 2 Alt 3 Alt 4 1 Use Case Many slices…
- 6. Creating winning teams. Customer: Dutch Railways • Dutch Public transportation • 24 x 7 x 365 • 5200 trains a day • 600.000 passengers a day • 11.000 FTE
- 7. Creating winning teams. The challenge • Replacement of (obsolete) handheld device by mobile (phone) apps • Transformation from RUP based development process to Scrum • New technology
- 8. Creating winning teams. Assignment Ivar Jacobson International & DiVetro • Feed the App factory with user stories • Ensure up-to-date system documentation (use cases) • Keep the big picture and scope in mind • Do it fast! Develop a new agile way of working within the current process
- 9. Creating winning teams. Starting point TEAM Developers, Testers, Scrum master (external) PO (Dutch Railways) UX designer (Dutch Railways) Analyst (DiVetro) Backend team – to manage all the backend systems WORK Combination of Scrum and Kanban REQUIREMENTS Needs & Features (Vision) Initial Use Case Model Some use case narratives with lots of colours OPPORTUNITY Clear business case STAKEHOLDERS Over 40
- 10. Creating winning teams. From Features to Epic (stories) • Focus on what does the user really need? • Use “Story” template to record needs • Add “Acceptance criteria” to each Epic story • Create product backlog (with epics stories) • Prioritize the backlog • Most Epics were too big to be handled by the team E01 Call relevant generic contacts E02 Call location based contacts E03 Create a list of favorite numbers E08 Manage contact information remotely
- 11. Creating winning teams. Align Epics and Use Cases Actor 01 (from Actors) Actor 02 (from Actors) Actor 03 (from Actors) (from Heavy Molecule) Use Case 01 (from Heavy Molecule) Use Case 02 (from Heavy Molecule) Use Case 03 (from Heavy Molecule) Use Case 04 Actor 06 (from Actors) Actor 05 (from Actors) «include» E01 Call relevant generic contacts E02 Call location based contacts E03 Create a list of favorite numbers Divide Epics into stories and relate them to a Use Case Divide Use Cases into slices and place them under an Epic
- 12. Creating winning teams. Lessons learned • Slicing use cases (to user stories) effectively is an art • Don’t rely on paper only • Don’t confuse the team with future changes
- 13. Creating winning teams. Result • Aligned process that supports the App factory • Up-to-date system documentation after each sprint • Best practice project in agile working
- 14. Creating winning teams. Thank You – Learn More Dutch Railways Case Study Use-Case 2.0 ebooks practicelibrary.ivarjacobson. com Visit our stand to request a copy!
Notas do Editor
- OUTLINE (Conference side) In some cases user stories are enough, but not when the number of user stories begins to grow, or when you develop enterprise systems for banks, insurance, telecom operations, defense or other large scale or regulated industries. The answer is Use-Case 2.0 – the agile way of doing use cases. Use-Case 2.0 ‘slices-up’ use cases to provide an iterative agile approach that can provide just-enough information as needed or can be zoomed-in for more detail. This session explores how Dutch Railways kept development on track and delivered the right level at the right time by applying Use-Case 2.0 with help from Ivar Jacobson International and DiVetro.
- Lots of people in the organisation that have been on the pre-iji UP Journey
- Simple picture…. Loads of slices all over the screen…. One simple build puts them into use case context
- Simple picture…. Loads of slices all over the screen…. One simple build puts them into use case context
- NS had to deal with a variety of challenges. Besides the one on the slide alignment of business was also an issue Replacement of (obsolete) handheld device by mobile (phone) apps Mission critical software “No” slack in the deadline (hardware not supported any more) Transformation from RUP based development process to Scrum Development done by “third party” App factory RUP based requirements vs user stories to ran the App factory New technology Azure, Airwatch, Xamarin Reusable services (multiple hardware devices)
- Use cases are too big for the factory Mission critical software so proper documentation is needed More than one project (TimTim, EKT etc…) We had to jump on a moving train
- Slicing use cases (to user stories) effectively is an art involving the whole team helps! Get everyone on the same page Don’t rely on paper only Use alignment workshops! Don’t confuse the team with future changes Only specify what is needed in the sprint! – Don’t tell what’s coming down the line.
- PRE-LI-MI-NAIRY We created a “bench mark” project