About the Book
Please note that the content of this book primarily consists of articles available from Wikipedia or other free sources online. Pages: 56. Chapters: The Mythical Man-Month, Homesteading the Noosphere, Feature creep, Ninety-ninety rule, Lead programmer, Agile software development, Scrum, Software development effort estimation, Dual Vee Model, IBM Tivoli Unified Process, Use case, Rapid application development, Misuse case, V-Model, IBM Rational Unified Process, Brooks's law, Software product management, Brownfield, Planning poker, Project triangle, VersionOne, Baseline, SharpForge, Application lifecycle management, MKS Integrity, No Silver Bullet, Release management, Death march, Issue Log, MoSCoW Method, Conway's Law, Timeboxing, Release engineering, Team programming, Endeavour Software Project Management, Enterprise Unified Process, Software factory, Software Peter principle, Multiagent systems product lines, Essential complexity, Software product line, Comparison of development estimation software, Tracking questionnaire, Agile Modeling, Gold plating, Offshore custom software development, Peopleware: Productive Projects and Teams, Programming team, RATF, Top Development, Software Development Folder, Accidental complexity, Metaprogramming, Bus number, Simple matter of software, Merge window, Chief programmer team, NNPP, SAIV. Excerpt: Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. The Agile Manifesto introduced the term in 2001. Agile management methods can also be applied in other development projects than software development. Jeff Sutherland, one of the developers of the Scrum agile software development processIncremental software development methods have been traced back to 1957. In 1974, a paper by E. A. Edmonds introduced an adaptive software development process. So-call...