Articles I've written
Take a Seat, Please
OK, the decision has been made that you are moving to Agile/Scrum from a more traditional method, most likely Waterfall. Agile has three clearly defined roles: product owner, ScrumMaster, and team. In this new framework, then, who gets to do what?
But That Trick Never Works!
I believe in being pragmatic. I don't so much see Scrum as a set of rules but rather as guidelines. In short, I like to do things because they make sense. . . .
The Importance of Being Earnest
It is in our nature as IT professionals to be bound by facts and formulas. Little wonder, then, that we often find ourselves judging the success of a project based on a wide array of metrics and reports. Particularly as project managers, we find ourselves immersed in the data as opposed to watching what is truly occurring. Is it possible that the more importance we place upon reporting, the more we distance ourselves from the true benefits of adopting the Scrum method?
Has Anyone Seen My Product Owner?
As the key stakeholder within the Scrum framework, the product owner is an essential player in ensuring that a relevant and quality solution is delivered. Typically, the product owner role is performed by the product manager, who has the vision and understanding of the end-user requirements to be able to effectively direct the team. If you find yourself working on a project with an "absent" product owner, or with a weak or ineffective product owner, then it is time to speak up.