FRED

Software Project Management Plan

Ver. 1.8 November 28, 2001

Preface
The Software Project Management Plan (SPMP) for FRED outlines the managerial aspects of the project, including a description of deliverables and deadlines. FREDs main objective is to create a system that will enable dental patients to fill out their medical information using a tablet pc while they wait to be seen by the dentist. Patients will be receiving targeted advertisments while they use the tablet PC. FREDs work will also serve to meet the requirements of the MSE program at Carnegie Mellon University (CMU). The customer for this project (the client ) is Scott Gray, representing the startup Limited Liability Corporation called RedX. The FRED team members are Nasri Hajj, Mike Lester, Georgios Markakis, Edward Neubecker, Jiang (Julian) Qian and Yue Zao, under the mentorship of Grace Lewis and Mark Klein. Hema Manickavasagam will be contributing to FREDs work during the fall of 2001. David Caruso will be FREDs technical writer for the Fall 2001 semester.

FRED SPMP version 1.8

Page 2 of 11

Table of Contents
Preface............................................................................................................................................................2 Table of Contents...........................................................................................................................................3 1 Overview.......................................................................................................................................................4 Project organization......................................................................................................................................7 2 Managerial process plans...........................................................................................................................7 3 References..................................................................................................................................................11

FRED SPMP version 1.8

Page 3 of 11

1 Overview
This section of the Software Project Management Plan (SPMP) gives an overview of the purpose, scope, and objectives of the project. It also contains sections regarding the assumptions and constraints, the project deliverables, the summary of the schedule and budget, and the plan for change in the SPMP.

1.1

Project summary

The client wishes to market a tablet PC based software system that will allow patients to fill out their medical information while in the dentists waiting room. The system should be able to interface with existing dental systems (such as Dentrex, Softdent, etc.) and should also be able to securely store the patients information so that the information can be retrieved upon subsequent visits. Finally, the system should be able to perform the following: Serve to the user targeted advertisments. Allow the user the tablet pc to surf the web. Provide information about the dentist. Provide surveys that the user can fill out. The scope and of the project is outlined in the Statement of Work (SOW). FREDs Project Plan provides a summary of the project tasks, milestones and deliverables. Technical information and use case scenarios can be found in the Software Requirements Specification (SRS) document.

1.1.1 Purpose, scope and objectives

The objective for this project is to create a system that satisfies the following requirements: Users should be able to use a tablet pc (provided by the dentist) to fill out their medical information while waiting to be received by the dentist. The information that the user provides should be communicated wirelessly to a secure, central repository for future retrieval and reference. Targeted advertising should appear on the tablet pc while it is in use. Users should be able to perform other functions with the tablet pc, such as surf the web, fill out surveys, play games, or read about other services provided by the dentist.

FRED will provide the client with a prototype. The goal of the client is to bundle a production-ready version of the system as a single solution and market it to dentists.

1.1.2 Assumptions and constraints

FRED operates under the following assumptions: The client has no human resources other than the FRED team to work towards building this system. Either the client or the MSE program will provide FRED with the tools (hardware, software, office space, etc) to complete this project. The development team has enough experience as a whole to complete the project. The development team will learn and work together to meet the deliverables of this project. The customer will respond in a timely manner to all questions and requests for information. The customer will provide or make available access to users for the purposes of conducting research and/or testing of the system.

The following constraints may impose limits on this project:

Our time availability for this project is constrained by other MSE program requirements. All studio time must be split between project work and other studio activities (classes, studiowide roles, etc.) FRED shall operate under the directives of the selected development process. Our ability to outsource functions of the system will depend on the responsiveness or the respective third-party vendor. We are bounded by the immaturities of the wireless sector, particularly with respect to security, speed and network availability. Additional resources (financial or human) are not available for the project.

1.1.3 Project deliverables

FRED will deliver all of the software and documentation for the project to the client no later than August 9, 2002. In addition, a final report and presentation will be given to the MSE studio audience at about that time. These deliverables are described below and are subject to change. Only a single copy of each deliverable shall be provided. For material given to the customer, an electronic copy of the material on a CD-ROM shall be sufficient. For studio deliverables, a printed hardcopy shall be provided. Customer deliverables shall be considered delivered when presented to the client. Studio deliverables shall be considered delivered when given to either of the FRED studio mentors, or their designee.

1.1.3.1 Software deliverables

Software The following is a preliminary list of software deliverables that will be handed to the client upon completion of the project. will be determined upon completion of the system architectureThese deliverables will be updated as the architecture of the system approaches completion. Software Component Tablet PC client Dental server RedX server Delivery Date (No Later Than) August 2002 August 2002 August 2002

1.1.3.2 Documentation Deliverables

