Requirements in agile for SE2014
description
Transcript of Requirements in agile for SE2014
![Page 1: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/1.jpg)
Requirements management
In Agile: What’s happening
in real world?
![Page 2: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/2.jpg)
Let’s introduce ourselves ;)
Helen PrykhnychCo-founder & trainer @ E5 IC Agile certified professional In past – Returns Operation Department Manager, Project Manager, Manager of Kyiv office of IT outsourcing company
Roman SakharovLead Business Analyst & Resource manager @ EPAM SystemsCertified Scrum Master, Trainer In past – Testing Engineer, Project Manager
![Page 3: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/3.jpg)
Prize for the most interesting question ;)
![Page 4: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/4.jpg)
How are requirementschanged in Agile compared with othermethodoligies (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.
![Page 5: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/5.jpg)
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?
![Page 6: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/6.jpg)
Initial description (Vision)
Theme
Epic
User Story
Work breakdown in Agile
![Page 7: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/7.jpg)
Task, User Story, Epic, Theme
![Page 8: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/8.jpg)
Epic 1
Epic 2
Epic 3
Epic 4
Epic 5
Epic 6
Theme 1
Theme 2
Start with Themes & Epics
![Page 9: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/9.jpg)
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
![Page 10: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/10.jpg)
Epic 1
Epic 2
Epic 3
Epic 4
Slice the cake
US1
Epic 1
US2
US4 US5
US6 US7
US8
Epic 6
Epic 2
Epic 1
Epic 4
Epic 3
Epic 5
Epic 4
Epic 3
Epic 5
Epic 5
Epic 6
![Page 11: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/11.jpg)
Just In Time
Closest Iteration
Final Iteration
TASKS STORY STORY/EPIC EPIC THEME(Iteration in play)
![Page 12: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/12.jpg)
Prioritization
Based on Value
using MoSCoW:
• M - MUST
• S - SHOULD
• C - COULD
• W - WON'T (but would like)
![Page 13: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/13.jpg)
Why do we prioritize?
![Page 14: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/14.jpg)
14
Agile Analysis Proces in Time flow
![Page 15: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/15.jpg)
User Story
…a piece of functionality valuable for the end-user.
![Page 16: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/16.jpg)
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?
![Page 17: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/17.jpg)
User Story Card examplesAs a recruiter
I want to search by job-seeker’s name so I can find all resumes of job-seeker
![Page 18: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/18.jpg)
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
work?Stakeholder
Developer
Tester
Which color scheme should
we use?
Designer
![Page 19: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/19.jpg)
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
![Page 20: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/20.jpg)
• Independent
• Negotiable
• Valuable
• Estimable
• Small
• Testable
INVEST principle
![Page 21: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/21.jpg)
Bonus: Story mapping
![Page 22: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/22.jpg)
Story mapping
![Page 23: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/23.jpg)
Documents’ templates
If you want to receive User Story & Product Vision templates, please send us the request:[email protected]
![Page 24: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/24.jpg)
Recommended books Karl Wiegers - Software RequirementsMike Cohn - User stories appliedDean Leffingwell - Agile Software RequirementsHenrik Kniberg - Scrum and XP from the trenches
![Page 25: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/25.jpg)
Coming soon…
Requirements management workshop @ July, 12
ITKaiZenClub @ July, 10 & 29
![Page 26: Requirements in agile for SE2014](https://reader033.fdocuments.us/reader033/viewer/2022060108/554d1adcb4c905c5208b4639/html5/thumbnails/26.jpg)
Thank you for your attention!
Our contacts:
[email protected] E5Trainings E5Trainings E5 www.e-5.com.ua
We will be glad to answer your questions & invite you on our trainings ;)