Projects with Shared Resources in Agile Teams

Written by admin

February 1, 2019

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

Project Management with Agile Teams

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

Product Management with Agile Teams

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?


You might also like…

getKanban – Experiential Kanban board game

getKanban – Experiential Kanban board game

Either you want to switch for your current way of working to Kanban, or you want to map some Kanban principles on your current way of working, this game is a great way to find out what fits you the best.

Organizing a process improvement workshop inspired by the Lencioni model

Organizing a process improvement workshop inspired by the Lencioni model

A team asked for a product discovery workshop. After addressing few upfront questions, I realized very fast that their poor and unpredictable velocity is not caused by uncertainty on the product level; it was the foundation that was actually missing – the absence of trust on the team level (Lencioni’s 5 Dysfunctions of a team).

The road to Lean HR

The road to Lean HR

One example of Value Stream is “Recruiting for new employees”. The trigger is clear, there is a need for a “Java Developer”. The end of the Value Stream is “java developer available”.



  1. Coaching for Scrum of Scrums - Agile Minds - […] Today I had the opportunity to coach the Scrum of Scrums for 5 Scrum Masters that deliver with their…

Submit a Comment

Your email address will not be published. Required fields are marked *