Frequency
The frequency of internal releases can vary based on the Agile methodology being used, the project's needs, and the organization's preferences.
-
In Scrum,
-
internal releases occur at the end of each sprint, typically every 2 weeks.
-
-
In Kanban,
-
releases can be more continuous, with features or changes being released as they are completed and tested.
-
Roles and responsibilities
Product Owner
The Product Owner plays a central role in internal releases. They are responsible for prioritizing the backlog and deciding which user stories or features are included in each sprint release.
Development Team
The Development Team is responsible for implementing the selected backlog items during the sprint. They code, unit-test, and integrate the features or changes into the product increment. The Development Team ensures that the work meets the Definition of Done (DoD).
Testing/ Quality Assurance Team
Testing/ QA team members are responsible for testing the product increment provided. They create and execute test cases, perform testing, and ensure that the product meets requirements.
Scrum Master
The Scrum Master facilitates the Scrum process and ensures that the team follows Agile practices, helping them remove impediments and facilitate collaboration among team members.
Stakeholders
Stakeholders, including end-users or client representatives, may be involved in reviewing the internal releases. They provide feedback on the delivered functionality and help validate that it aligns with their requirements and expectations.
Release sign-off
A release review meeting (Scrum Master or Agile Coach facilitate the release review) is held at the end of each sprint to assess whether the release is ready for internal or external distribution. The process includes:
-
PO Confirming that the product increment aligns with the sprint goals and product roadmap.
-
QA/Dev Demonstrating the completed functionality to stakeholders.
-
Test and Release Manager - Reviewing test results and defect reports.
-
Everyone - Discussing any unresolved issues or risks and Collecting feedback from stakeholders.