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".
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.
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.
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
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.
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.”