Design 101 : Beyond ideation - Transforming Ideas to Software Requirements
- 1. Design 101 Beyond Ideation - Transforming Ideas into Software Requirements
- 2. Most people with an idea… • ‘know’ they’ve got a market for a product • have limited UX/design capabilities • will develop something that users don’t really want • need to move fast as they probably have a limited (or zero) budget
- 7. 1. Balance Business and User Needs
- 8. 2. Iteration Improves the Product
- 9. 3. Focusing on the UX is Key
- 10. Agenda… • Create your Product Vision • Identify your Users • Write User Stories • Build a Prototype
- 11. Product Vision Why - the reason for creating the product What – the goal you are aiming for
- 12. 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/
- 13. Benefits • Avoid useless features • Prioritise the backlog targeting the main goal • Align information across the team
- 14. 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!
- 15. Product Vision Template For _______________ who ___________________ (target customer) (customer need) ___________________ is a ___________________ (product idea) (market category) that ____________________________ (key benefit) Unlike ________________, __________________ (competitor) (unique differentiator)
- 16. Product Vision Example “For a mid-sized company's marketing and sales departments who need basic CRM functionality, the CRM-Innovator is a Web-based service that provides sales tracking, lead generation, and sales representative support features that improve customer relationships at critical touch points. Unlike other services or package software products, our product provides very capable services at a moderate cost” Source: http://www.quora.com/What-are-some-good-examples-of-a-product-vision
- 17. Exercise 1: Create your 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 • Pitch your Product Vision to the group Duration: 15 Minutes
- 18. Identify Your Users • What is a Persona? – archetypal users of an system that represent the needs of larger groups of users – identify the user motivations, expectations and goals • Why do we need them? – Helps identify user motivations, expectations and goals
- 19. Personas must be… • Relevant to business goals and the product • Data driven with clearly defined assumptions • Enlightening and inspiring
- 22. User Stories… • Describe functionality that is useful to the user or customer • Tell a story about how someone uses the product
- 23. Focus on the User • Describe functionality from the perspective of your target users • Use personas or user roles in your stories
- 24. 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
- 25. 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
- 26. Epic • A high level goal of a Persona • Usually too big to implement in single iteration • Usually split into features and then stories
- 27. Themes/Features • Collection of related stories • Usually used to organize stories into releases
- 28. User Story Map Source: http://www.payton-consulting.com/how-to-create-a-user-story-map/
- 29. Exercise 2: Write User Stories • Identify 2 personas for your product idea • Write a few User Stories for each persona • Group the User Stories into Themes (Features) • Group the Themes into high level goals (Epics) • Create a User Story Map Duration: 30 Minutes
- 30. User Story Map
- 31. User Story Map
- 32. Exercise 3: Create a User Story Map • Organise Epic, Themes and User Stories into a User Story Map • Assign each User Story a T-shirt size (S,M,L,XL or XXL) • Arrange User Stories in priority order (highest at the top) Duration: 20 Minutes
- 34. Exercise 4: Build a Prototype • Download the Pop™ App to your Smartphone • Create paper prototypes of typical screens for your App • Capture your prototypes with Pop™ • Link the screens inside Pop ™ • Demo your prototype Duration: 30 Minutes
- 35. Summary • You have just converted your idea into Agile Software Requirements • You now have enough information to – Engage a UX Designer – Engage a Web Developer – Engage an App Developer – Learn some coding and do it yourself! • Congratulations!
- 36. Resources
Editor's Notes
- #12: https://www.scrumalliance.org/community/articles/2009/january/the-product-vision http://www.romanpichler.com/blog/tips-for-writing-compelling-product-vision/
- #23: http://www.payton-consulting.com/explain-present-user-stories/
- #27: 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.
- #28: ‘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.
- #29: ‘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.
- #30: http://www.payton-consulting.com/how-to-create-a-user-story/ http://www.payton-consulting.com/how-to-create-a-user-story-map/
- #33: http://www.payton-consulting.com/how-to-create-a-user-story/ http://www.payton-consulting.com/how-to-create-a-user-story-map/
- #35: http://www.payton-consulting.com/how-to-create-a-user-story/ http://www.payton-consulting.com/how-to-create-a-user-story-map/