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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


People are going to want to know what's going on in the Sprint. A weekly demo works to allow outside but interested members to see and hear what's the current status.

Sprint Backlog

To be maintained in JIRA - re-work underway for improvements.


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.

Also, establish rules of engagement for the team ie: Every developer will ensure that code is unit tested before being checking in. ie: see Daily Scrum Meetings.

Daily Scrum Meetings

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

Development Process

  • No labels