The following is a preliminary list of documents that the team will need to deliver to the client and/or internally: Document FRED Statement of Work (SOW) FRED Software Requirements Specification (SRS) FRED Software Project Management Plan (SPMP) Software Architecture Design Test scripts and procedures User manuals (system and user documentation) Process documentation (including Process Improvement Plans) Delivery Date (No Later Than) Dec 5, 2001 Dec 5, 2001 (first version) Dec 5, 2001 Spring May 2002 August 2002 August 2002 Dec 5, 2001 (first version)

Table 1 - Documentation Deliverables

FRED SPMP version 1.8

Page 5 of 11

1.2

Evolution of the plan

This SPMP is intended to be an evolving document. As the project changes from cycle to cycle, a team member will be responsible for updating the SPMP. The team leader is responsible for the revisions to this document, although responsibility for some of the sections may be delegated to other members of the team.

FRED SPMP version 1.8

Page 6 of 11

Project organization
This section describes the external interfaces to the team, the internal team structure as well as the roles held by the team members.

1.3

External interfaces

The client representative for this project is Scott Gray. The FRED customer liaison is responsible for formal interaction between the FRED and the client representative. Necessary interaction can be done through anyone on the team, but all discussions with the customer should be documented clearly for records.

1.4

Roles and responsibilities

Based on the process that FRED follows, there are two roles that exist in the team: Team Lead and Developers. FRED will have a different Team Lead every semester. By default all other members will have the role of Developers. There is also one technical writer assisting the group during the Fall and Spring semester.

2 Managerial process plans

This section contains the management objectives and priorities; the start-up and staffing plan; the project plan; the risk management plan; the reporting plan and the monitoring and controlling strategies. More plans will be added as the document evolves.

2.1

Management objectives and priorities

FREDs primary objective is to ensure the successful completion of the project. To be considered successful, the team must perform the following: 1. Use good software engineering methods to develop the product. o Apply the methods learned in classes. o Experience a new way of doing things. o Practice reflective learning. Deliver a quality product that meets the requirements agreed upon in the SRS. o Deliver a product that is stable and relatively defect-free. o Deliver a system that addresses the clients needs at the clients satisfaction. Honor its commitments. o Meet client and team deadlines. o Avoid unrealistic commitments. Display professionalism. o Value the time of team members, mentors, and the client. o Accept and support team decisions. o Communicate openly and frequently. o Take responsibility for the success of the project. o Be proactive. Make efficient use of all available resources. o Learn from each other.

2.

3.

4.

5.

o o

Take advantage of the Software Engineering Institute and Carnegie Mellon University staff and peer expertise. Experiment with existing tools and processes.

2.2

Start-up plan

This section describes the materials and resources required to start the project. Because most of this information was pre-defined, this section will not describe the rationale for many of these choices.

2.2.1 Staffing plan

Section 2.2 shows the staffing resources for the project. Each team member will be available for 12 hours per week in the fall and spring semesters. This time includes time spent with the mentors and time spent working on any studio-related tasks, such as team and client meetings, document preparation and inspection, and tool development Each team member is expected to devote 48 hours per week in the summer semester. In addition to the core members, there will be several peripheral resources shared among all the studio teams. These are described in the MSE Studio Handbook. All of these resources will be available from August 2001 to August 2002. A technical writer will be available for the Fall semester and possibly for the Spring semester as well. There will be no writer available to the team during the summer

2.3

Reporting plan

Internal reporting for FRED team members will be relatively informal. Each team member will provide a status report to the team during the weekly team meetings. The Team Lead will use this information to update the project plan. Mentors will be invited to attend the weekly meetings for general status issues. Additionally, each team member will have a regularly scheduled one-on-one meeting with their mentor and will send a weekly email report to discuss further issues. External reporting will be more formal. At the end of each semester, the team will give a presentation (EOSP) for the MSE studio on selected items of significance for that semester. In addition, the team will give biweekly status reports to the customer at the client meetings to indicate progress. Although external reporting should take the form of face-to-face meetings with the customer, if the customer is not available, a written or electronic report will be sufficient.

2.4

Project Plan

FRED will operate under the guides of a project plan prepared by the Team Lead. Refer to [4] for the most recent copy of the teams project plan. The following WBS (duration in person-hours) summarizes the tasks outlined in [4]:

FRED SPMP version 1.8

Page 8 of 11

System Design

80 p-h

Code

137 p-h

Document

32 p-h

Entry: Functional Requirements Tasks: Top-level diagram, internal system interfaces, external system interfaces design, database design. Verification: All components of the system have been designed according to the requirements. Exit: Design of the entire system (including internal and external link connections).

Entry: System Design, Requirements Tasks: Implement Tablet PC GUI, the actual thin client, dentist & RedX server. Verification: All parts of the system plus their connections have been implemented based on the design and the requirements and are ready to be tested. Exit: Fully implemented system.

Entry: System design, code Tasks: Prepare system and user documentation. Verification: Sufficient technical (system) and user documentation has been produced. Exit: System and user documentation.

