If you were to ask product owners, all product people really, whether they spent more time in discovery or delivery, you’d expect them to say discovery.
While that’s certainly true, they also play an important role in delivery. Product owners make sure that their team stays focused on the outcome they seek to deliver, maintain the shared understanding they worked so hard to maintain, and they make sure those last minute decisions that inevitably come up are made in a timely manner.
This week let’s take a look at some suggestions on how you can build a strong relationship with your team and some techniques that you can use to improve the way you work with the development team.
One more thing – I’ve renamed this newsletter Inside Product Ownership alongside with a clarification of the entire KBP.media site to focus on product ownership.
The nature of the content on the site isn’t changing. It’s still provides resources help product people deliver powerful internal products. Product ownership seemed to be a better categorization for most of the content, which tends to be about how product people interact with the development team.
I’ll still include quite a bit of content about product management, especially about how those techniques are relevant for people working on those things that I’ve referred to as internal products.
The Secret to Working with Developers
Nick Butler dragged some real-life developers away from their keyboards and asked them what works for them when it comes to working with product owners. He found out that developers work most effectively when a product owner knows the product well, and communicates this knowledge responsively and decisively.
You Like Me!, Right Now You Like Me!*
Ron Lichty counsels developers, development managers, and scrum masters alike to forge alliances with their product manager counterparts. In this presentation at ProductTank San Francisco, he outlined how product managers can do the same – how to get their developers to love them and, along the way, enable high performance teams.
*This is the actual quote from Sally Field’s acceptance speech for the 1985 Academy Award for Best Actress. Not the often misquoted “You like me, you really like me!”
A delivery board is a way for a team to visualize their process for delivering functionality in a sprint. The best delivery boards consist of a whiteboard or wall divided into columns that reflect the various steps a team takes to develop and test backlog items in a sprint. The backlog items are represented by sticky notes or cards that move across the board as the team gets closer to having functionality to deliver.
Retrospectives with a Purpose
Action focused retrospectives are a way for your team to reflect on your past cycle of work, discuss what you’ve learned, identify specific action items to pursue, and follow through on those action items.
Documentation with a Purpose
System documentation is information about an as-built solution and acts as a reference for future maintenance or update efforts. It is organized based on system functionality rather than when changes were made to the system, making it easier for people who maintain the solution to find the information they need quickly.