Multiple project management methodologies and frameworks have been followed, with newer ones—some facing resistance depending on the degree of cultural challenges—being adopted by organizations. This article will look at some of today’s key PM methodologies and frameworks.
Scrum has two stable states--ready and done--that are linked to user stories. Do you know what the "Definition of Ready" is?
A retrospective meeting is for betterment, learning, problem solving and celebrating team achievements during sprint execution and review; they should have a motivating approach. Yet so often, they don't.
In a pure Scrum environment, the project manager's responsibilities are reallocated to the newly introduced roles of Development Team, ScrumMaster and Product Owner. In a hybrid Scrum environment, the project manager role may still exist--but likely in a significantly altered form. PMs need to take the impact of this change on their role and responsibilities into consideration…and plan accordingly.
We've covered certain challenges a project manager is likely to face when a Scrum transition is first being evaluated, and a comparison between Waterfall and Scrum methodologies. Part 2 of this article covers the ScrumMaster and Product Owner roles in the Scrum environment--and also addresses the project manager’s role during and after an organization's transition to Scrum.
Ever encounter people who consider themselves “victims” of the agile process? They are competent contributors, managers and project managers who never asked for agile, have had no say in its implementation and hate going through its motions. What can you do to cheer them up?
Have you ever entered a sprint taking on a user story that you later regretted? What can be done to prevent this frustration? Is there a technique that will prevent this from happening, or are these teams doomed to keep repeating their mistakes?
|
Egotism is the anesthetic that dulls the pain of stupidity. - Frank Leahy |
