… Stop it.
|
||||||
|
… Stop it. Good Evening. Retrospective meeting(s) That’s right. The time between Sprints [...] Product Owners come in most shapes and sizes. Some of those shapes and sizes don’t quite fit into the development process – and here’s some suggested points from which you can conclude whether or not you have a dud PO. The P.O. doesn’t come to the Sprint Planning Meeting. To me, there’s not confusion on how to handle incomplete stories – and yet, there is a huge range of different approaches hanging around in the Scrum community.So, I’m going to address some of the common claims being made. Mr. Ronald E Jeffries is trying to drum up support for a certification process for agile developers, because, “Ken Schwaber, co-creator of Scrum, says publicly that perhaps only 25% of Scrum teams get the full benefit of Scrum.” Dramatic title, I know. Well, being Product Owner is a bit like being a head chef. You can either cook the meal yourself, you can order someone to cook it, or you can convince the diner that they don’t really need a meal. A lot is written about the three main roles (or only roles, as some might have it) in scrum. Here are my definitions: Product Owner – The product owner is the filtration and feeder system for the machine, which inputs ideas and outputs a product. I’ve just added a document written by Ternary Software, Inc. to the documents category – you can see it on the right side of the blog. |
||||||
|
Copyright © 2010 Karmængine - All Rights Reserved |
||||||