Working without a Product Owner by Maaret Pyhajarvi at #AgileIndia2019
•
0 likes•195 views
The document describes an experiment conducted by a software development team where they worked without a dedicated Product Owner for 3 months. In the experiment, the team was directly responsible for interacting with customers and prioritizing work. After the experiment, the team found that they were able to deliver more while being more customer-focused without a Product Owner acting as a proxy between them and customers. The team also realized they did not need the Product Management Expert to be present at all planning meetings to understand customer priorities. After a year of working without a Product Owner, the team was recognized as the "Best Team in Corporate R&D".
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Working without a Product Owner by Maaret Pyhajarvi at #AgileIndia2019
Similar to Working without a Product Owner by Maaret Pyhajarvi at #AgileIndia2019 (20)
More from Agile Software Community of India
More from Agile Software Community of India (20)
Recently uploaded
Recently uploaded (20)
Working without a Product Owner by Maaret Pyhajarvi at #AgileIndia2019
- 1. @maaretp http://maaretp.com Working without a Product Owner by Maaret Pyhäjärvi
- 2. @maaretp http://maaretp.com Taking forward an established product From Lead Quality Engineer to Senior Manager, Windows Endpoint Development Customers in millions, test automation with 14k virtual machines spawned daily.
- 3. @maaretp http://maaretp.com Testers don’t break the code, they break your illusions about the code. - Adapted from James Bach WHATEVER NECESSARY
- 4. @maaretp http://maaretp.com Code doing what it’s supposed to. Product doing what it would need to. Product doing only what it is supposed to do. Basic Illusions: Code Making a Product Other Illusions: Ideas Leading to Code Process being able to deliver with a change in mind People having skills to deliver well. Business model driving the selection of right focus.
- 5. @maaretp http://maaretp.com Continuous Delivery No Jira No Estimates No Product Owner No Projects No Scrum
- 6. @maaretp http://maaretp.com Turning Ideas into Code Get the right ideas on every single developer
- 10. @maaretp http://maaretp.com But Being a Product Owner is So Much Work!
- 11. @maaretp http://maaretp.com BEING A PRODUCT OWNER SURE IS A LOT OF WORK! - WILLIAM GILL
- 12. @maaretp http://maaretp.com Setting up a 3-month Experiment
- 13. @maaretp http://maaretp.com OUR EXPERIMENT HYPOTHESIS CUSTOMER-OBSESSED TEAM DIRECTLY IN TOUCH WITH THEIR CUSTOMERS PERFORMS BETTER WITHOUT A PROXY
- 14. @maaretp http://maaretp.com Before this Experiment …hands-off manager … multiple ways of dealing with team list of work = super-simple Jira flow without Jira …moving the product owner out of team room …frequent releases …no estimates
- 15. @maaretp http://maaretp.com Listing Product Owner Responsibilities
- 16. @maaretp http://maaretp.com Product Owner to Product Management Expert to work on Requirements Trawling
- 17. @maaretp http://maaretp.com RETRO 1. Nothing changed 2. Delivered more 3. Magical things happened 4. Strategic thinking for PME 5. NOTHING TRAWLED
- 18. @maaretp http://maaretp.com 21 days into the experiment the team received feedback that their latest demo was particularly good and focused on the customer value.When confronted with the feedback, the team considered it as "that's what we're supposed to do now" - we are customer-focused.
- 19. @maaretp http://maaretp.com 65 days into the experiment the team realizes the last appearance of the product management expert in planning was around day 55.There were other channels to maintain pulse of what might be important than the structure.
- 20. @maaretp http://maaretp.com Impacts in the team
- 21. @maaretp http://maaretp.com Fixing geared up to max
- 24. @maaretp http://maaretp.com Faster Delivery of Solutions
- 26. @maaretp http://maaretp.com Features from Problems that weren’t asked for
- 27. @maaretp http://maaretp.com Introducing Positive and Negative Telemetry
- 29. @maaretp http://maaretp.com Working as Network of Connections
- 30. @maaretp http://maaretp.com Bias to Action
- 31. @maaretp http://maaretp.com Customers: Don’t keep a Distance
- 32. @maaretp http://maaretp.com Data Lies Less than People
- 33. @maaretp http://maaretp.com After a Year of #NoProductOwner
- 34. @maaretp http://maaretp.com “Best Team in Corporate R&D”
- 35. @maaretp http://maaretp.com “One team is not sufficient proof that this approach is better. Also, out team lacks the seniority and communication skills to attempt it.”
- 36. @maaretp http://maaretp.com Nothing changes if you change nothing.
- 38. @maaretp http://maaretp.com Developers love solving problems
- 39. @maaretp http://maaretp.com Maaret Pyhäjärvi Email: maaret@iki.fi Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn)