The Value of Deliverables in Agile Product Management
What is a Deliverable?
A deliverable is a product or service provided to stakeholders, typically measured by the scope of a project. It can be classified as internal (produced for the company) or external (produced for a client or customer). Examples of internal deliverables include timesheets, audit reports, or requirements documents, while external deliverables might be strategy reports or analysis reports.
### Internal Deliverables * Timesheets * Audit reports * Requirements documents ### External Deliverables * Strategy reports * Analysis reports
Deliverables vs. Milestones
While often confused, deliverables and milestones serve different purposes. A milestone marks a significant event in a project, usually tied to a specific date. Deliverables, on the other hand, are the actual products or services provided.
| Milestones | Deliverables |
|---|---|
| Mark significant events | Actual products or services |
| Tied to specific dates | Measured by project scope |
The Purpose of Deliverables
In product management, deliverables serve two primary purposes: communication and governance. They help communicate aspects of product design, such as requirements documents or wireframes, and provide proof of progress for auditing and risk management.
- Communication:
- Requirements documents
- Wireframes
- Governance:
- Auditing
- Risk management
Communicating Deliverables to Stakeholders
When working in regulated industries, deliverables become crucial for governance. Auditors require written records to prove compliance, but this doesn’t necessarily mean lengthy documents. Teams can use alternative formats, like comments in Jira or Confluence pages, to document decisions and changes.
### Alternative Formats * Comments in Jira * Confluence pages
The Agile Clash
So, does documentation clash with agile? Not necessarily. The agile principle prioritizes working software over comprehensive documentation, but this doesn’t mean documentation has no value. By asking “why” and ensuring deliverables serve a purpose, teams can create and format them effectively while maintaining focus on producing working software.
Best Practices
- Start with “why”: Ensure each deliverable serves a purpose.
- Ask questions:
- “Does it add value?”
- “How does it help with product development?”
- Keep it concise: Focus on essential information, rather than comprehensive documentation.
- Use alternative formats: Explore different ways to document decisions and changes.