One experience that keeps coming back to me is how people interpret and adapt Projects in Agile environments. I’m summarizing here my opinion on the disadvantages from getting this done wrong and also a proposed change in the paradigm.
I’m keeping it short, you may add more details in the comments and debate on this.
Project Management approach
Main disadvantages here would be:
- People have multiple backlogs of activities. Bring people to work.
- Prioritization is done decentralized
- Mura Waste is generated: unevenness in an activity; e.g. for the Project you have 2 Months of hard work then, for whatever problems with the budget (in most of the cases), no activity and the people go back to their teams
- Predictability is hard to achieve as the project team is not stable
Product Management approach
Main advantages here would be:
- People are part of One Team, with one Product Owner that sets the priorities. Such a team is self-organized & self-managed, concepts discussed by Daniela in her blog post Leadership in an Agile Environment – no one man’s job
- Teams have One Backlog, so what the team is working should be clear and the predictability also gets better and better
- Project activities are split over different Teams and synchronized between the Product Owners of these teams
- Activities go to Teams’ Backlog, not people to other Teams for the activities. Bring work to people.
What do you think?