Requirements management

In Agile: What’s happening

in real world?

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.

Prize for the most interesting question ;)

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.

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?

Initial description (Vision)

Theme

Epic

User Story

Work breakdown in Agile

Task, User Story, Epic, Theme

Epic 1

Epic 2

Epic 3

Epic 4

Epic 5

Epic 6

Theme 1

Theme 2

Start with Themes & Epics

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

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

Just In Time

Closest Iteration Final Iteration

TASKS STORY STORY/EPIC EPIC THEME (Iteration in play)

Prioritization Based on Value using MoSCoW: •  M - MUST •  S - SHOULD •  C - COULD •  W - WON'T (but would like)

Why do we prioritize?

Agile Analysis Proces in Time flow

14

15

User Story …a piece of functionality valuable for the

end-user.

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?

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

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

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

•  Independent •  Negotiable •  Valuable •  Estimable •  Small •  Testable

INVEST principle

Bonus: Story mapping

Story mapping

Documents’ templates I f y o u w a n t t o receive User Story & Product Vision templates, please send us the request: info@e-5.com.ua

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 S o f t w a r e Requirements

"  Henrik Kniberg - Scrum and XP from the trenches

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

Thank you for your attention!

Our contacts: info@e-5.com.ua E5Trainings E5Trainings E5 www.e-5.com.ua

We will be glad to answer your questions & invite you on our trainings ;)