Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Experience sharing on benefits and downsides of PO tools for partnership building
Similar to Experience sharing on benefits and downsides of PO tools for partnership building (20)
Recently uploaded
Recently uploaded (20)
Experience sharing on benefits and downsides of PO tools for partnership building
- 1. Experience share (benefits and downsides, impact on partnership building) Małgorzata Maksimczyk What for all those PO tools & techniques?
- 2. 2 Why am I here? share
- 3. 3 Ways of working Content mapping Product discovery Clean BacklogStory map & roadmap Clean Backlog Product Vision Board Value Proposition Canvas User Journey Business Model Canvas Personas Competition analysis Stakeholder mapping, RACI User Testing Problem Solution Fit
- 4. 4 Based on 2 real life cases scenarios (from building the trust to product creation)
- 5. 5 2h: rules prepare Ways of working ● ongoing process thru product build lifecycle
- 6. 6 ● Benefit-> Partnership ● Full transparency on challenges ● 1 day feedback loop between the done task and Client feedback ● Ongoing user feedback via forums ● User testing (corridor) Ways of working Stakeholder mapping RACI Transparent process ● day to day use
- 7. 7 ● Principals - projects sponsors with business goals we are trying to achieve ● End-users - our target group of the product ● Insiders - users from organization that will influence the product ● Other Critical / Important / Interesting 30-60m: prepare ● additional benefit: input to the other methods
- 8. 8 30m Ways of working Stakeholders analysis and mapping Who really counts? Source: Stakeholder Salience https://www.stakeholdermap.com/stakeholder-analysis/stakeholder-salience.html ● day to day use
- 9. 9 ● Benefits ○ Partnership model ○ from scribe PO to proxy / business representative PO ● Downsides ○ might be time consuming to agree the process or owners (sooner the better) Ways of working RACI Transparent process ● day to day use
- 10. 10 Transparent process of requirements agreement & Roles (RACI) Draft requirements discussion Draft mock up (if applicable) Further business confirmations Final design Requirements & development readiness Ready to do Jira requirements owners:... Designs owners: ... 1.User story and Acceptance Criteria prepare owners: ... Owners: ... Technical refinement Owners: Magic estimate Owners: ... 3.Requirements acceptance 2.Requirements refinement Sprint estimate Process Backlog estimate Estimate approach Prioritization of topics (meetings) Requirements stage
- 11. 11 Development process with bi-weekly review Part.C testing Bug or improvement create Review Released to PROD Development Release to env. A Part.B testing Part.A testing few days Sprint N 2 weeks 1 week (for regular cycle)WED 1.Sprint N (current): critical bugs ONLY, and exceptional process - option 2 2.Sprint N+1, N+2: lower than critical bugs & improvements, all features (all that is not a critical bug) 3.Releases to env A and production only after review Product Meeting - 1-2x week
- 12. 12 Development process - exceptional process Released to PROD Obligatory Recommended Critical production bugs &critical features prioritized fully as per Biz needs (daily ) Release to env.A Part.A testing Cycle N (current): critical bugs Sprint N+1, N+2: lower than critical bugs & improvements 1) business catch up (bug prioritization): daily for crucial periods 2) Ad hoc Release to env A / PROD only for critical production bugs Part.B testing Part.C testing
- 13. 13 Key takeaway What for? To build partnership step by step ● By knowing your stakeholders well ● By being transparent with your ways of working
- 14. 14 Product discovery ● ongoing process thru product build lifecycle
- 15. 15 ● Benefits ○ all stakeholders agreement for the product vision ○ first feeling what for is the product ● Downsides ○ Need for a deep dive to get more details Product discovery Business Model Canvas Value Proposition Canvas or Proto - Personas Vision Board ● for each key feature or functionality 45m - 2h for each
- 16. 16 45m - 2h for each ● for each key product group
- 17. 17 Alternative approaches and deep dive into product vision
- 18. 18 ● Benefits ○ Deeper dive into segments & needs (if users groups are identified) ○ Great help in requirements focus and prioritization /user orientation ● Downsides ○ It is hypothetical persona (proto) unless there are upfront analyses 30m - 1h per proto-persona ● per segment
- 19. 19 ● Benefits ○ Holistic view for company business model ● Downsides ○ Where it goes for customer segments it might be too simplistic 2h: Business Model Canvas source: https://strategyzer.com/
- 20. 20 ● Benefits ○ Perfect product idea creation tool! ○ Especially with toolset proposed at https://strategyzer.com/ ○ Deep dive into customer needs and product value proposition ● Downsides ○ It is still a hypothesis till it is validated 1-2h per customer segment source: https://strategyzer.com/
- 21. 21
- 22. 22 Key takeaway What for? ● To understand what is and what is not a business value (value proposition) ● To understand what user needs (pains / gains) product is currently satisfying or where is a value proposition gap
- 23. 23 User journey ● product discovery start point ● repeated process whenever new customer segment is targeted, new feature or design is planned
- 24. 24 ● Benefits ○ Feature proposals are based on user emotions and expectations and matched to product design ● Downsides ○ It still hypothesis till user test (unless made during user testing) 30min-1h per user journey
- 25. 25 What next with challenges found?
- 26. 26 Problem - Solution Fit ● product discovery start point ● a way of thinking on each key requirement or requirements group
- 27. 27 ● Benefits ○ Concentrate on unique value proposition for the user (problem - solution) ○ Gives perspective you might forget once doing day to day work ○ Way of thinking! ● Downsides ○ I did not notice any so far :) Few minutes - 2 hours ● structured approach to product ● or a way of thinking (day to day, during refinements, during meeting with Clients, etc.) an extract from Lean Canvas technique
- 28. 28 Key takeaway Problem - solution fit is a way of thinking
- 29. 29 ● Benefits ○ high level overview of competition solution ○ Easy way to learn on how competition addresses user needs and how we want to differentiate from them ○ good way to know product (looking on features thru unique value proposition) ● Downsides ○ You might not invent brand new products by just looking what others do 0,5-1 day: Competition analysis Competition analysis
- 30. 30
- 31. 31 Key takeaway Do not concentrate that much on features competition is having but try to figure out how they cover customer needs and by what unique value they are proposing. Then think what market gap you might want to cover
- 32. 32 Story Mapping ● ongoing process with many iterations
- 33. 33 ● Benefits ○ The best tool to make good roadmap ○ Gives team few dimensions to think about during refinements ○ Shows complexity ○ Base for magic estimates, release planning and MVP ● Downsides ○ Good split might not be made successfully the first time (for me it is on average 2nd or 3rd try) / reiterate on it ongoing process Story mapping
- 34. 34
- 35. 35 Key takeaway What for? ● To shows complexity to stakeholders ● To encourage team discussion to capture holistic view &task dependencies ● To plan releases ● To capture MVP ● To give input to tidy & organized backlog
- 36. 36 Content mapping ● whenever content structure is complex
- 37. 37 ● Successes ○ Team and myself could understand which system areas are mapped to what content ○ Refinements were much more simpler ● Downsides ○ First version was not perfect - misunderstood content architecture (complexity), 2nd one was better 2 days for sample below
- 38. 38 Key takeaway What for? ● To understand the complexity of product content
- 39. 39 User corridor testing few hours
- 40. 40 ● Successes ○ I believed for what I have read “You Only Need to Test with 5 Users...” /Jakob Nielsen (https://www.nngroup.com/ar ticles/why-you-only-need-to- test-with-5-users/) few hours User testing source: https://www.nngroup.com
- 41. 41
- 42. 42 Key takeaway What for? ● To prove hypothesis on user needs, user paths and finally value proposition
- 43. 43 Summary Techniques: Try different product creation techniques as much as possible. For each of methods try implementation few times as each time you might get other conclusions. Clients & Partners cooperations: With Clients and Partners (external or internal) it is all about trust. Build it step by step showing your engagement and product value creation
- 44. THANK YOU! ● Questions? ● Knowledge share? Let’s stay in touch @LinkedIn Małgorzata Maksimczyk