This text explains how agile software development methods produce better business results. It aims to help managers combat the biggest business complaints about software (for example, late, doesn't deliver as promised, over-budget and so forth). This text explains how agile software development methods produce better business results. It aims to help managers combat the biggest business complaints about software (for example, late, doesn't deliver as promised, over-budget and so forth).
Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results
Availability:
Ready to download
This text explains how agile software development methods produce better business results. It aims to help managers combat the biggest business complaints about software (for example, late, doesn't deliver as promised, over-budget and so forth). This text explains how agile software development methods produce better business results. It aims to help managers combat the biggest business complaints about software (for example, late, doesn't deliver as promised, over-budget and so forth).
Compare
Nathalie Karasek –
Very interesting, connecting and comparing different agile methods, TOC and also traditional methods. Giving a lot of information about “numbers” like metrics and finance. An “Agile Management handbook”.
Ciprian Dobre-Trifan –
A valiant attempt at making software development less of an art and more of a science, by employing ToC metrics. I liked the translation of ToC concepts into the world of software. Also some very interesting ideas for metrics and nice comparisons of some known agile methodologies. Advocating FDD quite a lot.
Collin Rogowski –
Very thorough book about applying the theory of constraints to agile processes. It's becoming a bit dated (which shows e.g. in the choice of agile process presented), but everything in it is still valid. The reasoning/argumentation is very rigid and formal which is not that common in agile literature. In this regards it (still) fills a gap, IMO. Very thorough book about applying the theory of constraints to agile processes. It's becoming a bit dated (which shows e.g. in the choice of agile process presented), but everything in it is still valid. The reasoning/argumentation is very rigid and formal which is not that common in agile literature. In this regards it (still) fills a gap, IMO.
gramakri –
This is one of the first few books on Agile which goes beyond presenting the anecdotal benefits of Agile and discusses the business metrics which can be used to quantify the ROI. Read more about this book in my Professional Blog. This is one of the first few books on Agile which goes beyond presenting the anecdotal benefits of Agile and discusses the business metrics which can be used to quantify the ROI. Read more about this book in my Professional Blog.
Jack Vinson –
Good stuff. More software development methodology than I need, but I really enjoyed the connections between Theory of Constraints and Agile. And I blogged a review, of course. https://www.jackvinson.com/blog/2012/... Good stuff. More software development methodology than I need, but I really enjoyed the connections between Theory of Constraints and Agile. And I blogged a review, of course. https://www.jackvinson.com/blog/2012/...
Michael Sorensen –
JC Plessis –
Eric Brasch –
Sergio Villagra –
Kristjan –
Kurt –
Øystein –
Dariusz Debowczyk –
Raman Ohri –
João Jesus –
Bob Schatz –
Karuppiah –
Chris Hefley –
Anju M –
Zan Kavtaskin –
Brian –
Kashuo –
Mike Rodbell –
Celio Pontes –
Seth Thomson –
Khurram Ch –
Biyi Akinpelu –
What Bird Is That? –
Kristian –
Alberto –