Summary

This document describes the features and timeframe desired for this project...

Project Goals, Justification, and Success Criteria

Project Goals

Explain the goals of the project here...

Justification

Explain why the project is needed. List revenue impact or cost savings information.

Success Criteria

List the success criteria for the project. Once the project is complete, it will be measured back to the criteria listed here to determine if the project was successful.

Features

Feature 1

Explain exactly what the feature is to perform in Use Case format. List any constraints, actors, security implications, etc.

Feature 2, etc

Security Requirements

Explain the security requirements of the system. If needed, assign user groups and define what those groups have access to.

Data Conversion Requirements

Explain any requirements in which we must convert data to import into the system. Detail the mapping needed from their system to the new system.

Performance and Response Time Requirements

Explain how many concurrent users will be using the system and expected response time.

Platform Dependent and Installation Requirements

Explain what platforms the client presentation layer must run on (Windows 95, 98, NT 4, 5, etc)

Localization Requirements

Explain any requirements that are specific to localization (European date and postal code format, etc.)

Parallel Testing Requirements

Explain the areas of the system (if any) that must be run parallel to an existing production system and compared for consistency.

Cross System Interface Requirements

Explain the systems this system interact with and detail any requirements for testing with that system to ensure integrity.

Data Archival, Backup and Recovery Requirements

Explain the purge, archival, backup and recovery requirements of the system.

Reporting Requirements

Describe the reports (if any) are required for the system. Are they to be online or run in batch and must they be exportable to other formats such as MS Word, MS Excel or HTML.

Project Flexibility Matrix

For a project to succeed, there are 3 variables that affect how quickly a project can be completed: Resources, Schedule and Feature (see diagram below). One of the sides of the triangle must always be flexible to achieve success. For example, if the client has a fixed number of resources (people that work on the project) and their schedule has been set in stone, the feature set must be flexible. This means that they must be flexible to drop some features to make the pre-determined date with that number of resources.

Stack Ranking of Features

To ensure that items are worked on in order of importance, stack rank the features with the lowest stack rank being most important and the highest stack rank being least important. This will allow the development team to focus on the important items and to manage risk.

Roles and Responsibilities

Below are the roles and responsibilities for each phase of the life cycle. Smaller projects may not be broken out to this level of detail.

Life Cycle	Role	Responsibility
Planning	Setup hardware for development	Development Team
	Functional specs	Development Team / Client Project Manager
	Detailed Design	Development Team
	Test Design	System Test Lead
	Development Project Plan	Development Team
	Test Project Plan and Budget	System Test Lead
	Overall Project Plan	Project Manager
Construction	Coding	Development Team
	Unit Testing	Development Team
	System Test - Test Cases	System Test Team
	User Test - User Test Lead	User Test Team
	User Test - Test Cases	User Test Team
	Setup hardware for System Testing	System Test Team
System Testing	Migration of code/database from development to system test	Development Team
	Populate test database for system test	Development Team
	System testing	System Test Team
	Bug tracking / triage	System Test Lead, Development Manager, Project Manager
	Drops for reiteration of fixes	Development Team
User Acceptance Test (UAT)	Migration of code system test to UAT	Development Team
	Populate test database for UAT	Development Team
	UAT Testing	User Test Team
	Bug Tracking/Triage	System Test Lead, DM, PM, User Test Lead
	Drops for iteration of fixes (must go back through System Test)	Development Team
Production	Migration of code from UAT to production	Development Team