These are the slides with synchronised audio of my presentation to the Public Sector Agile SIG based in the Midlands (UK). This was a day focused on the role of the Product Owner and I was asked to complement the more basic “what is a Product Owner” presentations with a “Product Owners in the real world” talk.
This is not a Scrum-only talk as it also includes mentions of Kanban, Agile PM and DSDM.
Any feedback, comments and suggestions will be greatly appreciated.
Let me get this clear. If you want to be a professional Agile Project Manager, going down the Scrum rabbit-hole could well be a mistake. A mistake with lots of ramifications.
Over the past few years, many traditional (PRINCE2) PMs have retrained as Certified Scrum Masters and they will be livid by this statement and ready for a heated argument. So, please allow me to explain what I mean.
One of the problems for an Agile PM is how much, or little, to intervene and when.
As an Agile transformation coach , all the initial emphasis is put on ensuring that PMs are not command and control, not directive and behave like “good chickens” for their team. This is the standard starting point for an Agile PM managing a performing, adult team
However, if things are not going so well, it may be necessary for the PM to change behaviours. After all, the Agile PM is still responsible for delivering the project and managing the risks and issues. From an Agile point of view, this is acceptable, but the level of intervention should be a graduated “ramping up” process, and it needs to be a temporary measure (although changing teams embedded bad behaviours can take some time). It is not a good idea to go straight in at Defcon 1 level.
Some of the coolest discoveries often come as a surprise and today was no exception as I unexpectedly found out a few Google Apps available in the Marketplace that look very slick and useful.