| |
| |
Introduction | |
| |
| |
About This Book | |
| |
| |
Foolish Assumptions | |
| |
| |
Conventions Used in This Book | |
| |
| |
How This Book Is Organized | |
| |
| |
| |
Understanding Agile | |
| |
| |
| |
Being Agile | |
| |
| |
| |
Working in Agile | |
| |
| |
| |
Managing in Agile | |
| |
| |
| |
Ensuring Agile Success | |
| |
| |
| |
The Part of Tens | |
| |
| |
Icons Used in This Book | |
| |
| |
Where to Go from Here | |
| |
| |
| |
Understanding Agile | |
| |
| |
| |
Modernizing Project Management | |
| |
| |
Project Management Needed Makeover | |
| |
| |
The origins of modern project management | |
| |
| |
The problem with the status quo | |
| |
| |
Introducing Agile Project Management | |
| |
| |
How agile projects work | |
| |
| |
Why agile projects work better | |
| |
| |
| |
The Agile Manifesto and Principles | |
| |
| |
Understanding the Agile Manifesto | |
| |
| |
Outlining the Four Values of the Agile Manifesto | |
| |
| |
Value 1: Individuals and interactions over processes and tools | |
| |
| |
Value 2: Working software over comprehensive documentation | |
| |
| |
Value 3: Customer collaboration over contract negotiation | |
| |
| |
Value 4: Responding to change over following a plan | |
| |
| |
Defining the 12 Agile Principles | |
| |
| |
Agile principles of customer satisfaction | |
| |
| |
Agile principles of quality | |
| |
| |
Agile principles of teamwork | |
| |
| |
Agile principles of project management | |
| |
| |
Adding the Platinum Principles | |
| |
| |
Resisting formality | |
| |
| |
Thinking and acting as a team | |
| |
| |
Visualizing rather than writing | |
| |
| |
Changes as a Result of Agile | |
| |
| |
The Agile Litmus Test | |
| |
| |
| |
Why Agile Works Better | |
| |
| |
Evaluating Agile Benefits | |
| |
| |
How Agile Approaches Beat Historical Approaches | |
| |
| |
Greater flexibility and stability | |
| |
| |
Reduced nonproductive tasks | |
| |
| |
Higher quality, delivered faster | |
| |
| |
Improved team performance | |
| |
| |
Tighter project control | |
| |
| |
Faster and less costly failure | |
| |
| |
Why People Like Agile | |
| |
| |
Executives | |
| |
| |
Product development and customers | |
| |
| |
Management | |
| |
| |
Development teams | |
| |
| |
| |
Being Agile | |
| |
| |
| |
Agile Frameworks | |
| |
| |
Diving Under the Umbrella of Agile Approaches | |
| |
| |
Reviewing the Big Three: Lean, Extreme Programming, and Scrum | |
| |
| |
An overview of lean | |
| |
| |
An overview of extreme programming | |
| |
| |
An overview of scrum | |
| |
| |
Putting It All Together | |
| |
| |
| |
Putting Agile into Action: The Environment | |
| |
| |
Creating the Physical Environment | |
| |
| |
Collocating the team | |
| |
| |
Setting up a dedicated area | |
| |
| |
Removing distractions | |
| |
| |
Going mobile | |
| |
| |
Low-Tech Communicating | |
| |
| |
High-Tech Communicating | |
| |
| |
Choosing Tools | |
| |
| |
The purpose of the tool | |
| |
| |
Organizational and compatibility constraints | |
| |
| |
| |
Putting Agile into Action: The Behaviors | |
| |
| |
Establishing Agile Roles | |
| |
| |
Development team | |
| |
| |
Product owner | |
| |
| |
Scrum master | |
| |
| |
Stakeholders | |
| |
| |
Agile mentor | |
| |
| |
Establishing New Values | |
| |
| |
Commitment | |
| |
| |
Focus | |
| |
| |
Openness | |
| |
| |
Respect | |
| |
| |
Courage | |
| |
| |
Changing Team Philosophy | |
| |
| |
Cross-functionality | |
| |
| |
Self-organization | |
| |
| |
Self-management | |
| |
| |
Size-limited teams | |
| |
| |
Mature behavior | |
| |
| |
| |
Working in Agile | |
| |
| |
| |
Defining the Product Vision and Product Roadmap | |
| |
| |
Planning in Agile | |
| |
| |
Planning as necessary | |
| |
| |
Inspect and adapt | |
| |
| |
Defining the Product Vision | |
| |
| |
Step 1: Developing the product objective | |
| |
| |
Step 2: Creating a draft vision statement | |
| |
| |
Step 3: Validating and revising the vision statement | |
| |
| |
Step 4: Finalizing the vision statement | |
| |
| |
Creating a Product Roadmap | |
| |
| |
Step 1: Identifying product requirements | |
| |
| |
Step 2: Arranging product features | |
| |
| |
Step 3: Estimating and ordering the product's features | |
| |
| |
Step 4: Determining high-level time frames | |
| |
| |
Saving your work | |
| |
| |
| |
Planning Releases and Sprints | |
| |
| |
Refining Requirements and Estimates | |
| |
| |
What is a user story? | |
| |
| |
Steps to create a user story | |
| |
| |
Breaking down requirements | |
| |
| |
Estimation poker | |
| |
| |
Affinity estimating | |
| |
| |
Release Planning | |
| |
| |
Completing the product backlog | |
| |
| |
Creating the release plan | |
| |
| |
Sprint Planning | |
| |
| |
The sprint backlog | |
| |
| |
The sprint planning meeting | |
| |
| |
| |
Working Through the Day | |
| |
| |
Planning the Day: The Daily Scrum | |
| |
| |
Tracking Progress | |
| |
| |
The sprint backlog | |
| |
| |
The task board | |
| |
| |
Agile Roles Within the Sprint | |
| |
| |
Creating Shippable Functionality | |
| |
| |
Elaborating | |
| |
| |
Developing | |
| |
| |
Verifying | |
| |
| |
Identifying roadblocks | |
| |
| |
The End of the Day | |
| |
| |
| |
Showcasing Work and Incorporating Feedback | |
| |
| |
The Sprint Review | |
| |
| |
Preparing to demonstrate | |
| |
| |
The sprint review meeting | |
| |
| |
Collecting feedback in the sprint review meeting | |
| |
| |
The Sprint Retrospective | |
| |
| |
Planning for retrospectives | |
| |
| |
The retrospective meeting | |
| |
| |
Inspecting and adapting | |
| |
| |
| |
Preparing for Release | |
| |
| |
Preparing the Product for Deployment: The Release Sprint | |
| |
| |
Preparing the Organization for Product Deployment | |
| |
| |
Preparing the Marketplace for Product Deployment | |
| |
| |
| |
Managing in Agile. | |
| |
| |
| |
Managing Scope and Procurement | |
| |
| |
What's Different About Scope in Agile | |
| |
| |
How to Manage Scope in Agile | |
| |
| |
Understanding scope throughout the project | |
| |
| |
Introducing scope changes | |
| |
| |
Managing scope changes | |
| |
| |
Using agile artifacts for scope management | |
| |
| |
What's Different About Procurement in Agile | |
| |
| |
How to Manage Procurement in Agile | |
| |
| |
Determining need and selecting a vendor | |
| |
| |
Contracts and cost approaches for services | |
| |
| |
Organizational considerations for procurement | |
| |
| |
Working with a vendor | |
| |
| |
Closing a contract | |
| |
| |
| |
Managing Time and Cost | |
| |
| |
What's Different About Time in Agile | |
| |
| |
How to Manage Time in Agile | |
| |
| |
Introducing velocity | |
| |
| |
Monitoring and adjusting velocity | |
| |
| |
Managing scope changes from a time perspective | |
| |
| |
Managing time by using multiple teams | |
| |
| |
Using agile artifacts for time management | |
| |
| |
What's Different About Cost in Agile | |
| |
| |
How to Manage Cost in Agile | |
| |
| |
Creating an initial budget | |
| |
| |
Creating a self-funding project | |
| |
| |
Using velocity to determine long-range costs | |
| |
| |
Using agile artifacts for cost management | |
| |
| |
| |
Managing Team Dynamics and Communication | |
| |
| |
What's Different About Team Dynamics in Agile | |
| |
| |
How to Manage Team Dynamics in Agile | |
| |
| |
Becoming self-managing and self-organizing | |
| |
| |
Supporting the team: The servant-leader | |
| |
| |
Working with a dedicated team | |
| |
| |
Working with a cross-functional team | |
| |
| |
Establishing an agile environment | |
| |
| |
Limiting development team size | |
| |
| |
Managing projects with dislocated teams | |
| |
| |
What's Different About Communication in Agile | |
| |
| |
How to Manage Communication in Agile | |
| |
| |
Understanding agile communication methods | |
| |
| |
Status and progress reporting | |
| |
| |
| |
Managing Quality and Risk | |
| |
| |
What's Different About Quality in Agile | |
| |
| |
How to Manage Quality in Agile | |
| |
| |
Quality and the sprint | |
| |
| |
Proactive quality | |
| |
| |
Quality through regular inspecting and adapting | |
| |
| |
Automated testing | |
| |
| |
What's Different About Risk in Agile | |
| |
| |
How to Manage Risk in Agile | |
| |
| |
Reducing risk inherently | |
| |
| |
Identifying, prioritizing, and responding to risks | |
| |
| |
| |
Ensuring Agile Success | |
| |
| |
| |
Building a Foundation | |
| |
| |
Commitment of the Organization and of Individuals | |
| |
| |
Organizational commitment | |
| |
| |
Individual commitment | |
| |
| |
How to get commitment | |
| |
| |
Will it be possible to make the transition? | |
| |
| |
What is the best timing for moving to agile? | |
| |
| |
Choosing the Right Project Team Members | |
| |
| |
The development team | |
| |
| |
The scrum master | |
| |
| |
The product owner | |
| |
| |
The agile champion | |
| |
| |
The agile mentor | |
| |
| |
The project stakeholders | |
| |
| |
Creating an Environment That Works for Agile | |
| |
| |
Support Agile Initially and Over Time | |
| |
| |
| |
Being a Change Agent | |
| |
| |
Making Agile Work in Your Organization | |
| |
| |
Step 1: Conduct an implementation strategy | |
| |
| |
Step 2: Establish a transformation team | |
| |
| |
Step 3: Build awareness and excitement | |
| |
| |
Step 4: Identify a pilot project | |
| |
| |
Step 5: Identify success metrics | |
| |
| |
Step 6: Train sufficiently | |
| |
| |
Step 7: Develop a product strategy | |
| |
| |
Step 8: Develop the product roadmap, the product backlog, and estimates | |
| |
| |
Step 9: Running your first sprint | |
| |
| |
Step 10: Make mistakes, gather feedback, and improve | |
| |
| |
Step 11: Mature | |
| |
| |
Step 12: Scale virally | |
| |
| |
Avoiding Pitfalls | |
| |
| |
Questions to Prevent Problems | |
| |
| |
| |
The Part of Tens | |
| |
| |
| |
Ten Key Benefits of Agile Project Management | |
| |
| |
Better Product Quality | |
| |
| |
Higher Customer Satisfaction | |
| |
| |
Higher Team Morale | |
| |
| |
Increased Collaboration and Ownership | |
| |
| |
Customized Team Structures | |
| |
| |
More Relevant Metrics | |
| |
| |
Improved Performance Visibility | |
| |
| |
Increased Project Control | |
| |
| |
Improved Project Predictability | |
| |
| |
Reduced Risk | |
| |
| |
| |
Ten Key Metrics for Agile Project Management | |
| |
| |
Sprint Goal Success Rates | |
| |
| |
Defects | |
| |
| |
Total Project Duration | |
| |
| |
Time to Market | |
| |
| |
Total Project Cost | |
| |
| |
Return on Investment | |
| |
| |
New Requests Within ROI Budgets | |
| |
| |
Capital Redeployment | |
| |
| |
Satisfaction Surveys | |
| |
| |
Team Member Turnover | |
| |
| |
| |
Ten Key Resources for Agile Project Management | |
| |
| |
Agile Project Management For Dummies Online Cheat Sheet | |
| |
| |
The Agile Alliance | |
| |
| |
The Scrum Alliance | |
| |
| |
The Project Management Institute Agile Community | |
| |
| |
Agile Leadership Network | |
| |
| |
Scrum Development Yahoo! Group | |
| |
| |
InfoQ | |
| |
| |
Lean Essays | |
| |
| |
What Is Extreme Programming? | |
| |
| |
Platinum Edge | |
| |
| |
Index | |