Project Plan Assignment
In this assignment you will create a project plan for a fictional project described below. Often organizations create a High Level Scope for projects. These are typically 1 page documents describing the software. They are used for planning purposes and deciding on what software should be created next without writing a full requirements document.
Once a High-level Scope is approved a Project Plan is created. Often Project Plans change throughout the course of the project, but it is important to have a Project Plan at the beginning of a project.
In this assignment you may use any software development method taught in this class. You are also allowed to make any assumptions about your technical team, budget, etc.
Accompanying this assignment is a Project Plan Template. The template is organized for the Waterfall model, but can be easily changed for other development methods. For example, if you are doing an Agile method, sections 4.1.1, 4.1.2, etc. could be for different Sprints of your project.
Deliverable
For the project you should only submit a Word or PDF document of your Project Plan.
Grading
The software development method that you select will not have an impact on your grade. There is no right or wrong method for this project.
Grading Ru
ic
Item
Description
Percentage
Follows the method
Your project plan should clearly state what method you are using. All areas of the Project Plan should have activities that co
ectly implement the selected method.
30%
Clearly Written
The project plan should be clearly written, free of grammar and spelling mistakes.
20%
Consistent
Your project plan should be consistent. If in one section you state that you are using the Waterfall method and in other you write about Sprints, these two sections are not consistent with each other.
30%
Completeness
All areas of the method should be included.
20%
High-level Scope
Software Title: Cancerous Tumor Tracking System
Description
A cancer research team studies different types of cancerous tumors and all relevant information that is known about the tumor. Cu
ently they have been doing this with a simple shared drive on the network. Now, they would like to build a software system that will track all of the information and provide search capabilities.
The system needs to track the many different types of tumors. Each tumor has a medical name, like Pleomorphic Adenoma. There is various information stored about each tumor like: type (cancerous or non-cancerous), typical location of the tumor, photos, etc. Once this data is entered it probably won’t change much, unless there is a new type of tumor.
Then researchers can find and enter research about the tumor. This could be documents like PDFs or links to websites.
Finally, we would like a website for the general public to use to search through the database. Public users can read the data, but not enter, update or delete anything.
Project plan template
Source: This template comes from the following source, which is creative commons.
Baars, W., Harmsen, H., Kramer, R., Sesink, L. and van Zundert, J., 2006. Project management handbook. The Hague: DANS–Data Archiving and Networked Services.
project name
Project name:
Date:
Project leader:
Phase:
development phase, implementation phase or follow-up phase
For approval:
Date:
For approval:
Date:
__________________________________________________________________
Introduction:
This document is a
ief instruction book for compiling a project plan. The first project plan is developed after the initiation phase and serves as an approval document for the entire project. After each phase, this document must be revised. A detailed plan must be developed for the next phase. For the subsequent phases, the plan will be of a more global nature. Evaluation of this document also takes place after each phase.
General information about the project
1. Situation sketch and problem definition of the project
· Provide a
ief description of the organisation in which the project will take place.
· Provide a
ief description of the department(s) in which the project will take place.
· Provide a
ief description of any relationships between this project and any others.
· Provide a
ief description of the history of this project.
· Provide a
ief description of the catalyst for this project.
· Identify the client(s) for this project.
· Identify the contractor for this project.
2. Project assignment
· Explain the rationale for this project; follow the SMART formula as closely as possible.
(SMART=specific, measurable, attainable, realistic, timely).
· Identify what will be delivered.
· Identify the most important boundaries of the project (what will not happen).
3. Risk analysis
· Identify the risks that are known in this project.
· Specify how these risks will be handled (avoiding, fighting, insuring, accepting).
4. Organisation of the project
This section of the project plan provides a description of the phases, activities in each phase and the associated control factors of the project. The plan is elaborated globally for the more remote phases and in concrete and specific terms for the next phase. This sample begins from the compilation of the initial project plan and thus with the initiation phase. This section of the project plan should be revised after each phase.
4.1 Explanation of the project/management model that will be applied
Briefly explain the software develop method being used. Sections 4.1.1 through 4.1.7 are sections for each phase of the project. Based upon the methodology these phases can be different. The examples in XXXXXXXXXXthrough 4.17 are for the Waterfall model, but change them based upon your method.
4.1.1 Initiation phase
This project plan is the result of the initiation phase. This phase requires no further detailed elaboration. A summary of the activities that have taken place in preparation may be included.
4.1.2 Definition phase
Planned starting date:
Planned ending date:
Description of the result of the definition phase:
A list of requirements concerning the project result will be compiled in the definition phase.
Most important milestones: <(example)
· List of functional requirements
· Research on legal requirements
· Requirements from interviews with end users
· Requirements from end-user tests
· Report of technical requirements
· Client approval of list of requirements
Specify when each milestone will be accomplished and who is responsible. Specify the required quality for each milestone (intermediate product).
Activities in the definition phase:
Provide a list of the activities that must take place in order to achieve the milestones. Specify who will ca
y out these activities, when and by whom they will be approved (ultimate responsibility).
Timeline:
Include a chronological list of activities using a bar graph or similar visual aid. Provide a clear indication of the timing of all milestones. Do not forget to include margins.
Budget:
Provide an estimate of the costs for each activity in this phase. In addition, specify the costs for materials and supplies, as well as any other costs. Refer as necessary to external documents that specify the costs (see also the separate model for budgets).
Internal information:
Indicate how the information from this phase will be recorded and archived. Specify any resources that will be used and, if necessary, who will or will not have access to this information.
External information:
The approval of this phase by the client/customer is an important information moment. Indicate the reports that must be submitted to the client, customer or external management after this phase.
4.1.3 Design phase
Planned starting date:
Planned ending date:
Description of the result of the design phase:
A (number of) design(s) for the intended project result will be made in the design phase.
Most important milestones: <(example)
One or more dummies
Screen design
Photo impressions/sketches
Specify when each milestone will be accomplished and who is responsible. Specify the required quality for each milestone (intermediate product).
Activities in the design phase:
Provide a list of the activities that must take place in order to achieve the milestones. Specify who will ca
y out these activities, when and by whom they will be approved (ultimate responsibility).
Timeline:
Include a chronological list of activities using a bar graph or similar visual aid. Provide a clear indication of the timing of all milestones. Do not forget to include margins.
Cost estimates:
Provide an estimate of the costs for each activity in this phase. In addition, specify the costs for materials and supplies, as well as any other costs. Provide an estimate of the costs for each activity in this phase. As necessary, refer to an external document that contains the costs. Do not forget to include a category of ‘unexpected costs’ and the costs of project management itself (also see the separate model for budgets). As necessary, refer to an external document that contains the costs (also see the separate model for budgets).
Internal information:
Indicate how the information from this phase will be recorded and archived. Specify any resources that will be used and, if necessary, who will or will not have access to this information.
External information:
The approval of this phase by the client/customer is an important information moment. Indicate the reports that must be submitted to the client, customer or external management after this phase.
After the design phase, the waterfall method continues with the development phase; the DANS method for software development continues with the cyclical section. The various possibilities are described together below. One of the two options must be chosen for the preparation of a project plan.
4.1.4 Development phase <(Waterfall only)
Planned starting date:
Planned ending date:
Description of the result of the development phase:
During the development phase, an action plan will be developed in preparation for the implementation phase.
Most important milestones: <(example)
Action plan, Part 1
Action plan, Part 2
etc.
Specify when each milestone will be accomplished and who is responsible. Specify the required quality for each milestone (intermediate product).
Activities in the development phase:
Provide a list of the activities that must take place in order to achieve the milestones. Specify who will ca
y out these activities, when and by whom they will be approved (ultimate responsibility).
Timeline:
Include a chronological list of activities using a bar graph or similar visual aid. Provide a clear indication of the timing of all milestones.