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

Learn More About the Agile Planning Package

Quick View of Agile Planning Forms

Quick View of All Planning Artifacts

Overview of Planning Package

Download 10 Planning 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 Word logo 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 explains 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.

Vision Statement Word logo 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.

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.

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.

Theme / Epic Structure (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

Theme / Epic Structure (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.

Planning Poker Companion Excel logo 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.

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.

  10 Forms $99.00
  Information   Products   Documentation  
  Primer on WaterFall SDLC Process
Questions & Answers
Forms Overview
Custom Form Development
Contact Us
Order Status
Place Purchase Order
  Agile Multi-Form Packages
Waterfall Multi-Form Packages
Individual Agile Forms
Individual Waterfall Forms
Agile Planning Package
Agile Status Package
Waterfall Starter Package
Waterfall SmallBiz Package
Waterfall JumpStart Package
Waterfall Professional Package
Waterfall Ultimate Package
  Agile Quick Start Guide
Agile System Administrator Guide
Agile User Guide
Waterfall Quick Start Guide
Waterfall System Administrator Guide
Waterfall User Guide
Creating Your Own SDLC Process
Video - Customizing SDLCforms Office 2007-2010
Video - Customizing SDLCforms Office 2013-2016
  Copyright © 2007-2017 Documentation Consultants