One Real-Life Product Owner Team

This content is syndicated from LeadingAgile by Mike Cottmeyer. To view the original post in full, click here.

Okay… enough of the theory.  I want to share with you guys the roles involved with one of the Product Owner teams I’m working with right now.  I’ve listed each role and why we added these people to the team. As always, interested to know your thoughts:
  1. Chief Product Owner – The CPO provides strategic product direction to the Product Owner Team and interacts directly with each individual Scrum team as necessary.  The CPO’s primary responsibility is to interface with each of the other Product Managers, gather their requirements, understand their business drivers, understand their high level timelines and make business focused trade-offs that deliver the most value to the business, given the time and cost constraints, and measured throughput of the team.  The CPO can pull other Product Managers into the Product Owner team, or even the individual Scrum teams, as necessary to communicate business goals to the team.
  2. Architect – The Architect provides strategic technology direction to the Product Owner team and interacts directly with each individual Scrum team as necessary.  The Architect’s primary responsibility is to make the significant architectural decisions that impact the long-term direction of the product, or those design decisions that have impact across multiple Scrum teams.  The goal with the Architect’s participation is to make the decisions that cannot, or should not be made at the team level.  This role should defer as many design decisions to the individual Scrum teams as possible.  The Architect will also help the PO team to understand the cost of features we might add to the backlog, and work with Product Management to develop solutions that can be delivered within the time, cost, and ROI constraints of the business.
  3. Project Manager – The Project Manager manages the overall plan and makes sure that the mechanics of the Product Owner team are happening as necessary.  The Project Manager will manage release level communication with external stakeholders; facilitate meetings as necessary, and work to help people come to consensus in the best interest of the overall product.  This person will understand the velocity of each Scrum team, and how their progress supports on-time delivery of the release, relative to the size of the backlog.  They will work across the Scrum teams to understand organizational constraints and impediments, and either get these issues resolved, or make recommendations on how the overall delivery capacity of the team could be improved.
  4. Business Analysts – The BA’s role is to provide domain knowledge in her area of expertise, facilitate the participation of other Business Analysts as necessary, work with Product Management to elicit requirements as necessary, work with Product Management and the Product Owner team to define acceptance criteria, and maintain the prioritized product backlog.
  5. Systems Engineer – The SE’s role is to provide technical domain knowledge in his area of the product.  The SE will facilitate participation of other Systems Engineers as necessary, and work with the Architects and Team Leads to document any design constraints that either guide, or limit the options of the individual Scrum teams.
  6. Quality Assurance – QA’s role is to provide domain knowledge in the area of testing and facilitate the participation of other QA engineers as necessary.  The QA representative has the job of assessing the readiness of the user stories from a testability perspective and providing guidance on how to break down user stories in a way that makes the job of the test engineers easier and results in better quality, easier to maintain, code.
  7. Technical Leads/ScrumMasters – These folks are not part of the core team, but may participate as necessary in the backlog grooming process.  Their participation in the Product Owner team is primarily a formal feedback mechanism to help the Product Owner team understand team level impediments and coordinate dependencies between teams.
Collectively, these people are responsible for decomposing the backlog in a way that can be easily consumed by the team in sprint planning.  The Product Owner team will also provide an early, high-level estimates so that we can quickly determine a release candidate scope.  The Product Owner team will bring the release candidate scope to the team for final validation, breakdown, and estimation prior to making either a final release decision, but definitely before anything get’s pulled into the sprint. It’s early for this particular team, but I think we’ve got all the right pieces in place, and are on our way to getting this team of folks to gel.  As I said, always welcome your comments.  

Leave a Reply

What is 2 + 4 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”