- ホーム
- > 洋書
- > 英文書
- > Computer / General
Full Description
Agile Recipes gives you proven ways to quickly drive real value from any Agile/Lean approach in any organization. Influential software innovator Peter Bell first introduces a set of core principles that underlie the effective use of Agile/Lean methods, offering foundational insights on issues ranging from motivation and talent to craftsmanship, constraints, and organizational learning. Next, he presents a series of detailed Agile/Lean pattern-style "recipes" for addressing several of today's most common software development challenges, including: Building the right software Creating effective specifications Minimizing bugs Improving estimates Meeting commitments and handling backlogs Implementing automated testing Managing technical, model, and innovation debts Leading developers more effectively And much more Through realistic examples, Bell explains how and why organizations choose specific Agile patterns to solve specific technical or business problems. Next, he presents a library of detailed patterns, each with a brief explanation, summary of the problems it is designed to solve, step by step instructions for implementing it successfully, and suggestions for enhancing its value once you've done so. Bell's patterns range from story mapping to pairing, user stories to Behavior, Feature, and Acceptance Test-driven development, and he supports them with examples based on common technologies ranging from Java, and .NET to Groovy, Ruby, Python, and PHP.
Contents
Part 1software engineering - the business problem - why BDUF fails - introducing the manifesto - understanding the manifesto Building a foundation - engineering practices - - the scarcity of talent - - the importance of motivation - - craftsmanship - - if only xP wasn't so extreme - Start where you are - - the importance of context (beyond best practices) - - inspect and adapt - - the theory of constraints - - beyond ToC - optimizing the whole - Levels of learning - - shu-ha-ri - - the dreyfus model - - how to use this book Part 2: Recipes - Specifying Software - - What should we build? - - Incremental delivery - - Understanding audiences - - Specifying with stories - - Story decomposition - - Iterative vs incremental delivery - Managing the team - - Estimating - - Managing commitments - - Automated tests - - Debt (technical, model and innovation) - - Getting started with deliberate discovery - - Managing the backlog Part 3: Patterns - Story maps - Limiting WIP - Value stream mapping - Pairing - Time boxed iterations - Regression tests - Scenarios - Behavior Driven Development - Feature Driven Development - User stories - Acceptance Test Driven Development