**Collegiate Sports Paging Service
Iteration Plan**
Version 1.0
Revision History
| Date | Version | Description | Author |
| October 6, 1999 | 1.0 | Initial version | Context Integration |
Table of Contents
- Introduction
- Plan
- Resources
- [Use Cases](#Use Cases)
- [Evaluation Criteria](#Evaluation Criteria)
Introduction
Purpose
This Iteration Plan describes the detailed plans for the Preliminary Iteration of the Project. During this iteration, the requirements of the system will be defined and the high level plan for execution of the full project will be developed. This first iteration will conduct a thorough analysis on the business case for the system and will result in a decision on whether the project will proceed.
Scope
The Preliminary Iteration Plan applies to the project being developed by Context Integration for WebNewsOnLine. This document will be used by the Project Manager and by the project team.
Definitions, Acronyms and Abbreviations
See Glossary document.
References
Plan
The Preliminary Iteration will develop the product requirements and establish the business case for the Collegiate Sports Paging System. The major use cases will be developed as well as the high level Project Plan. At the end of this iteration, will decide whether to fund and proceed with the project based upon the business case.
Iteration Tasks
The following table illustrates the tasks with their planned start and end dates.
| Task | Start | End |
| INCEPTION | Fri 10/1/99 | Mon 10/25/99 |
| Begin Inception | Fri 10/1/99 | Fri 10/1/99 |
| Inception Kick-off | Mon 10/4/99 | Wed 10/6/99 |
| Add tasks to project plan for specific project technology using ContextWISE cartridges | Mon 10/4/99 | Mon 10/4/99 |
| Assemble Change Control Board | Mon 10/4/99 | Tue 10/5/99 |
| Create and baseline Change Control Plan | Tue 10/5/99 | Tue 10/5/99 |
| Obtain Sign-off | Tue 10/5/99 | Tue 10/5/99 |
| Inception Kick-off Meeting | Tue 10/5/99 | Wed 10/6/99 |
| Prepare for inception kick-off meeting | Tue 10/5/99 | Wed 10/6/99 |
| Hold Inception Kick-off Meeting | Wed 10/6/99 | Wed 10/6/99 |
| Inception Kick-off Completed | Wed 10/6/99 | Wed 10/6/99 |
| Inception Deliverables | Wed 10/6/99 | Thu 10/14/99 |
| Hold Requirements Workshop | Wed 10/6/99 | Thu 10/7/99 |
| Project Vision created, reviewed, and signed off | Wed 10/6/99 | Thu 10/7/99 |
| Preliminary Use Case Model (10-20% complete) created and placed under revision control | Thu 10/7/99 | Mon 10/11/99 |
| Preliminary Use Case Survey created, reviewed, and signed off | Mon 10/11/99 | Tue 10/12/99 |
| Preliminary Supplementary Specifications created, reviewed, and signed off | Tue 10/12/99 | Tue 10/12/99 |
| Business Case created, reviewed, and signed off | Tue 10/12/99 | Tue 10/12/99 |
| Preliminary Project Glossary created, reviewed, and signed off | Tue 10/12/99 | Tue 10/12/99 |
| Preliminary Creative Design Brief created, reviewed, and signed off | Wed 10/6/99 | Thu 10/7/99 |
| Preliminary Site Map & Use-Case Navigation Mapping created, reviewed, and signed off | Thu 10/7/99 | Fri 10/8/99 |
| Creative Design Comps created, reviewed, and signed off | Fri 10/8/99 | Mon 10/11/99 |
| Preliminary Content Plan created, reviewed, and signed off (if applicable) | Wed 10/6/99 | Wed 10/6/99 |
| User Interface Prototype (optional) created, reviewed, and signed off | Wed 10/6/99 | Wed 10/6/99 |
| Reports Prototype (optional) created, reviewed, and signed off | Tue 10/12/99 | Thu 10/14/99 |
| Develop Preliminary Technology Alternatives | Wed 10/6/99 | Thu 10/7/99 |
| Establish contact with appropriate Context Gurus | Tue 10/12/99 | Wed 10/13/99 |
| Preliminary Knowledge Transfer Plan & Schedule created, reviewed, and signed off | Wed 10/13/99 | Wed 10/13/99 |
| Validate/Invalidate Assumption from Inception proposal | Wed 10/13/99 | Thu 10/14/99 |
| Obtain Sign-off | Thu 10/14/99 | Thu 10/14/99 |
| Inception Deliverables Complete | Thu 10/14/99 | Thu 10/14/99 |
| Inception Wrap-up | Thu 10/14/99 | Mon 10/25/99 |
| Conduct Quality Check Meeting with Client | Thu 10/14/99 | Thu 10/14/99 |
| Conduct Quality Assurance | Thu 10/14/99 | Fri 10/15/99 |
| Hold Context Lessons Learned Meeting | Thu 10/14/99 | Thu 10/14/99 |
| First project estimates created, reviewed, and signed off (+75%, -60%) | Thu 10/14/99 | Mon 10/18/99 |
| Full Project Iterative Delivery Plan created, reviewed, and signed off | Mon 10/18/99 | Tue 10/19/99 |
| Create proposal for Elaboration Phase | Thu 10/14/99 | Fri 10/15/99 |
| Create Software Project Log | Fri 10/15/99 | Fri 10/15/99 |
| Prepare for Inception Checkpoint | Fri 10/15/99 | Mon 10/18/99 |
| Have team, including client project manager, complete the work release sign-off form | Mon 10/18/99 | Tue 10/19/99 |
| Deliver proposal for Elaboration Phase | Tue 10/19/99 | Thu 10/21/99 |
| Inception Checkpoint Review and Go/No Go Decision | Thu 10/21/99 | Fri 10/22/99 |
| Move appropriate deliverables from Project Homepage to IAN Artifacts | Fri 10/22/99 | Mon 10/25/99 |
| Inception Complete | Mon 10/25/99 | Mon 10/25/99 |
The following deliverables or artifacts will be generated and reviewed during the Preliminary Iteration:
| Artifact Set | Deliverable | Responsible Owner |
| Business Modeling Set | Glossary | Brian Egler Brian Egler Brian Egler Brian Egler |
| Requirements Set | Vision Document Use Case Specifications Supplementary Specification Use Case Model (and Model Survey) | Brian Egler Brian Egler Ed Post Ken Perch Ken Perch |
| Management Set | Preliminary Iteration Plan Project Plan Project Schedule Project Risk List Status Assessment Preliminary Iteration Assessment Configuration Management Plan | Mary Durham Mary Durham Mary Durham Mary Durham Mary Durham Mary Durham Mary Durham Mary Durham Ken Perch |
| Standards and Guidelines | Configuration Management Environment | Ken Perch |
Resources
The project staffing for this iteration can be viewed as follows:
Financial Resources
The budget for this iteration is $150,000. WebNewsOnLine has secured this funding.
Use Cases
During the Preliminary Iteration, all significant use cases and actors will be identified. The basic flows and key alternative flows of each use case will be determined and documented in the Use Case Specifications. The design and implementation of use cases will begin in the next iteration.
Evaluation Criteria
The primary goal of the Preliminary Iteration is to define the system to the level of detail required to make a sound business judgment on the viability of the project from a business prospective. At the completion of the iteration, a review of the Business Case will arrive at a Go / No Go decision for the project.
Each deliverable developed during the iteration will be peer reviewed and subject to approval from the team.
Criteria for evaluation can be found in the Test Plan.