7.3.3.1 Release Deliverables*
Release deliverables can include features, products, outputs, or results that are successfully deployed to production or handed off to end users.
Figure 7-14 illustrates an ongoing release as captured in an AI-enabled digital Kanban tool:
Figure 7.14: Sample Ongoing Release (Source: Vabro)
Figure 7-14 above shows the Vabro interface for a software release named "Sample Release," which is currently ongoing and scheduled for completion in 9 days, with a release date of January 31, 2025. It lists two tasks in the "Release Backlog" section: "Sample Task - Setup New Employee Workstation" and "Sample Task - Customer Feedback on Resolved Issue."
7.3.3.2 Release Notes*
In Kanban, releases are continuous and flow-based rather than tied to fixed iterations. This means that release notes must be dynamically maintained and updated as changes are deployed. Since work is released incrementally, release notes serve as an essential communication tool for stakeholders, documenting what has been delivered and any important updates.
Best Practices for Release Notes in Kanban are as follows:
- Automated Generation – Integrate release notes with issue-tracking tools (e.g., Jira, Trello) to pull completed work items automatically.
- Categorization – Organize notes into sections like new features, bug fixes, performance improvements, and security updates for clarity.
- Real-Time Updates – Maintain a continuously updated release notes repository rather than waiting for a big-bang release.
- Clear and Concise Language – Use simple, user-friendly descriptions instead of technical jargon.
- Stakeholder Accessibility – Publish release notes in wikis, dashboards, or notifications to keep users informed.
By integrating release notes into the Kanban Workflow, teams ensure transparency and keep all stakeholders aligned with the latest changes.