David J. Anderson explains how to use predictability, measurement and change management to balance the factors of observed capability, staffing, and delivery targets to achieve predictable outcomes.
David J. Anderson is the author of "Agile Management for Software Engineering", a signatory of the PM Declaration of Interdependence and a founder of the APLN, an original member of the "Singapore Project" where Feature Driven Development emerged, and vice president of the Lean Software and Systems Consortium.
Agile Cambridge 2011 is for anyone who wants to successfully apply or learn more about Adopting and evolving agile approaches; Agile software development; Agile product management; Agile testing; DevOps/Agile Operations; User experience and design in an agile world; Agile technical communications; Coaching and mentoring agile teams; Leadership; Tool and technology adoption; Distributed agile teams. The focus throughout the event is on sharing practical experience of these topics, in a range of sessions from beginner to expert.
Just want to clarify the sigma values
I am not sure where are the sigma values come from, you mentioned in your presentation:
1 sigma = 85%
2 sigma = 98%
But based on my understanding of standard deviation, en.wikipedia.org/wiki/Standard_deviation
1 sigma = 68%
2 sigma = 95%
Importance of velocity
Your presentation is great and asnwers many of the problems I see happening in IT projects.