Agile Requirements Discovery
- 1. Agile Requirements Discovery Twitter: #agile101 @agilenewbies
- 2. Today… • Cross-functional Teams • Product Vision • Agile Requirements • Group Exercises • Q&A
- 3. Cross-functional Teams “…a group of people with different functional expertise working together towards a common goal”– Wikipedia
- 4. Why cross-functional teams? Diversity of perspectives fuels greater innovation which leads to better products
- 5. How does this relate to Agile? A key ingredient in successful, high-performing, self-organized teams that discourages “..that’s not my job” mentality
- 6. Typical Cross-functional Team Source: http://www.mountaingoatsoftware.com/blog/cultivate-communities-of-practice
- 7. Exercise 1: Cross-functional Teams • 5 volunteers for Product Lead • Each Product Lead should form a Cross- functional Team of 6-8 members • Each team should choose a Team Identity Duration: 5 minutes
- 8. Why - the reason for creating the product What – the goal you are aiming for
- 9. Who Creates the Product Vision? Everyone involved in developing the product as the whole team must share the same vision Source: http://www.productmanagerclub.com/category/envisioning/
- 10. Why Product Vision? • Avoid useless features • Prioritise features to target the main goal • Align information across the team
- 11. Golden rules • Target the customer • Target the customer’s needs • Identify the market • Identify Product attributes • How do I know if my product vision works? ELEVATOR TEST!
- 12. Product Vision Template For _______________ who ___________________ (target customer) (customer need) ___________________ is a ___________________ (product idea) (product category) that _____________________________________ (key benefit, compelling reason to buy) Unlike ________________, __________________ (competitor) (unique differentiator)
- 13. Product Vision Example For a mid-sized startup who need a customer relationship management solution, the SalesForce.com platform is a cloud-based service that provides sales tracking, lead generation, and sales representative support features that improve customer relationships Unlike Oracle CRM, Salesforce.com provides very capable services at a moderate cost Source: http://www.quora.com/What-are-some-good-examples-of-a-product-vision
- 14. Exercise 2: Create a Product Vision • Each team should brainstorm and come up with a software product idea • Create a Product Vision Statement for their product idea • Product leads should sharethe Product Vision with the group Duration: 15 Minutes
- 15. Impact Mapping
- 16. • Personas • User Stories • Epics • Themes/Features • User Story Mapping Agile Requirements
- 17. Persona • Typical user of a system that represent the needs of larger groups of users • Helps identify user motivations and goals • Drives clarification of user expectations and requirements
- 18. Personas must be… Relevant to business goals and the product, have clearly defined assumptions, enlightening and inspiring
- 19. User Story
- 20. User Stories… • Describe functionality that is useful to the user or customer • Tell a story about how someone uses the product
- 21. Focus on the User Describe functionality from the perspective of your personas
- 22. Engage in Conversation • A story is not a specification. • It captures the essence of a conversation about the features of a product • User Stories encourage creativity • Stories facilitate dialogue between the team and the customer
- 23. Example User Story Amanda, a new Netflix customer, wants to see recommendations 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
- 24. Epic • A high level goal of a Persona • Usually too big to implement in single iteration • Usually split into features and then stories • E.g. Buy a plane ticket
- 25. Themes/Features • Collection of related stories • Usually used to organize stories into releases • E.g. Search for flight
- 26. User Story Map Source: http://www.payton-consulting.com/how-to-create-a-user-story-map/
- 27. Release Planning with Story Maps Source: http://winnipegagilist.blogspot.co.uk/2012/03/how-to-create-user-story-map.html
- 28. Release Planning with Story Maps Source: http://winnipegagilist.blogspot.co.uk/2012/03/how-to-create-user-story-map.html
- 29. Exercise 3: Create a User Story Map • Identify 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 Feature • Create User Stories associated with each Theme • Prioritise the User Stories • Organise Epic, Features and User Stories into a User Story Map Duration: 30 Minutes
- 30. Agile Requirements Pros & Cons • Short and easy to modify when requirements change • Allow projects to be broken into small increments • Easier to estimate the development effort • Drives the creation of acceptance tests • Completed user stories can go for development • Initial learning curve • Requires close customer contact • Relies heavily on a competent and engaged team
- 31. Resources
Editor's Notes
- #4: Have all the necessary skills to turn the idea into a product http://www.payton-consulting.com/scrum-cross-functional-teams-important-build/ http://www.keystoneinnovationchallenge.com/images/CrossFrunctionalTeams.png
- #5: http://www.jonar.com/jonarblog/come-together-right-now-the-benefits-of-cross-functional-teams/
- #6: http://www.managementexchange.com/sites/default/files/styles/large/public/Cross%20Functional%20-%20Diverse%20Team.jpg?itok=Yc0Geyfw
- #7: http://www.mountaingoatsoftware.com/blog/cultivate-communities-of-practice
- #9: https://www.scrumalliance.org/community/articles/2009/january/the-product-vision http://www.romanpichler.com/blog/tips-for-writing-compelling-product-vision/
- #16: http://www.bawbgale.com/wp-content/uploads/2015/01/impact_map_example.png
- #17: http://www.payton-consulting.com/run-user-story-workshop/
- #20: ‘Epic’, ‘Feature’ and ‘Theme’ have had different meanings in every company I have worked in. ‘Epic’ – a large user story that will usually be split into smaller stories ‘Theme’ – a group of features ‘Feature’ – A discrete piece of business value. ‘User Story’ – Contributes to a Feature. What teams deal with everyday.
- #21: http://www.payton-consulting.com/explain-present-user-stories/
- #25: http://www.payton-consulting.com/run-user-story-workshop/ ‘Epic’, ‘Feature’ and ‘Theme’ have had different meanings in every company I have worked in. ‘Epic’ – a large user story that will usually be split into smaller stories ‘Theme’ – a group of features ‘Feature’ – A discrete piece of business value. ‘User Story’ – Contributes to a Feature. What teams deal with everyday.
- #26: ‘Epic’, ‘Feature’ and ‘Theme’ have had different meanings in every company I have worked in. ‘Epic’ – a large user story that will usually be split into smaller stories ‘Theme’ – a group of features ‘Feature’ – A discrete piece of business value. ‘User Story’ – Contributes to a Feature. What teams deal with everyday.
- #27: ‘Epic’, ‘Feature’ and ‘Theme’ have had different meanings in every company I have worked in. ‘Epic’ – a large user story that will usually be split into smaller stories ‘Theme’ – a group of features ‘Feature’ – A discrete piece of business value. ‘User Story’ – Contributes to a Feature. What teams deal with everyday.
- #28: http://winnipegagilist.blogspot.co.uk/2012/03/how-to-create-user-story-map.html
- #29: http://winnipegagilist.blogspot.co.uk/2012/03/how-to-create-user-story-map.html
- #30: http://www.payton-consulting.com/how-to-create-a-user-story/ http://www.payton-consulting.com/how-to-create-a-user-story-map/