Agile Status Package
 
  • SDLCforms Status Slide Show Page 1
  • SDLCforms Status Slide Show Page 2
  • SDLCforms Status Slide Show Page 3
  • SDLCforms Status Slide Show Page 4
  • SDLCforms Status Slide Show Page 5
 

Learn More About the Agile Status Package

Quick View of Status Forms

Quick View of All Status Forms

Download Status Package PDF Files

Download 20 Status Package PDF Files

Compare Agile Packages

Side-By-Side Comparison of Agile Packages

Forms Included in Package
Form Name Type Form Purpose View/Download
Project Charter A project charter (PC) is a document that states a project exists and provides the project manager with written authority to begin work.

The document assists the project manager in communicating his authority and explain to project participants and stakeholders why the project is needed, who it involves, how long the project will take to complete, how much it will cost, what resources are needed and how successful completion of the project will help the organization. Once created, the document is rarely (if ever) amended.


Vision Statement A Vision Statement is a document that describes a compelling idea or values or future state for a particular organization, product or service. It defines the stakeholders view of the product/service to be developed, specified in terms of the stakeholders key needs and features. It provides the fundamental basis for the more detailed technical requirements.

Project Data Sheet The objective of a project data sheet is to convey the scope, schedule, and resources of how a project will deliver on the project vision.

A project data sheet is a single summary of key business and quality objectives, product capabilities, and project management information. It is a simple document with a powerful impact whose condensed format appeals to the entire project community and constantly reminds them of the strategic aspects of the project.


Theme / Epic Structure (Excel) The Theme / Epic Structure provides the ability to graphically identify a hierarchy of an optional high level theme and /or epic and depicts the user stories within that hierarchy.

Two versions of the Theme / Epic Structure are provided in the package - this document in Excel and one in Visio, as some organizations prefer to work in Excel, while the Visio version facilitates ease of "drag and drop" to move/copy objects within the document.


Theme / Epic Structure (Visio) This is the optional Visio version of the Theme / Epic Structure (see Theme / Epic Structure (Excel)) to provide ease of working with "drag and drop" objects to update the document.

Release Plan A release plan communicates when the release will be available, what features will be in the release, and how much it will cost.

The Release Plan is a collaborative effort involving these roles: Scrum master: Facilitates the meeting. Product owner: Represents a general view of the product backlog. Delivery team or agile team: Provide insights into technical feasibility and dependencies.


Sprint Planning & Meeting Schedule The Sprint Planning & Meeting Schedule is a collaborative effort involving a ScrumMaster, who facilitates the meeting, a Product Owner, who clarifies the details of the product backlog items and their respective acceptance criteria, and the entire Agile Team, who define the work and effort necessary to meet their sprint commitment.

This document provides a vehicle to identify the sprint / task duration, start and end dates, a description of the task, the priority, and allocated story points.


Risk Management Register Risk management identifies, addresses, and reduces or preferably eliminates sources of risk by taking mitigating actions before they become a threat to the project.

Risk management methodology determines the processes, techniques, tools, and team roles and responsibilities for a specific project. The risk management log describes the risk, the mitigating action, the probability of the risk, the size of the risk, and the exposure, generally measured in days.


Planning Poker Companion The Planning Poker Companion is a method for estimating story points for user stories accomplished by entering values provided by the Agile Team with four optional methods for capturing and displaying results: Fibonacci Series, Numeric Series, Hours Approximation and Days Approximation.

Averages are then calculated for: 1) Last Round Only, 2) Average All Rounds, and 3) Average Without First and Last Rounds.


Story Points Allocation Story points allocation provides a repository for identifying and recording the applicable sprint, the epic or theme (if applicable), the user story, and the points allocated to each story.

Sprint Backlog Status (Excel) Two versions of the Theme / Epic Structure are provided in the package - this document in Excel and one in Visio, as some organizations prefer to work in Excel, while the Visio version facilitates ease of "drag and drop" to move/copy objects within the document.

The Theme / Epic Structure provides the ability to identify a heirarchy of an optional high level theme and /or epic and depicts the user stories within that heirarchy


Sprint Backlog Status (Visio) This is the Visio version of the Theme / Epic Structure (see above) to provide ease of working with "drag and drop" objects to update the document.

14-Day Sprint Backlog - Capacity The 14-day Sprint Backlog contains the output of a sprint planning meeting. It contains a list of tasks that the Scrum team needs to complete during the sprint in order to convert a selected set of product backlog items into deliverable functionality within a period of 14 days.

The 14-day Sprint Backlog contains identification of the various sprints, and capacity for an elapsed period of 14 days.


30-Day Sprint Backlog - Capacity The 30-day Sprint Backlog contains the output of a sprint planning meeting. It contains a list of tasks that the Scrum team needs to complete during the sprint in order to convert a selected set of product backlog items into deliverable functionality within a period of 30 days.

The 30-day Sprint Backlog contains identification of the various sprints, and capacity for an elapsed period of 30 days.


Product Backlog Grooming Product Backlog Grooming is a meeting that is held near the end of one sprint to ensure the backlog is ready for the next sprint.

During a product backlog refinement meeting, the team and product owner discuss the top items on the product backlog and record decisions in the Product Backlog Grooming artifact.


Story Completion Checklist As user stories are completed, the product owner will work with their Agile team and the scrum master to ensure that the finished stories are complete in all aspects.

The Story Completion Checklist provides a vehicle to record user stories and verify that the story has been completed, inspected, and any defects identified for correction.


Sprint Burn-Up Chart A Sprint Burn-Up Chart is a graph that shows the progress of work toward a goal line associated with a value on the vertical axis.

As work is completed over time (the horizontal axis), the progress line moves up (burns up) to be nearer to the desired completion line. We can show projected outcomes on burn-up charts by calculating a trend line to see when work might be completed.


Sprint Burndown Chart The Sprint Burndown Chart displays the remaining effort for a given period of time. Work remaining is the Y axis and working days is the X axis. When the x and y axis coincide, the work is complete.

When tracking product development using the Burndown Chart, teams can use a Sprint Burndown Chart and a Release Burndown Chart.


Sprint Velocity Chart The Velocity Chart shows the amount of value delivered in each sprint, enabling you to predict the amount of work the team can get done in future sprints. It is useful during your sprint planning meetings, to help you decide how much work you can feasibly commit to.

Iteration Retrospective An Iteration Retrospective is conducted at the end of an Iteration. The output of an Iteration Retrospective directly feeds into the planning of the next Iteration. An Iteration Retrospective should be conducted after the completion of an Iteration, but before the start of the next Iteration.

To improve subsequent iterations, the Iteration Retrospective artifact consists of what questions should be asked, what worked well, what can be improved, what do we want to try, and what do we still not know?


 
  20 Forms $175.00
 
 
 
 

Home
Packages Individual
Forms
Understanding
SDLC

Forms
Overview
Questions &
Answers
Custom Form
Development
Documentation
Contact Us