WebCamp: Project Management Day: Управление требованиями в Agile: как это происходит в реальном мире - Прихнич Алена
4 likes786 views
The document discusses the changes in requirements management within agile methodologies compared to traditional methods like waterfall, highlighting that requirements have become smaller, less precise, and more adaptable. It outlines the agile work breakdown structure, emphasizing the use of themes, epics, user stories, and prioritization techniques such as the MoSCoW method. Additionally, it touches on the importance of user stories for understanding product functionality and encourages organizations to engage in continuous discussions throughout the development process.
![Card
As a [user role] I want [activity] so I can [benefit]
User role – who (new user, guest, job-seeker)?
Activity – functionality, action of the system,
what?
Benefit – value for the end-user, why?](https://image.slidesharecdn.com/4-140915045349-phpapp01/85/WebCamp-Project-Management-Day-Agile-16-320.jpg)
WebCamp: Project Management Day: Управление требованиями в Agile: как это происходит в реальном мире - Прихнич Алена
- 1. Requirements management In Agile: What’s happening in real world?
- 2. Let’s introduce ourselves ;) Helen Prykhnych" Co-founder & trainer @ E5 IC Agile certified professional In past – Returns Operation Department Manager, Project Manager, Manager of Kyiv office of IT outsourcing company. Last project – opening office of outsourcing company in Kyiv.
- 3. Prize for the most interesting question ;)
- 4. How are requirements changed in Agile compared with other methodoligies (RUP, Waterfall)? • Became smaller. • Became less precise. • Less time for elaborating them. • Easy to change or extend. • Now they encourage discussions instead of describing the final state.
- 5. Vision: answers the big questions for the system 1. What problem does this particular solution solve? 2. What features and benefits does it provide? 3. For whom does it provide it? 4. What performance, reliability, platforms, standards and so on, does it deliver?
- 6. Work breakdown in Agile Initial description (Vision) Theme Epic User Story
- 7. Task, User Story, Epic, Theme
- 8. Start with Themes & Epics Epic 1 Epic 2 Epic 3 Epic 4 Epic 5 Epic 6 Theme 1 Theme 2
- 9. Epic 1 Epic 2 Epic 3 Epic 4 Set priorities Epic 6 Epic 2 Epic 1 Epic 4 Epic 3 Epic 5 Epic 6 Epic 5
- 10. Epic 1 Epic 2 Epic 3 Epic 4 Slice the cake US1 US2 US4 US5 US6 US7 US8 Epic 1 Epic 6 Epic 2 Epic 1 Epic 4 Epic 3 Epic 5 Epic 4 Epic 3 Epic 5 Epic 5 Epic 6
- 11. Just In Time TASKS STORY STORY/EPIC EPIC THEME (Iteration in play) Closest Iteration Final Iteration
- 12. Prioritization Based on Value using MoSCoW: • M - MUST • S - SHOULD • C - COULD • W - WON'T (but would like)
- 13. Why do we prioritize?
- 14. Agile Analysis Proces in Time flow 14
- 15. User Story …a piece of functionality valuable for the end-user.
- 16. Card As a [user role] I want [activity] so I can [benefit] User role – who (new user, guest, job-seeker)? Activity – functionality, action of the system, what? Benefit – value for the end-user, why?
- 17. User Story Card examples As a recruiter I want to search by job-seeker’s name so I can find all resumes of job-seeker
- 18. User Story: Conversation What do I need to make a successful product? What are the details I should work on? How do I validate the completed Stakeholder work? Developer Tester Which color scheme should we use? Designer
- 19. Level of details • Detailed enough for the team to start work from. • Further details to be established and clarified at the time of development. Details, Use cases, Mockups, Scenarios, Specs
- 20. INVEST principle • Independent • Negotiable • Valuable • Estimable • Small • Testable
- 22. Story mapping
- 23. Documents’ templates I f you want t o receive User Story & Product Vision templates, please send us the request: [email protected]
- 24. Recommended books " Karl Wiegers - S o f t w a r e Requirements " Mike Cohn - User stories applied " Dean Leffingwell - A g i l e Software Requirements " Henrik Kniberg - Scrum and XP from the trenches
- 25. Coming soon… Ø Workshops Киев Ø Kanban 14/09 Ø Communication with client 27/09 Ø ITKaiZenClub Киев Ø Нематериальная мотивация команды 29/07 Киев Ø Изменение sprint scope по средине разработки 09/09 Ø Webinars Ø Типичные ошибки п р и р а б о т е с клиентами 23/09 Ø Scrum VS Kanban: Kanban wins? 04/09
- 26. Thank you for your attention! We will be glad to answer your questions & invite you on our trainings ;) Our contacts: [email protected] E5Trainings E5Trainings E5 www.e-5.com.ua