Scrum has come to Canberra and along with it Product Owners. It has been growing for a few years but now just about every Federal Government Agency have Product Owners running around. However, they are still facing the classic issue of how do you empower a Product Owner in such a hierarchical and inflexible organisation?

We’ve all seen it, the Product Owner who can’t make a decision without a committee or approval from above. Let’s break the pattern! Or should I say anti-pattern.

In this session you will learn about:

  • How a Product Owner differs in Government
  • What anti-pattern indicators are out there for Product Owners
  • How as a Product Owner you can break free of these disempowering anti-patterns
  • How to enable Product Owners in your team

 

 
 

Outline/Structure of the Presentation

  • Introduction
  • The challenges and impact of Government on Scrum
  • Interactive audience poll 
  • A Government Product Owner
  • The cost of time and lack of empowerment
  • Early indicators of anti-patterns for Product Owners
  • How to break free as a Product Owner
  • How to enable your Product Owner to break free
  • The future of Product Ownership in Government
  • Remaining time Q&A

Learning Outcome

Participants will learn:

  • The impacts Government organisations have on the Scrum Framework
  • How a Product Owner differs in Government
  • How much of impact disempowerment can have on the bottom line
  • What anti-pattern indicators are out there for Product Owners
  • How as a Product Owner you can break free of these disempowering anti-patterns
  • How to enable Product Owners in your team

Target Audience

Product Owners, Agile Coaches, Scrum Masters, Team Leaders, Government employees

Prerequisites for Attendees

Participants should have a:

  • Basic understanding of the Scrum Framework 
  • Basic understanding of the Product Owner role and responsibilities 
schedule Submitted 6 months ago

  • Craig Smith
    keyboard_arrow_down

    Craig Smith / Michael Huynh - Have we Outgrown the Scrum Master and Product Owner Roles?

    40 Mins
    Workshop
    Intermediate

    The Scrum Master and Product Owner roles (along with the developers) are well understood and described in the Scrum Guide. As organisations begin to mature and scale, a lot of anti patterns start to emerge with these roles, as well as adding traditional roles (such as change, release and project management) and additional agile roles (such as Agile Coach and Release Train Engineer). Given the simplicity of the three roles in the Scrum Guide for a single team versus the challenges of scaling, do we need to take another look at the key roles to help solve the confusion that so many organisations continue to face?

    Join us as we ponder the question of whether we have outgrown the roles of Scrum Master and Product Owner or whether we just need more clarity on what these roles actually mean in the context of true business agility. 

help