Presentation on theme: "Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com."— Presentation transcript:
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com
Agenda Emergence Tech Training / emergencetechtraining;com What is Release Planning? When does it happen? Team Roles and Responsibilities Using Jira to manage Release Planning Managing your backlog Managing Sprints Closing the Sprint
What is Release Planning? Emergence Tech Training / emergencetechtraining;com In an Agile world release planning provides visibility to upcoming work. Effective release planning provides the team with an ability to work in small increments, enabling strong focus and high quality work. Release Planning in a Nutshell is: Building a Product Backlog – Shared Knowledge Prioritizing the Backlog – Project Plan Continue to ‘groom’ the Backlog – Manage Scope Execute on the Backlog – Build your Product
What is Release Planning Emergence Tech Training / emergencetechtraining;com An ability to derive a project schedule based upon: Total number of Story Points for a particular project or product feature A Scrum Teams historical velocity Assumes that the team has been together for awhile If team is new Risk is associated with the Release Plan until such time as the team velocity hits the estimated velocity. What is Velocity?: The Total number of points that a team can complete within a designated Sprint. Why is Velocity Important? Provides predictability.
When Does it Happen? Emergence Tech Training / emergencetechtraining;com Release Planning happens throughout the project. Pre-Sprint Planning: Build the Product Backlog Estimate Story points to the Stories in the backlog Prioritize work based upon highest value first Set project milestones and expectations via Planning
Team Roles and Responsibilities Emergence Tech Training / emergencetechtraining;com Getting to Release Planning: Discovery – Collaborative effort to build out individual User Stories and Acceptance Criteria. Building Context for your Product/Features. Who? – The entire team Estimation – Story Point stories that are going to be included in the development phase of the project. Who? – The entire team How – Team needs to decide if they will estimate collectively or separately with respect to Dev and QA efforts. Release Planning: Prioritizing the User Stories Who? – Primarily the Product Manager, with input from the the rest of the team.