Story Mapping for Agile Software Development
•
4 j'aime•1,961 vues
The document discusses story mapping, which is a technique for planning software releases. Unlike traditional user story backlogs, story maps make the workflow or value chain visible, show relationships between larger stories and child stories, and provide context for prioritization. They also allow planning of releases as complete slices of functionality. The document provides an example of creating a story map, which involves defining personas, mapping goals and activities, and progressively adding more details like subtasks and functional decomposition.
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à Story Mapping for Agile Software Development
Similaire à Story Mapping for Agile Software Development (20)
Plus de Nikita Filippov
Plus de Nikita Filippov (20)
Story Mapping for Agile Software Development
- 1. STORY MAPPING Nikita Filippov using some Jeff's Pa6on Content © 2010
- 2. Agenda • Me • UserStory & Backlog issues • StoryMapping – Personas – Release Slice Nikita Filippov using some Jeff's Pa6on Content © 2010
- 3. Nikita Filippov • ScrumTrek • Agile Coach • Managing Partner • My Experience • WebDev, Product Manager, Process Engineer
- 4. Disclaimer & Ground Rules • Welcome to Russian English cKlass – If you don’t understand me, ask in russian J • Right hand rule – See my raised hand – Rise the hand – Shut up – Make it peer to peer – Listen to me Nikita Filippov using some Jeff's Pa6on Content © 2010
- 5. Incremental Delivery 1 2 3 4 5
- 6. Incremental & IteraUve 1 2 3 4 5
- 7. Warm UP • Describe your acUviUes – StarUng from you waked up and finish when you get to Agile Saturday – Group of 5-‐6 – One AcUvity per SUcker Nikita Filippov using some Jeff's Pa6on Content © 2010
- 8. Concept acUvity task task task task task Nikita Filippov using some Jeff's Pa6on Content © 2010 8
- 9. Concept manage email acUvity read message send prioriUze message message delete message place create message task folder in folder Nikita Filippov using some Jeff's Pa6on Content © 2010 9
- 10. User Story • As a <user role>, I want <goal> so that <reason> Nikita Filippov using some Jeff's Pa6on Content © 2010
- 11. Story Mapping Unlike typical user story backlogs, Story Maps: – make visible the workflow or value chain – show the relaUonships of larger stories to their child stories – provide a useful context for prioriUzaUon – Plan releases in complete and valuable slices of funcUonality. Nikita Filippov using some Jeff's Pa6on Content © 2010
- 12. Vision: Alex Bookstore Problem • Alex Krivitsky has a Book store of Foreign Literature • Now he has so many books , so he needs some soeware to organize it • He likes touchscreen interface © Nikita Filippov, 2010 Using Jeff Pa6on Content
- 13. Philipp Finance Officer Type: Customer § CFO § Age: 30 § Soft: Win7, Invision & Cognos, Uses Corporate Laptop Problems Values • Philip can’t track • Cheap SoluUons operaUonal expenses • Mobility • Can’t access to sales data • Actuality of data remotely
- 14. Make 3 personas
- 15. StoryMap: Map Goals / AcUviUes • Tell a big story of the product by starUng with the major user acUviUes Mental Pa6ern: Our persona can Example: <do something > with system in global Work with Reports Nikita Filippov using some Jeff's Pa6on Content © 2010
- 16. Nikita Filippov using some Jeff's Pa6on Content © 2010
- 17. Nikita Filippov using some Jeff's Pa6on Content © 2010
- 18. Simple story • Add simple simplest story(task) in every acUvity • Move from lee to right Example: See list of Mental Model: And then persona can <do reports some task> Nikita Filippov using some Jeff's Pa6on Content © 2010
- 19. Bare what is essential functionality necessary to demonstrate the simplest use of the feature? Necessity Capability, what would make this feature useful in more situations? What would allow the feature to be used in alternative Flexibility ways? Safety what would make this feature safer for me to use for the user or other stakeholders? These are characteristics that help prevent errors or validate data to prevent bad information from entering the system. Usability, what would make this feature more desirable to use? This includes adjustments to improve usability, visual Performance, and interaction design improvements to esthetic Sex Appeal appeal, and improvements that help users do their work faster including architectural improvements or 19 features such as short cuts or speed keys.
- 20. Bare Necessity Example: A form with only necessary fields and no validaFon Capability & Flexibility Example: a form with opFonal fields, date lookup tools, input translaFon on dates Safety Example: input validaFon, enforcement of business rules such as credit card validaFon Usability, Performance, Sex Appeal Example: auto-‐compleFon, sexy visual design, speed keys
- 21. Nikita Filippov using some Jeff's Pa6on Content © 2010
- 22. Add Subtasks, Details, Func. DecomposiUon Example: • As details emerge in conversaUon, trap them under their associated task cards filter for User • Record details so they re not lost, areports list of nd so those who you re working with know that Nikita Filippov using some Jeff's Pyou re listening a6on Content © 2010
- 23. J Проблемы ~~~~~ Ценности ~~~~~ Adding Details ~~~~~ ~~~~~ ~~~~~ ~~~~~ ~~~~~ ~~~~~ Goal Goal Goal Bare Necessity Safety, Usability Capability & Flexibility , etc… Nikita Filippov using some Jeff's Pa6on Content © 2010
- 24. Nikita Filippov using some Jeff's Pa6on Content © 2010
- 25. Thanks • Skype:nikita_filippov • Twi6er: @nfilippov • h6p://Scrumtrek.ru Nikita Filippov using some Jeff's Pa6on Content © 2010