no projects

14
#NoProjects @allankellynet @joshuajames @agilestevesmith

Upload: steve-smith

Post on 18-Nov-2014

697 views

Category:

Technology


0 download

DESCRIPTION

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

TRANSCRIPT

Page 1: No Projects

#NoProjects

@allankellynet @joshuajames @agilestevesmith

Page 2: No Projects

#NoProjects

Page 3: No Projects

#NoProjects

A project is a fixed amount of time and money assigned to deliver a large batch of value-add

Page 4: No Projects

#NoProjects

Large batch = increased cycle time

Page 5: No Projects

#NoProjects#NoProjects

Large batch = increased variability

Page 6: No Projects

#NoProjects#NoProjects

Large batch = increased feedback delays

Page 7: No Projects

#NoProjects#NoProjects

Large batch = increased risk

Page 8: No Projects

#NoProjects#NoProjects

Large batch = increased overheads

Page 9: No Projects

#NoProjects#NoProjects

Large batch = increased inefficiencies

Page 10: No Projects

#NoProjects#NoProjects

Large batch = increased dissociation

Page 11: No Projects

#NoProjects#NoProjects

Reinersten: large batches “appear to have scale economies that increase efficiency” [PoPDF]

Page 12: No Projects

#NoProjects#NoProjects

Page 13: No Projects

#NoProjects#NoProjects

Page 14: No Projects

#NoProjects

Deliver features, not projects

#NoProjects