By Craig Larman
Larman outlines the foundations and most sensible practices of iterative, evolutionary, and agile methods to software program improvement that emphasize collaboration and suppleness, illustrates these practices in an instance procedure for monitoring immigrants, and overviews the paintings items and middle practices of the Scrum technique, severe programming, the unified strategy, and evolutionary venture administration (Evo).
Read or Download Agile and Iterative Development (Agile Software Development Series): A Manager's Guide PDF
Best programming books
Are you a relative newcomer to iPhone and iPad? or even an previous hand trying to find a e-book with Objective-C that digs deep into Apple’s most recent iOS SDK? Then extra iPhone improvement with Objective-C is for you. Authors Dave Mark, Jayant Varma, Jeff LaMarche, Alex Horovitz, and Kevin Kim clarify recommendations as merely they can—with code snippets you could customise and use, as you're keen on, on your personal apps.
Всем желающим получить глубокие знания о Microsoft workplace 2007 и, возможно, в дальнейшем получить сертификат, в помощь эта книга.
- Programming C# 4.0, 6th Edition: Building Windows, Web, and RIA Applications for the .NET 4.0 Framework
- Parallele und verteilte Programmierung (Springer-Lehrbuch) (German Edition)
- Programming Languages: A Grand Tour
- Game Development with Swift
- Integer Programming and Related Areas A Classified Bibliography 1976–1978: Compiled at the Institut für Ökonometrie und Operations Research, University of Bonn
- Palm & Pocket PC Programming
Extra info for Agile and Iterative Development (Agile Software Development Series): A Manager's Guide
In another study [Jones00], 47 factors that increase or decrease productivity were identified, including project complexity: 55 56 productivity was measured in function points per person-month This indicates a productivity advantage by organizing projects in low-complexity mini-project iterations. To reiterate the results of a study on productivity and iterative development [MKCC03], their conclusion was, In this study, we find that releasing [the result of an iteration] at an earlier stage of development appears to contribute to both a lower defect rate and higher productivity.
As with up-front specifications, it isn't that IID practitioners wouldn't welcome reliable up-front estimates and schedules. But in domains of high change, complexity, and novelty, it is premature, risky, and unrealistic. Adaptive risk-driven or client-driven planning implies the scheduling of goals to iterations can and should change as better information and new priorities arise. 45 46 predictive planning risk- and client-driven planning Still, the demand for premature up-front commitments happens all the time.
Standards-body evidence In the 1980s the USA Department of Defense promoted a waterfall lifecycle in DOD-STD-2167. It was associated with high failure rates. In 1987 a recommendation was made to prefer iterative and evolutionary methods. This occurred in 1994 with the adoption of MIL-STD-498. NATO, the FDA, and other bodies have similar stories. Expert thought leader evidence Many prominent software engineering thought leaders have recommended avoiding the waterfall and adopting iterative development, including Harlan Mills, Frederick Brooks, Barry Boehm, James Martin, Tom DeMarco, Ed Yourdon, and more.