Hitachi Vantara Pentaho Community Wiki
Child pages
  • 14. Sprint Template
Skip to end of metadata
Go to start of metadata


This template is a Wiki Sprint Template (a guideline) - that is to be used when you begin a Sprint. It is required to help consolidate information that would be otherwise scattered in various places.

Purpose - This template will help you keep your sprint content intact and act's as a reusable asset.  It discusses various elements of the Sprint that needs to be shared with the internal and external team.

Sprint Name - Project - Release - Deliverable

 The naming convention of the sprint should follow the following format > Project, Release, Deliverable ie: Ease of Use/3.1/Milestone 1.

Personas

List the name, position, description, their skill set and common tasks. 

Project goals

A list of identified goals for the project. 

User Stories

 A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it.  A good way to think about a user story is that it is a reminder to have a conversation with your customer

Status - Not Started, In Progress, Nearing Completion, Completed

Communication with and among sprint team members and stakeholders, internal and external, must be constant. The project team needs relevant information, in a timely manner, from each of its members to complete and improve the project, and to understand the needs and expectations of project outcomes. Since change is constant in an agile project, constant communication is the only means of maintaining the connections among all the participants. "Going dark" for any significant amount of time is simply not feasible. Project communication management involves planning, information distribution, performance reporting, and formal project close-out. These are the elements a Sprint team must agree to and be facilitated by the Scrum Master.

A scrum (or Sprint) is controlled by means of frequent (daily) inspection of the progress followed by necessary adoptions. Most times this is done face to face. In any Sprint people are going to want to know the progress, the tone and the attitude of the team.

A weekly demo works to allow outside but interested members to see and hear what's the current status.

Current Risks/Blockers

Risk Level

Description

 Status

 Owner

Date last Updated

High





Medium





Low

 

 

 

 



Sprint Description

Sprint Feature Backlog

During the Sprint, that Backlog (JIRA) is fixed and can only be changed as a result of the work being performed in that Sprint. The Backlog which is basically the current requirements (not tasks) list will be publicly available on the project website.

The Backlog outside the current sprint/s is always changing, evolving and being re-prioritized by Product Management. As contributions are accepted from community the Sprint backlog needs to be updated. New requirements need to be prioritized and grouped in some logical order.

In addition to the typical Scrum information the Backlog needs to include a field that describes the extent to which an implemented feature has been hardened and accepted by the community. In order to get peer review and feedback on requirements and design the descriptions in the product back should include (or include references to) requirements and design documentation where possible.To be maintained in JIRA - re-work underway for improvements.

Team

The scope of the Scrum Team will include the community as they will help provide peer review of the design, implementation, testing, documentation, usability feedback etc. If needed, (and possible) the designation 'Core Scrum Team' and 'Extended Scrum Team' may be used.

Identify who's on the team and what is their primary function? Ensure the team understands the Backlog and what are the primary features that are to be coded. Note any vacations or upcoming holiday's that might be a factor during the Sprint.

Daily Scrum Meetings

During the daily scrum each team member provides answers to the following three questions:

  1. What did you do yesterday?
  2. What will you do today?
  3. Are there any impediments in your way?

The Core Scrum Team needs to synchronize frequently and the results of these interactions made public for the Extended Scrum Team. In the case of projects with full-time "committers" or commercial open source projects this should happen daily. In the case of solo or part-time core teams weekly or biweekly Scrums should be held. Scrum meetings can be held over instant messaging but work best face to face. The content will be maintained in a Forum.

Establish the time and place for the daily Scrum meeting and if a dial in is required. The Scrum team is responsible for ensuring members are present. The ScrumMaster simply ensures the conversation stays focused and tracks and manages the blockers.

How to Contribute?

Burn Down Charts

Use a chart that shows progress throughout a Sprint and ensure it is transparent to the extended team.

The team tracks its progress against a release plan by updating a release burndown chart at the end of each sprint. The horizontal axis of the release burndown chart shows the features; the vertical axis shows the amount of work remaining for each feature.

  • No labels