Test Data Test Plan

15 p-h

10 p-h 17 p-h

Entry: Requirements, design Tasks: Create a plan for testing the functionality of client, servers, external interfaces, connections and overall system, including authentication. Verification: There exists a test plan for all components/connections of the system. Exit: Test Plans for isolated units as well as for the entire system.

Entry: Design, Test Plan Tasks: Prepare data for Tablet PC, dentist server, RedX server, external & internal links as well as proper authentication. Verification: Sufficient data must exist to perform thorough tests on all components of the system including their connections. Exit: Test Data for client, dentist & RedX servers, external and internal connections.

Product Test
Entry: Design, Code, Test Data, Test Drivers, and Test Plan Tasks: Test functionality of Tablet PC, dentist server, RedX server, external and internal links as well as authentication. Verification: All parts of the system have been thoroughly tested and bugs have been either fixed or properly documented. Exit: System has been tested thoroughly and all bugs found were either fixed or properly documented.

Test Drivers

10 p-h

Figure 4: Level 1 ETVX diagram for Tablet PC

Entry: Design, Test Plan Tasks: Prepare drivers to test functionality for internal/external interfaces and overall system. Verification: Proper test drivers must exist for every test that is to be performed. Exit: Drivers for unit and system testing.

2.5

Risk management plan

Risks will be managed through a web-based interface that will be available through FREDs web site. The five most urgent risks will be reviewed at each team meeting. This list will be maintained and updated either by the Team Lead or, after a team meeting, by the Scribe. During the spring of 2002, a mini Software Risk Evaluation (SRE) meeting will be conducted to perform risk analysis and risk mitigation strategies.

2.5.1 Risk identification and prioritization

The team has identified important risks it may face and assembled them into the Top Risks list. This list is published on the FRED Web site to be reviewed by each member. Reassessment of risks will include identification of new risks, elimination of old risks, and prioritization of the list.

2.5.2 Risk mitigation

For each risk identified in the top risks list, mitigation strategies will be presented, reviewed, and documented during the weekly status meeting. Any tasks that need to be completed order to mitigate risks will be assigned as action items and added to the team plan.

2.5.3 Risk tracking

All risk-related action items will be reviewed as part of the action items during the weekly status meeting with the team and updated updates will be made on FREDs web site.

2.6

Monitoring and controlling strategies

FRED will actively track plans and the processes it has established. Several methods will be implemented for effective tracking of the project.

2.6.1 Weekly team meetings

Each week, the team leader (or a designee) will chair a team meeting to update members on the status of the project and to discuss any new issues. Time permitting, the team meeting will also be an opportunity to brainstorm ideas and provide suggestions and comments. Each team meeting will commence with an update of the open action items so everyone will have an understanding of the status and progress of each action item. The team meeting will then continue with the agenda for the meeting. Finally, the team meeting will end with a review of the project plan, the list of risks and new action items. If and when there is an open issue with the team, it will be discussed at the weekly team meeting and handled accordingly. Additional meetings may be requested by team members on a per-need basis.

2.6.2 Bi-weekly client meetings

Every other week, the customer liaison will facilitate a client meeting to provide an update of the status of the project to the client, and also to elicit requirements from the clients. At this meeting, each team member will be able to request clarifications and ask questions regarding the project. Similar to the team meeting, each client meeting will commence with an update of the open action items. The client meeting will then continue with the objective stated for the meeting. Finally, the client meeting will end with the listing of new action items. If and when there is an open issue with the client, it will be discussed at a client meeting. Depending on the level of the issue, the customer liaison may email the client directly.

2.6.3 Brainstorming meetings

On a per-needed basis, the developers of FRED will meet to brainstorm on some issue or discuss action items. This meeting is designed for team members to work together on portions of the project. This working meeting is informal and it is intended to be a learning time for each member on the team.

2.7

Processes and practices

The team will maintain documentation on the process that it follows during the lifetime of the project. The details of this process can be found in the FRED Process Document [3]. Should the team decide to modify any parts of its adopted processes, all such modifications will be documented in the form of a Process Improvement Plan (PIP). The team may decide to test the proposed process modifications for some period of time before adopting the modifications as permanent.

2.7.1 Paired tasks

It is generally good practise for the team lead to assign two to three people per sufficiently large task. Specifically during the development (coding) phase of the project, paired programming will be part of the teams process.

3 References
[1] [2] [3] [4] FRED Software Requirements Specification. CMU-MSE-FRED-SRS-1.0, 2001 FRED Statement of Work. CMU-MSE-FRED-SOW-1.0, 2001 FRED Process Document CMU-MSE-FRED-PROCESS, 2001 FRED Project Plan CMU-MSE-FRED-PROJECT-PLAN, 2001

FRED SPMP version 1.8

Page 11 of 11