The Flaw in the Plan / 1: |
The Delusive Perception of Having Anticipated Everything / 1.1: |
Accept the Uncertainty and Adapt / 1.2: |
Involving the Teams / 1.3: |
In Search of Structure / 1.4: |
Agile Software Development / 1.5: |
Further Readings |
Traditional Software Development / 2: |
History of Project Management / 2.1: |
Waterfall Approach / 2.2: |
Requirements / 2.2.1: |
Design Phase / 2.2.2: |
Implementation / 2.2.3: |
Testing / 2.2.4: |
Support / 2.2.5: |
Advantages and Disadvantages / 2.2.6: |
Project Management Triangle / 2.3: |
Modified Waterfall Models / 2.4: |
Milestone and Regular Integration / 2.4.1: |
Incremental Development / 2.4.2: |
Overview of Agile Software Development / 3: |
Lean Software Development / 3.1: |
Project Management 2.0 / 3.2: |
Agile Manifesto / 3.3: |
Scrum / 3.4: |
Test Driven Development / 3.5: |
Extreme Programming / 3.6: |
Rational Unified Process / 3.7: |
Best Practices / 3.7.1: |
The Phases / 3.7.2: |
The Process / 3.7.3: |
Agile Unified Process / 3.8: |
Agile Model Driven Development / 3.9: |
Tooling / 4: |
Project Management Tools / 4.1: |
Microsoft Solutions Framework for Agile Development / 4.1.1: |
Jazz and Rational Team Concert (RTC) / 4.1.2: |
Collaboration Tools / 4.2: |
Development Infrastructure and Environment / 4.3: |
Source Control and Version Management / 4.3.1: |
Automated Test Environment / 4.3.2: |
"Code-Build-Test" / 4.3.3: |
Considerations on Teaming and Leadership / 5: |
A "Lean" Hierarchy / 5.1: |
Selling the Directions: Management by Objectives / 5.2: |
Defining the Goals / 5.3: |
About Trust and Thrust: Culture and Climate / 5.4: |
Cross-functional Teams / 5.5: |
The Wisdom of Crowds / 5.6: |
It Isn't that Easy / 5.7: |
Skills / 5.8: |
Considerations on Planning and Architecture / 6: |
About Requirements, Resources, and Dates / 6.1: |
Agile, a License for Chaos? / 6.2: |
Balance Flexibility and Structure / 6.3: |
Balance the Level of DetailError! Bookmark not defined / 6.3.1: |
Balance the Timing of Decisions / 6.3.2: |
Balance the Need for Commitment / 6.3.3: |
Balance Between Autonomy and Guidance / 6.3.4: |
Balance the Amount of Documentation / 6.3.5: |
Disciplined Agile / 6.3.6: |
Reducing Complexity / 6.4: |
Simplify Prioritization and Planning / 6.4.1: |
Simplify Team Setup and Dependencies / 6.4.2: |
Simplify Tools and Processes / 6.4.3: |
Simplify Daily Life / 6.4.4: |
Architectural Considerations / 6.5: |
Outside-In Design / 6.5.1: |
Requirements, Use Cases, Scenarios, and Tasks / 6.5.2: |
Architectural Attitude / 6.5.3: |
Making Architecture Flexible / 6.5.4: |
Considerations on Project Execution / 7: |
The Big Bang / 7.1: |
Continuous Integration / 7.2: |
The Rhythm of the Project: Iterations / 7.3: |
Integration Fest / 7.4: |
Juggling Content Within an Iteration / 7.5: |
Planning in an Agile Project / 7.6: |
Estimating / 7.7: |
Units often used in Agile Projects / 7.7.1: |
Ways to get to Estimates / 7.7.2: |
Metrics for an Agile Project / 7.8: |
Defects / 7.9: |
Independent Release Testing and Wrap-up / 7.10: |
Involving Customers / 7.11: |
Mix and Match / 8: |
The Tragedy of Being Successful / 8.1: |
About WebSphere Portal / 8.2: |
Which Projects are suitable for Agile Software Development? / 8.3: |
Scaling Agile / 8.4: |
Moving Towards Agile / 8.5: |
Tiger Teams in WebSphere Portal / 8.6: |
Budget-based Prioritization / 8.6.1: |
Cross-Organizational Teaming Structure / 8.6.2: |
Evolving the Product in Iterations / 8.6.3: |
Integrating Test and Development / 8.6.4: |
Designs and Documentation / 8.6.5: |
Managing Tiger Teams / 8.6.6: |
The Benefits and Pain Points / 8.7: |
Summary and Wrap-Up / 9: |
The Essence of Agile / 9.1: |
Building an Agile Community / 9.2: |
Comparing once again / 9.3: |
Index |
The Flaw in the Plan / 1: |
The Delusive Perception of Having Anticipated Everything / 1.1: |
Accept the Uncertainty and Adapt / 1.2: |
Involving the Teams / 1.3: |
In Search of Structure / 1.4: |
Agile Software Development / 1.5: |