No Projects

No Projects

#NoProjects - why the IT project delivery model is fundamentally flawed, and the use of one-piece continuous flow as an alternative

622051376c3b381ef1c786036011112d?s=128

Steve Smith

October 27, 2013
Tweet

Transcript

  1. #NoProjects @allankellynet @joshuajames @agilestevesmith

  2. #NoProjects

  3. #NoProjects A project is a fixed amount of time and

    money assigned to deliver a large batch of value-add
  4. #NoProjects Large batch = increased cycle time

  5. #NoProjects #NoProjects Large batch = increased variability

  6. #NoProjects #NoProjects Large batch = increased feedback delays

  7. #NoProjects #NoProjects Large batch = increased risk

  8. #NoProjects #NoProjects Large batch = increased overheads

  9. #NoProjects #NoProjects Large batch = increased inefficiencies

  10. #NoProjects #NoProjects Large batch = increased dissociation

  11. #NoProjects #NoProjects Reinersten: large batches “appear to have scale economies

    that increase efficiency” [PoPDF]
  12. #NoProjects #NoProjects

  13. #NoProjects #NoProjects

  14. #NoProjects Deliver features, not projects #NoProjects