Re: [scrumdevelopment] Re: Scrum training
- On 6/1/07, Roman Pichler <roman.pichler@...> wrote:
Judging from my experience, most product owners need additional
knowledge and skills to do their job effectively. The CSM class
primarily focuses on the skills necessary for ScrumMasters. I have
trained product owners using dedicated training classes, workshops
and boot camps. I also frequently recommended self-study, e.g., by
reading Mike Cohn's excellent book on user stories. It depends on
what is most helpful for the people involved and how much exposure
the individuals have had to Scrum.
To Roman's excellent advice I would suggest start with your CSM, Mike's book on User Stories, Mike's presentation: "Becoming an Effective Product Owner " (http://www.mountaingoatsoftware.com/presentation_view/47) from the Nov '06 Scrum Gathering.
But as with anything else in Scrum I would use the inspect and adapt process. So take your course, do some reading and check where you're at. If you need more help - we will still be here to answer questions.
Most Popular posts:
Aperture vs. Lightroom - best comparisons
Scrum in a Nutshell or 5 minutes to learn Scrum http://www.notesfromatooluser.com/2006/11/scrum_in_a_nuts.html
Getting Things Done!!! Can't Keep Track of all the tasks you have to do? Need a better Tool to Implement GTD? http://www.notesfromatooluser.com/2006/12/getting_things_.html
- --- In firstname.lastname@example.org, "Peter Hundermark"
> Forgive me if I've missed a previous thread - I did tried to
> Why are there so few Product Owner courses? It seems Ken Schwaber
> Mike Cohn offer 2 or 3 CPO courses per year. A few other CST'soffer
> product owner training. Compare this with about 40 CST's offeringthat
> dozens (hundreds?) of CSM courses annually.
> It strkes me as a little odd that there is an established industry
> churns out thousands of CSM's (many of whom never practise),whilst
> PO's are largely ignored.The need for the product owner varies a lot depending upon whether
> Is there something I don't 'get'?
the software organization is a product type organization (creating
something sold) or an IT organization (creating something used
internally). Many software organizations actually have the role of
the product owner reasonably understood, but have no clue as to how
to really organize a product backlog or how to break stories up into
We offer a course called "Agile Estimation and Analysis For
Developers and Product Owners" see
developer-product-owner) which is a team based approach to analysis
in a Scrum environment. We have found a team based approach to
analysis to be very useful in the same way our team based approach
to teaching Scrum is (Implementing Scrum For Your Team). In other
words, instead of focusing on how to train _a_ project
leader/facilitator (the Scrum Master) or _a_ voice of the customer
(the Product Owner) we find a team based approach to training works
How to fill the role of the product owner itself when it is not
present is typically very different for different organizations. In
many of these cases, once the problem is understood, the team can
usually figure out how to best fill the role better than an outsider.
I find it ironic that a team based approach focuses so much on two
(admittedly key) roles.
CEO, Net Objectives