| |
| |
Acknowledgment | |
| |
| |
Introduction | |
| |
| |
A Quick Read | |
| |
| |
A Short History Provides Context | |
| |
| |
Agile Manifesto and Agile Principles Set Up Agile Methods | |
| |
| |
Project Development Lifecycle Covers Business Case-to-Business Delivery | |
| |
| |
Some Terminology to Make the Reading Easier | |
| |
| |
Plan-driven Provides Lessons Learned | |
| |
| |
Four Agile Methodologies Are Representative | |
| |
| |
The Spiral Methodology Is a Risk Reducer | |
| |
| |
Summary and Takeaway Points | |
| |
| |
The Agile Business Case | |
| |
| |
The Business Case Adds Value to the Project | |
| |
| |
Business Value Models Are the Setup for the Business Case | |
| |
| |
Project Balance Sheet Helps Communicate with the Business Decision Makers | |
| |
| |
The Agile Business Case Is Built by Levels | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Quality in the Agile Space | |
| |
| |
Quality Is Built Around Values, Principles, and Practices | |
| |
| |
Thought Leaders Set Up Agile Quality Values and Principles | |
| |
| |
Quality Values and Principles Are Planned into the Agile Methods | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Managing Test | |
| |
| |
Principles and Practices Guide Testing-in Quality | |
| |
| |
Test-driven Development Is the Starting Point | |
| |
| |
Test Planning Is Essential to Good Test Metrics | |
| |
| |
Testing by Sampling Conserves Time and Money | |
| |
| |
Testing a Hypothesis Builds Confidence | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Developing the Scope and Requirements | |
| |
| |
The Most Affordable Scope Is a Best Value | |
| |
| |
Vision Is the Beginning | |
| |
| |
An Agile Partnership with the Customer Is Built on Rights and Responsibilities | |
| |
| |
There Is a Process for Requirements | |
| |
| |
Teams Work with Stories, Models, and Prototypes | |
| |
| |
WBS Is a Tool for Organizing Scope | |
| |
| |
Manage Scope Emergence with the Planning Horizon | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Planning Cost and Schedule | |
| |
| |
It's Agile! Why Plan? | |
| |
| |
Make Agile Plans for Agile Projects | |
| |
| |
Time Boxes Are the Building Blocks of Schedules in the Agile Space | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Estimating Cost and Schedule | |
| |
| |
The Character of Estimates Affect Predictability | |
| |
| |
Scope, Complexity, and Velocity Drive All Estimates | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Teams Are Everything | |
| |
| |
Teams Are Formed from Social Units | |
| |
| |
Principles and Values Guide Teams | |
| |
| |
Teams Are Building Blocks in the Agile Project | |
| |
| |
Some Teams Work; Others Do Not | |
| |
| |
Matrix Management Manages Resources in the Agile Space | |
| |
| |
Agile Teams Recruit their Members | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Governance | |
| |
| |
Governance Is Built on Quality Principles | |
| |
| |
Governance Verifies Compliance | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Earning Value | |
| |
| |
Defining Value | |
| |
| |
Accounting for Value | |
| |
| |
Earned Value Is Earning Back the Investment | |
| |
| |
Value Is Earned at Every Agile Release | |
| |
| |
Plan, Do, Check, and Act at Every Release | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Scaling Up and Contracting | |
| |
| |
Scale Amplifies Every Problem | |
| |
| |
Networks Enable Large Scale | |
| |
| |
Virtual Teams Expand Throughput | |
| |
| |
Agile-by-Contract Enables Scale | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Benefit Realization | |
| |
| |
Benefits Are Part of the Plan | |
| |
| |
Measuring Results Drives Improvements | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Methodologies | |
| |
| |
The SCRUM Methodology Is Management-centric | |
| |
| |
Extreme Programming Is Disciplined | |
| |
| |
Crystal Methodology Is Human Powered | |
| |
| |
EVO Methodology Is PDCA-centric | |
| |
| |
Summary and Takeaway Points | |
| |
| |
Glossary | |
| |
| |
References | |
| |
| |
Index | |