Project vs. Product
Projects break Agile. The whole mindset behind starting and stopping a PROJECT results in the opposite of what we’re attempting to achieve using Agile approaches for a PRODUCT. The two words might sound similar, and mistakenly be used interchangably, but they are very different approaches.
Key Difference
Project-based approaches are to get the money, start the project, and bring the resources (not even people) to the project. In contrast, Agile approaches focus on building teams. First build an effective team, and then bring the work to the team to build a product.
| Project Mindset | Product Mindset |
|---|---|
| Fixed scope with variable resources and time | Fixed team (not resources) with variable scope (aka a Product Backlog) |
| Focus on completion and hand-off | Continuous evolution and value creation |
| Temporary teams and part-time team members | Stable teams with domain and technical knowledge |
| Fixed upfront budget | Continuous funding based on value |
| Limited stakeholder involvement | Ongoing stakeholder collaboration |
| Success is measured by time and budget adherence | Success is measured by problem-solving and usage |
| Difficult to maintain what you build | Maintenance is built into the process |
| Complicates forecasting | Forecasts based on historical data |
| Leads to multi-tasking and increased use of specialists | Eliminates multi-tasking |
| Deliver value at the end of the project | Deliver value as early and often as possible |
Agile Pain Relief Blog Entries
- In organizations that are struggling to break free of the Project based approach, consider Portfolio Management
- In Agile, Where Change is Valued, Why Is a Stable Team So Important?
- Specialists Are Overrated
- Speed Trap: How the Obsession with Speed is Building a Fragile Organization - Organizations that remain stuck in the Project approach are more Fragile.