Agile Requirements Discovery
33
Agile Requirements Discovery Twi6er: #agile101 @agilenewbies
Transcript of Agile Requirements Discovery
Agile Requirements Discovery
Twi6er: #agile101 @agilenewbies
Contents
• Cross-‐funcAonal Teams • Product Vision • Agile Requirements • Group Exercises • Q&A
Cross-‐funcAonal Teams
“…a group of people with different func4onal exper4se working together towards a common goal” – Wikipedia
Why cross-‐funcAonal teams?
Diversity of perspecAves fuels greater innovaAon which leads to be6er products
How does this relate to Agile?
A key ingredient in successful, high-‐performing, self-‐organized teams that discourages “..that’s not my job” mentality
Typical Cross-‐funcAonal Team
Source: h6p://www.mountaingoatsoZware.com/blog/culAvate-‐communiAes-‐of-‐pracAce
Exercise 1: Cross-‐funcAonal Teams
• Form cross-‐funcAonal teams of 6-‐8 people • Nominate a product lead • Product leads are responsible for clarifying product features and driving product vision
DuraAon: 10 Minutes
Product Vision
Why -‐ the reason for creaAng the product What – the goal you are aiming for
Who Creates the Product Vision?
Everyone involved in developing the product as the whole team must share the same vision
Source: h6p://www.productmanagerclub.com/category/envisioning/
Benefits
• Avoid useless feature • PrioriAse the backlog targeAng the main goal • Align informaAon across the team
Golden rules
• Target the customer • Target the customer’s needs • IdenAfy the market • IdenAfy Product a6ributes • How do I know if my product vision works? ELEVATOR TEST!
Product Vision Example
“For a mid-‐sized company's marke4ng and sales departments
who need basic CRM func4onality, the CRM-‐Innovator
is a Web-‐based service that provides sales tracking, lead genera4on, and sales representa4ve support features that improve customer rela4onships at cri4cal touch points. Unlike other services or package soIware products, our product provides very capable services at a moderate
cost”
Source: h6p://www.quora.com/What-‐are-‐some-‐good-‐examples-‐of-‐a-‐product-‐vision
Product Vision Template
For _______________ who ___________________ (target customer) (customer need)
___________________ is a ___________________ (product idea) (product category) that _____________________________________ (key benefit, compelling reason to buy) Unlike ________________, __________________ (compeAtor) (unique differenAator)
Impact Mapping
Exercise 2: Create a Product Vision • Each team should brainstorm and come up with a product idea (e.g. Smart Fridge)
• Create a Product Vision Statement for your product idea
• Create a Impact map for your product idea • Product lead to present the Product Vision to the group
DuraAon: 15 Minutes
• Personas
• User Stories
• Epics
• Themes/Features
• User Story Mapping
• Agile Estimation
Agile Requirements
Persona
• Typical user of a system that represent the needs of larger groups of users
• Helps idenAfy user moAvaAons and goals • Drives clarificaAon of user expectaAons and requirements
Personas must be…
Relevant to business goals and the product, have clearly defined assumpAons, enlightening and inspiring
User Story
User Stories…
• Describe funcAonality that is useful to the user or customer
• Tell a story about how someone uses the product
Focus on the User
Describe funcAonality from the perspecAve of your personas
Engage in ConversaAon
• A story is not a specificaAon. • It captures the essence of a conversaAon about the features of a product
• User Stories encourage creaAvity • Stories facilitate dialogue between the team and the customer
Example User Story
Amanda, a new Nenlix customer, wants to see recommendaAons for other movies she could watch based on her past viewings so that she gets to know what else is available to watch without having to browse a long list of movies
Epic
• A high level goal of a Persona • Usually too big to implement in single iteraAon • Usually split into features and then stories
Themes/Features
• CollecAon of related stories • Usually used to organize stories into releases
User Story Map
Source: h6p://www.payton-‐consulAng.com/how-‐to-‐create-‐a-‐user-‐story-‐map/
Release Planning with Story Maps
Source: h6p://winnipegagilist.blogspot.co.uk/2012/03/how-‐to-‐create-‐user-‐story-‐map.html
Release Planning with Story Maps
Source: h6p://winnipegagilist.blogspot.co.uk/2012/03/how-‐to-‐create-‐user-‐story-‐map.html
Agile EsAmaAon
• RelaAve EsAmaAon • Focus on speed over accuracy • Depends on team’s knowledge of domain
Source: h6p://www.agilenutshell.com/episodes/3-‐esAmaAon
Agile EsAmaAon Techniques
• T-‐shirt Sizes • Planning Poker
Source: h6p://www.agilenutshell.com/episodes/3-‐esAmaAon
Exercise 3: Create a User Story Map
• IdenAfy 3 Personas for your product idea • Outline the Epics for one of the Personas • Choose one Epic and outline each step of the user flow as
a separate Theme/Feature • Create User Stories associated with each Theme • Assign each User Story a T-‐shirt size (S,M,L,XL or XXL) • Arrange User Stories in priority order (highest at the top) • Organise Epic, Themes and User Stories into a User Story
Map DuraAon: 30 Minutes
Agile Requirements Pros & Cons
• Short and easy to modify when requirements change
• Allow projects to be broken into small increments • Easier to esAmate the development effort • Completed user stories can go for development • Drives the creaAon of acceptance tests • IniAal learning curve • Requires close customer contact • Relies heavily on a competent and engaged team
Resources
