A Product Owner’s Syllabus

This content is syndicated from Edge of Chaos | Agile Development Blog by Olga Kouzina. To view the original post in full, click here.

In one of my previous articles (Project Managers: Nurturing vs. Hiring?) I’ve written on why we prefer to nurture product owners (we call them feature owners) internally, instead of hiring newcomers. Quite some time has passed since we decided to try this approach, and it has yielded good results mostly. It’s safer and more reasonable to have several competent people involved in the product-related decision-making,  instead of one person who is held accountable for everything. All the people in our company — QA’s, developers, designers, marketing and support people — are engaged in educational activities one way or another. These activities are always intertwined with work. Home-made product owners are educated with the work, too, and we’ve come up with some sort of syllabus for them. This syllabus emerged from the real-life needs; it is a composite of skills and knowledge actually required to manage our product.

We are not putting a “certified Targetprocess Product Owner’s” training course tag on that syllabus, but I intend to write a series of articles that would provide some sort of “homeschooling” for novice product owners. Quite often formal training courses are too brief (2-3 days), cost money and fail to give that universal knowledge that a product owner needs (poke me if that’s not true). A formal course might be limited to a single “brand” or “label” from a certain domain, while the needs of practical software development require out-of-the-box, labelless thinking.  That being said,  a product owner still will want to be familiar with the major trends in the agile domain, and to switch between the brands and labels easily, depending on where a product is meant to go next.

Here’s a summary of this homeschooling Product Owner’s Syllabus. The mind map only gives a descriptive outline of the syllabus, as an intro to the upcoming articles. Click to enlarge:

Product Owner Syllabus

We educate our feature owners in the 4 main areas: Agile Domain, Marketing, Product Development and Backlog Management. Targetprocess 3, our visual project management tool, is the practice material for these studies.

Let me re-iterate, that first and most a Product Owner is someone with a curious and agile mind. The way we orient our feature owners/product owners is free from prescriptions. The main disadvantage of taking a training course that bears some “label” would often mean that students are pushed to operate within the limits of this label forgetting that there are other practices that can work better in this particular case. As an example, if there’s a course that trains Product Owners in Scrum only, this will be limiting, because their work might demand switching to Kanban, or maybe to Multiban, or to waterfall (which is now clad in the toga of SAF). This freedom from frameworks and labels is the most important prerequisite of a product owner’s success. Practices are only practices. The first question that a product owner should have when introduced to a technique or a practice is: “Why our product development might need this practice?” and not: “How do we tweak our product development to fit it to this agile practice?”

Another meta-skill applicable to all the areas is the ability to measure, analyze and make decisions. We measure feedback, we measure customer satisfaction, we measure the value of features. Most decisions are made based on the measurements and their analysis. The upper tier of product-related decisions (which feature will be developed next) is done by a group, the product board,  and feature owners are a part of this board. Then, decisions related to a product feature are in the realm of power of a feature owner. The air of learning and sharing is maintained throughout the whole product management process.

That’s how it looks, for starters. I will cover the subjects included to this syllabus in more detail in the future articles.

Leave a Reply

What is 10 + 3 ?
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.”