The product owner role was introduced in Scrum in 1993. So, the role has been around for ~25 years. Yet, still, we struggle with the nature of it. Is it simple or complex? Is it inward or outwardly facing? It is about backlogs and stories or something more? And is ‘ownership’ the whole point?
In this talk, Bob Galen will be sharing his 4-Quadrants model for what effective (good) product ownership looks like in the real world. It will start with balance because the role is so broad and deep in its nuance. The essence of the 4-quadrants says that there are product, project, analyst, and leadership parts to the role. We’ll explore each in turn and talk about cross-connecting each area. We’ll also explore the partnerships that are key to success.
You’ll leave this session certainly understanding what Product Owner Excellence looks like and how crucial it is for team success.
This session is relevant for all the attendees including who are new to the field.
Who is Bob Galen?
Bob Galen is an Agile Practitioner, Trainer & Coach based in Cary, NC. In this role he helps guide companies and teams in their pragmatic adoption and organizational shift towards agile methods of working. Bob has been doing that since the late 1990s, so he’s deeply experienced.
He is the Director of Agile Practice at Zenergy Technologies, a leading business agility transformation company. Bob is also President and Head Coach at RGCG a boutique agile coaching firm.
Bob regularly speaks at international conferences and professional groups on topics related to agile software development, testing, scaling, and organizational leadership. He is a Certified Enterprise Coach (CEC), CAL I trainer, and an active member of the Agile & Scrum Alliances.
He’s published three agile-centric books: The Three Pillars of Agile Quality and Testing in 2015, Scrum Product Ownership, 3’rd Edition in 2019, and Agile Reflections in 2012. He’s also aprolific writer & blogger (at – www.rgalen.com ) and podcaster (at www.meta-cast.com )
Bob may be reached directly at: email@example.com