Skip to main content
Rephrase the title
Link
Tiago Cardoso
  • 8.7k
  • 6
  • 31
  • 73

Is thisan anti agile-Agile pattern to commit to the total hours of capacity available during iteration?

Source Link
bobo2000
  • 3.9k
  • 1
  • 29
  • 49

Is this anti agile?

Working on a project right now that is using Scrum, the company is doing the following:

  1. Working out the availability of the team based on resources available and number of hours they can commit?

So if we have 5 resources available, the total number of hours they can all commit is added up.

  1. Create a sprint backlog based on the total number of hours they can commit

  2. Expect resources to deliver in that amount of time.

I have suggested this is anti scrum agile since the capacity is based on the average amount of time completed in x time. i.e. only because you have 37 hours worth of resources available does not mean you can get 37 hours worth of work done. Am I correct?