Project Plan

INTRODUCTION

Purpose of Plan
The purpose of this document is to describe the plan for a software development project to be carried out for CSc 205-206.

Project Scope
    See ETA-document containing customer's description of the project.

PROJECT TEAM

    Fetter Software
    Chained to the Computer

    Phillip Hansen - pshansen@calpoly.edu
    Wesley Strickland - wsstrick@charter.net
    Mike Power - mpower@falcon.csc.calpoly.edu
    Mike Hebron - mhebron@calpoly.edu
    Jonathon Lee - jolee@calpoly.edu
    Apel Yahinian - ayahinia@calpoly.edu

TEAM ORGANIZATION

Our team consists of six people. To view a complete description of each job click here.

Mike Hebron - Project Manager, Toolsmith

• The Project Manager is the administrative coordinator for all project activities. This job is critical to completing the final deliverable on time.
• Provide training on all development tools.
Jonathon Lee - Testing, Risk Officer
• Write and administers the product's Test Plan.
• Write/maintain top 10 risks list
Apel Yahinian - Configuration Management, Web Developer
• Configuration management takes administrative responsibility for the project's source code and documentation.
• All 206 project documentation is maintained on the Web. This person designs and administers the project web page.
Wes Strickland - Integration and Release, Customer Liason
• Write the Integration and Implementation Plan.
• Keeps the Customer informed and involved.
Phillip Hansen - Designer, Analyst Jobs
• The designer creates and maintains the high-level software design.
• The analyst maintains the project Specification document (or User Manual) and serves as the system analyst.
Mike Power - Quality Assurance, Training Coordinator
• The QA person ensures that the product meets the specifications and satisfies the product's release criteria.
• Responsible that all project personnel are trained to a level of competency that enables them to perform their technical responsibilities.
Customer
• Mike Reisz

The lines of code and effort estimates can be found here.

PROJECT SCHEDULEClick here to see the schedule.MEETINGS

Our meeting format will be as follows:

• Discuss what had been completed from last time (Action Items)
• Discuss Problems
• Discuss what needs to be done
• Assign new Action Items

We will deliver the working ETA program as well as the User Manual.

Our project will also have three release stages, as we will be using the Staged Delivery Plan. Each stage will be a working version of the program with varying amounts of functionality. More information about each stage can be found here.

CONFIGURATION MANAGEMENT PLAN

Our Change Control Plan can be read here.

REPORTING PLAN

Individual Status Reports

• The status report is where each person documents their accomplishments for the week. It includes a timecard of hours spent and what activity they were engaged in. Due each weekend. Submitted to the Project Manager (see productivity metrics, below). (Electronic submission is fine).
• Follow the Status Report Template.

• Produced weekly, by project manager, posted on the team web page. Follow the Progress Report Template. We are also reporting to the class on a weekly basis.

• The purpose of the journal is to document the process the team went through in creating their product. It is a record of all team activities. It can be maintained by the manager or by a designated recorder. Primarily it contains the minutes from every status meeting. Also, it documents significant management and technical decisions made during the meeting.

The Quality Assurance Plan can be read here.

CHANGE HISTORY
 

Date	Author	Changes
3/2	JD	Added example Effort Summary to metrics plan
1/4	JD	Added Quality Assurance Plan
9/26/00	WS	Customized for Fetter Software
1/15/01	PH	Customized for CSC 206
1/17/01	PH	Revised
1/19/01	PH	Revised
1/22/01	PH	Revised estimates and delivarables sections