University: Griffith University, Brisbane, Australia
Degree: Bachelor of Information Technology Accelerated
Date: August 23, 2010
Class/Course: 2001ICT Project Management
Author(s): Jeremy Cade, Alice Jackson, Nathan Jensen, Jenny Nguyen
Paper Grade: 15.33/20
1. Introduction
1.1 Project Overview
The Brisbane Curtain Company has tasked Sharpwise Software with the development and
delivery of job / task scheduling system for use within the business.
The scheduling software is required to generate and maintain a series of forms with follow-up dates built into them to ensure jobs and regular tasks are completed on time. Ideally, this would also display on an all encompassing diary. This software must be accessible via the internet from multiple locations by staff out of the office as well as from computers in the office. Management of tasks will be maintained by a series of reminders and follow-up dates. If there are any uncontrollable delays to jobs, the customers must be informed immediately.
The project team consists of:
- Project Manager
- Quality Engineer
- System Analyst / Designer
- Programmer
1.2 Project Deliverables
- Project Plan.
- Job scheduling and task management software.
- User documentation for Job scheduling and task management software.
1.3 Evolution of the Project Management Plan
The following applies to versioning of this document:
- The Project Plan document starts at Version 0.01.
- For each revision the version is incremented by 0.01.
- Major revisions or changes of user requirements are to be incremented by 1.0.
| Revision Date | Version No. | Author | Description of Change/Revision |
| 2010/09/20 | 0.01 | Jeremy Cade | Introduction |
| 2010/10/04 | 0.02 | Jeremy Cade | Evolution of the project Management Plan |
| 2010/10/05 | 0.03 | Jenny Nguyen | Introduction |
| 2010/10/07 | 0.04 | Nathan Jensen | Project organisation |
| 2010/10/09 | 0.05 | Jenny Nguyen | Mangerial Process |
| 2010/10/10 | 0.06 | Jenny Nguyen | Revision History |
| 2010/10/10 | 0.07 | Jenny Nguyen | Mangerial Process |
| 2010/10/10 | 0.08 | Nathan Jensen | Software life Cycle Model |
| 2010/10/10 | 0.09 | Jeremy Cade | Software life Cycle Model |
| 2010/10/11 | 0.10 | Jenny Nguyen | Reference Material |
| 2010/10/13 | 0.11 | Jeremy Cade | Mangerial Process |
| 2010/10/16 | 0.12 | Alice Jackson | Project Responsibilies |
| 2010/10/16 | 0.13 | Jenny Nguyen | Risk Management |
| 2010/10/16 | 0.14 | Jeremy Cade | WBS/Schedule |
| 2010/10/17 | 0.15 | Jeremy Cade | WBS/Schedule/Gantt Charts |
| 2010/10/17 | 0.16 | Jeremy Cade | Minor Corrections to Introduction |
| 2010/10/17 | 0.17 | Jenny Nguyen | Appendix (6.4) |
| 2010/10/17 | 0.18 | Jenny Nguyen | Project Responsibilities |
| 2010/10/17 | 0.19 | Jeremy Cade | Appendix, Reference Materials, Function Points |
1.4 Reference Materials
- A Guide to the Project Management Body Of Knowledge (PMBOK Guide) 4th Ed. (2008). Published: Project Management Institute, Inc.
- Schwalbe, K. (2009). Information Technology Management, 6th Ed., Thomson Technology
- Australian Standard AS 4071
- ISO/IEC 12207
- ISO 14143:1998
1.5 Definitions and Acronyms
- WBS: Work Break Down Structure
- SDLC: Software Development Lifecycle
2 Project Organisation
2.1 Software Life Cycle Model
The Life Cycle Model to be used for this project is the Evolutionary Prototyping Model. Each evolution of the prototype will be limited to a predifed set or group of the functional requirements as set out in section 6 (List of Requirements) of the Business and User Requirements document developed by Sharp Wise Software. Each prototype will be limited to two revisions.
The Evolutionary Prototyping Model has been selected as the basis for this project for the following reasons:
- Allows for rapid, iterative development.
- Reduces need for final stage documentation.
- Facilitates feedback from the end users at critical stages during development.
This constant and repetitive feedback from end users is important for this feedback will improve the project and fix bugs and problems that users might encounter.
2.2 Organisational Structure
Authority Flow Chart
Communication Flow Chart
2.3 Organisational Boundaries and Interfaces
A description of the relationship between the project team and the other parties involved in
the project. Relevant stakeholders in the Project should be explicitly identified.
Key Stake Holders
- Sharpwise Software
- Our company
- Curtain company
Roles of the Stake Holders
Sharpwise Software
- Developer of the project
- Creates all the deliverables of the Project
- Delivering a quality Product
The Curtain Company
- Consumer of the project after Sharpwise Software develops from our companies project plan.
Our company
- Creating Project Plan
- Ensuring all requirements of the Curtain Company are met
2.4 Project Responsibilities
2.4.1 Project Manager
The project manager’s responsibilities are as follows:
- Lead the planning and implementation of project
- Facilitate the definition of project scope, goals and deliverables of the project
- Define project tasks and resource requirements
- Develop the project plan
- Assemble and coordinate the project team
- Manage the project budget
- Manage project resource allocation
- Plan and schedule the project timelines
- Track project deliverables using appropriate tools
- Provide direction and support to project team
- Work with the quality engineer to maintain quality assurance
- Constantly monitor and report on progress of the project to all stakeholders involved in the project
- Present reports defining project progress, problems and solutions of the project
- Implement and manage project changes and interventions to achieve project outputs
2.4.2 Quality Engineer
The quality engineer’s responsibilities are as follows:
- Responsible for quality system maintenance
- Assist project manager in establishing, implementing and maintaining the quality management system
- Interface with the software engineer and programmers to ensure transfer of concept to production of the system is in accordance with approved data
- Conduct audits, create finding reports and determine corrective and preventative action from these findings
- Analyse failure and take corrective action to respond to, if any, of client complaints
2.4.3 Systems Analyst
The quality engineer’s responsibilities are as follows:
- Analyzing the user requirements to develop a concept model
- Researching, designing the software program
- Testing the programs and fault finding;
- Creating technical specifications and test plans with the quality engineer;
- Writing operational documentation for the project
- Maintaining systems by monitoring and correcting any software defects;
- Working with the project manager, quality engineer and two programmers to effectively implement the project
- Consulting clients concerning the maintenance and performance of the system and asking questions to obtain information, clarify details and implement information
2.4.5 Programmers
The programmer’s responsibilities are as follows:
- Code, test and troubleshoot the program utilizing the appropriate hardware, database, and programming technology
- Build the project as to specifications designed by the Software Engineer
- Adhere to the requirements stipulated by the Quality Engineer in regards to quality control
3 Managerial Process
3.1 Managerial Objectives and Priorities
3.1.1 Objectives
The Brisbane Curtain Company project will be thoroughly documented in the project plan, to ensure all the aspects have been agreed upon so the project can be completed on time and in scope. The project team is consists of five members and together working as a team will responsible for successful completion and handover of the project that will satisfy the user requirements and hopefully exceed the user requirements. This project will aim to follow the recommended procedures from the Australian Standard AS 4071, and PMBOK, to allow for the team to work successfully together while building improving their leadership, team building, communication, decision making, negotiation and their political and cultural awareness.
The main project goal will be to deliver the product within the estimated scope, budget and time.
3.1.2 Mechanisms for communications and reporting
| Information | From | To | How | Frequency |
| Meetings | Project Manager | Team Members | Face to face | Weekly |
| Project Planning | Project Manager | Team Members | Weekly | |
| Contact Team members | Project Manager | Team Members | E-mail, phone | Daily |
| System Analysis Report | System Analyst | Project Manager | Face to Face | Weekly |
| Gathering Information from Client | Project Manager | Team Members | Face to face, E-mail, Phone | Daily |
| Consulting With Client | System Analyst / Designer & Project Manager | Client | Face to face, e-mail, Phone | Fortnightly |
| System Design | System Analyst | Project Manager | E-mail, Face to face | Weekly |
| System Programming | Programmers | Quality Engineer | Weekly | |
| System Development Processes | Programmers | Project Manager | Daily | |
| System Development Report | Programmers | Project Manager | Weekly | |
| System Quality Report | Quality Engineer | Project Manager | Weekly | |
| System Deliverables | Project Manager | Client | Face to face | At completed project time |
| System maintenance Report | Quality Engineer | Client | Monthly |
3.1.3 Relative Priorities
- Ensure that the project is within budget, on time, within scope, and of high quality
- Ensure that the online forms match the functional and quality requirements
- Ensure that the new system can communicate with the existing system
3.1.4 Resolving interpersonal issues
During the life cycle of the project, interpersonal issues could arise resulting in some conflicts among team members. The project manger is the key to resolving any issues that occur, however, there are some techniques and personal attributes that can help to reduce the conflicts among team members and allow for effective and efficient methods to resolve these interpersonal issues such as:
- Promote communication: Team members should focus on communication when working on the project to make sure work is not being duplicated
- Give feedback regularly: Conflict can arise due to team members having differentiating goals but with regular feedback and meetings allows the team to be driven to the same objectives.
- Compromise: All team members should work collaboratively, and assist each other towards solving issues.
- Confrontation: The project manager should allow team members to work on their jobs with their ideas as long as they complete their tasks and satisfy the requirement. If team members can’t resolve their issues than the Project Manager acts as a mediator to assist with the resolution.
3.2 Assumptions, Dependencies and Constraints
The assumption has been made that all outputs where the fucntional requirements regarding data outputs to a user are vauge or undifiend are External Outputs (EO) rather than External Enquries (EQ)
In this project plan it is assumed the requirements will not change or funding will not be cut by the responsible stakeholders. Constraints to the project will be for it to be completed in the accurate time frame listed in the project plan and for the cost to not be exceeded. The design and production of the schedule will be run independently from the running of the company at The Brisbane Curtain Company, though it will be dependant on the requirements presented and test data also with the input of stakeholders to approve of changes and acceptance.
3.3 Risk Management
3.3.1 Risk Management Processes
The below is a view of the risk management strategy that identifies the three top risks. The full risk table can be found in the appendix (Appendix 6.4)
| Risk No | Risk (Cause and Consequence) | Pre-Strategy Risk Exposure | Strategy Description | Residual Risk Exposure |
| R01 | Risk: Poor communication
Cause: Project team and/or client are not communicating Consequence: Requirements not understood, Errors in project phases, delay in project, misunderstood scope, budget blow out Likelihood: High |
High |
|
Medium |
| R02 | Risk: Change in client requirements
Cause: clients changes their mind Consequence: Scope change Likelihood: High |
Medium |
|
R08 |
| R03 | Risk: Failure to meet deadline of tasks
Cause: Tasks made unclear by Project Manager, poor time management by individuals Consequence: Project is delayed Likelihood: Medium |
Medium |
|
Low |
3.4 Monitoring and Controlling Mechanisms
1. Budget Control
Budget: The Project Manager will maintain a weekly budget report that will show any variations on budget priorities. If any anomalies exist they will be investigated and the client will be notified if significant to the impact of the budget and the plan
2. Quality Control
The Quality Engineer will audit compliance with quality standards at varies stages throughout the project life cycle and will submit a weekly report on performance against progress. A weekly meeting will also be held to discuss the results and identify areas for improvement.
3. Project Status Report
All team members are required to submit a weekly report every Friday to show performance against progress and to enable the Project Manager to identify any variations against the plan. This will provide the Project Manager with the appropriate tool to be able to effectively and efficiently manage the project.
4. Risk Control
Risks to the project must be identified and logged in the risk register and monitored during the project progress. The Quality Engineer is responsible for measure the project milestones and maintain the risk register
3.5 Staffing Plan
3.5.1 Training Strategy
Sharpwise are using qualified specialist as part of the project team. The members have over 35 years experience in software development and project management. Therefore, the skill levels are satisfied however if required training will be prov
3.5.2 Skills Needed
Sharpwise Software has a total staff of 35 business analysts, designers, programmers and project managers. The project team for the scheduling software based forms will consist of 4 team members, entailing a Project Manager, Quality Engineer, System Analyst, and one programmer. The skills needed to complete the project and are needed between the 4 team members are:
| Skills Needed | Level Requirement | Satisfied By |
| Database Design / SQL | High | Programmers |
| Java or C# .Net | High | Programmers |
| GUI Design & Development | Medium | Programmers |
| Thorough Testing | Medium | Quality Engineer |
| Microsoft Project 2007 | High | Project Manager |
| Communication skills | Medium | All team members |
| Databases and Servers | High | Programmers |
| Problems Solving Skills | High | All team members |
| Research ability | Medium | Quality Engineer |
| Management and leadership | Medium | Project manager |
| Customer Relations | High | Project Manager |
| Design skills | Medium | All team members |
| Risk management | Medium | Project Manager |
4 Technical Process
4.1 Methods, Tools and Techniques
The following is a brief overview of the techniques that will be used to complete the objectives of the project:
- Adequate product documentation to ensure even a user with very little computer expiernce can understand how to use the system created
- To deliver a quality product quality audits, flow charts and cause and effect diagrams will be used to ensure that all functions of the project work and are implemented properly
A description of the methods, tools and techniques to be used to achieve the project
objectives. This section will reference the technical references and standards used for
application of the Primary Processes. There will also be a cross-reference to relevant
sections of the Quality Plan.
4.2 Work Product Documentation
The documentation needed for the project are as follows :
- Hard copies of both user manual and technical manual
- Electronic copies of both the user manual and technical manual
All documentation must be presented in the following way :
- All manuals must have a contents page
- All manuals must have an index page
- All manuals must contain web addresses, books and other resources.
| Document | Definition | Program | Relation to SDLC |
To be Completed by |
| Team Contract | Outlines the roles each team member is responsible for | Word | Requirements | Project Manager |
| Scope Statement | The work and processes involved in creating the forms | Word | Requirements | Project Manager |
| Project Charter | Formally authorises the existence of the project | Word | Requirements | Excelsior aerospace Systems |
| Project benefits measurement information | How the product will be measured as a success | Word | Requirements | Quality Engineer |
| List of prioritised risks | Possible risks and outcomes | Word | Requirements
Design |
Quality Engineer |
| Contract files | Binding agreement that the seller must deliver the products and obligates the buyer to purchase | Word | Requirements | Project Manager |
| Milestones reports | The status and health of the project at allocated times in project | Word | Design
Implementation |
Project Manager |
| Gantt Chart | A graphical schedule for the time line of the WBS to be completed | Project | Design | Project Manager |
| WBS and WBS dictionary | A hierarchical decomposition of the work to be executed to achieve the goals and objectives | Word | Design | Project Manager |
| Survey and results | A report on the chosen layout, colour and other options available | Word | Design | Quality Engineer |
| Summary of user inputs | The required fields need to be gathered and stored, and whether fields need to be validated | Word | Design | Software Engineer |
| Progress Reports | Establishes what the team has accomplished in the time frame | Word | Design
Implementation |
Project Manager |
| Forms designs | Layouts of the forms | Word | Design | Software Engineer |
| Form contents | All the required fields needs | Word | Design | Quality Engineer |
| Test plans and reports | Documents outlining the test procedures to be carried out, and also showing the test reports | Word | Implementation
Verification |
Software Engineer |
| Roll-out information | Showing how the new system will be implemented | Word | Verification | Software Engineer |
| Final presentation | To show all outcomes and objectives have been achieved | Word | Verification | Project Manager |
| Client acceptance form | Proof that buyer accepts the product | Word | Verification | Project Manager |
| Lessons Learnt reports | Reflective statements on new ideas learnt | Word | Maintenance | Superlative Software team members |
4.3 Project Support Functions
Descriptions of and references to the documentation of relevant project support processes.
The support functions should include:
4.3.1 Quality Management
To ensure the best quality throughout the life cycle of the product, the following will be implemented:
- Checklists to ensure all processes and activities are complete at each phase
- Quality audits at the end of the evoloutionary prototyping lifecycle to ensure that at the start of the next phase of the lifecycle the issues brought up in the quality audits can be fixed.
Each phase of the life cycle will have a checklist of items to be completed before starting the next phase of the life cycle this is to ensure that all the function requirements of the project are completed.The Project Manager is in charge of making sure that each item on the checklist has been checked off. At the end of the testing phase of the evoltionary prototyping life cycle,a quality audit need to be done by the Quality Engineer so that at the begining of the next phase of the life cycle the programmers can fix the problems with the project.
4.3.2 Verification and Validation
Verification Management
The verification strategy to be applied for the project is checklists, these checklists are to ensure that all of the project function and technical requirements of the project. The project manager is responsible for making sure that all of these requirements are included into the project, the system designer/analyst’s job is to make sure that the project has all of the functional requirements are designed into the project so they can be checked off by the project manager. The programmers are responsible for implementing all of the function requirements of the project and the quality engineer is responsible for making sure that all of the requirements are up to the correct standard of quality for the project. Once the other members of the team complete their tasks, the project manager has to sign off on the project for the last time to say that everything in the project is complies to correct specifications given. The verification management technique employed will be cause and effect diagrams; these diagrams will be used to show that the function requirements have been met. These diagrams will be made during the testing phase of the project, these diagrams will highlight problem areas of the project.
Validation Management
The validation strategy involves quality audits from the Quality Engineer; these quality audits are key to ensuring that the stakeholders are confident that the project is up to the highest level of quality and that every function requirement for the project is being implemented and designed to the consumers specifications. These quality audits happen at each revision of the project so if it is not up to right standard that the stake holders are happy with the team can fix the issues the stakeholders have with the prototype in the next revision of the lifecycle. The other validation management techniques that will be implemented are flow charts, flow charts will validate the project by ensuring all of the functions of project.
4.3.3 Configuration Management
Configuration Items
- Electronic User Manual
- Hard Copy User Manual
- Job scheduling and task management software
- Project Plan
Baseline items
- Job scheduling and task management software
- Project Plan
Change Control Management Process
5 Work Packages, Schedule, and Budget
5.1 Work Packages and Dependencies
| ID | Task Name | Predecessors |
| 1 | Scheduling Software | |
| 2 | Initiating & Planning | |
| 3 | Develop Project Charter | |
| 4 | Develop Project Plan | |
| 5 | Analysis | 3 |
| 6 | Prepare SUR & Acceptance Criteria | |
| 7 | Design | |
| 8 | Functional Requirements | |
| 9 | Review Inputs | 6 |
| 10 | Analyse Requirements | 9 |
| 11 | Produce SRS | 10 |
| 12 | System Design Document | |
| 13 | Review Inputs | 11 |
| 14 | Analyse Requirements | 13 |
| 15 | Produce System Design Document | 14 |
| 16 | Test Plan | |
| 17 | Review Inputs | 6,15 |
| 18 | Develop Test Strategy | 17 |
| 19 | Develop Test Cases | 18 |
| 20 | Produce Test Plan | 19 |
| 21 | Development & Integration Testing | 7 |
| 22 | Prototype 1 | 20 |
| 23 | Design & Build Functional Requirement FR1 | |
| 24 | Initial Prototype Testing | 23 |
| 25 | Solicit & Review User Feed Back | 24 |
| 26 | Change Management Process | 25 |
| 27 | Revision 1 | 26 |
| 28 | Implement Revision 1 Changes | |
| 29 | Revision 1 Testing | 28 |
| 30 | Solicit & Review User Feed Back | 29 |
| 31 | Change Management Process | 30 |
| 32 | Revision 2 | 27 |
| 33 | Implement Revision 2 Changes | 31 |
| 34 | Revision 2 Testing | 33 |
| 35 | Create Documentation for Prototype | 24,27,32 |
| 36 | Sign Off | 35 |
| 37 | Prototype 2 | 36 |
| 38 | Design & Build Functional Requirements FR2 through FR10 | |
| 39 | Initial Prototype Testing | 38 |
| 40 | Prototype 1 Integration | 39 |
| 41 | Prototype Integration Testing | 40 |
| 42 | Solicit & Review User Feed Back | 41 |
| 43 | Change Management Process | 42 |
| 44 | Revision 1 | 43 |
| 45 | Implement Revision 1 Changes | |
| 46 | Revision 1 Testing | 45 |
| 47 | Solicit & Review User Feed Back | 46 |
| 48 | Change Management Process | 47 |
| 49 | Revision 2 | 44 |
| 50 | Implement Revision 2 Changes | 48 |
| 51 | Revision 2 Testing | 50 |
| 52 | Create Documentation for Prototype | 42,43,44 |
| 53 | Sign Off | 52 |
| 54 | Prototype 3 | 53 |
| 55 | Design & Build Functional Requirements FR11 through FR19 | |
| 56 | Initial Prototype Testing | 55 |
| 57 | Prototype 2 Integration | 56 |
| 58 | Prototype Integration Testing | 57 |
| 59 | Solicit & Review User Feed Back | 58 |
| 60 | Change Management Process | 59 |
| 61 | Revision 1 | 60 |
| 62 | Implement Revision 1 Changes | |
| 63 | Revision 1 Testing | 62 |
| 64 | Solicit & Review User Feed Back | 63 |
| 65 | Change Management Process | 64 |
| 66 | Revision 2 | 61 |
| 67 | Implement Revision 2 Changes | 65 |
| 68 | Revision 2 Testing | 67 |
| 69 | Create Documentation for Prototype | 66,59,61 |
| 70 | Sign Off | 69 |
| 71 | Prototype 4 | 54 |
| 72 | Design & Build Functional Requirements FR20 through FR28 | |
| 73 | Initial Prototype Testing | 72 |
| 74 | Prototype 3 Integration | 73 |
| 75 | Prototype Integration Testing | 74 |
| 76 | Solicit & Review User Feed Back | 75 |
| 77 | Change Management Process | 76 |
| 78 | Revision 1 | 77 |
| 79 | Implement Revision 1 Changes | |
| 80 | Revision 1 Testing | 79 |
| 81 | Solicit & Review User Feed Back | 80 |
| 82 | Change Management Process | 81 |
| 83 | Revision 2 | 78 |
| 84 | Implement Revision 2 Changes | 82 |
| 85 | Revision 2 Testing | 84 |
| 86 | Create Documentation for Prototype | 83,76,78 |
| 87 | Sign Off | 86 |
| 88 | Prototype 5 | 71 |
| 89 | Design & Build Functional Requirements FR29 through FR37 | |
| 90 | Initial Prototype Testing | 89 |
| 91 | Prototype 4 Integration | 90 |
| 92 | Prototype Integration Testing | 91 |
| 93 | Solicit & Review User Feed Back | 92 |
| 94 | Change Management Process | 93 |
| 95 | Revision 1 | 94 |
| 96 | Implement Revision 1 Changes | |
| 97 | Revision 1 Testing | 96 |
| 98 | Solicit & Review User Feed Back | 97 |
| 99 | Change Management Process | 98 |
| 100 | Revision 2 | 95 |
| 101 | Implement Revision 2 Changes | 99 |
| 102 | Revision 2 Testing | 101 |
| 103 | Create Documentation for Prototype | 100,93,95 |
| 104 | Sign Off | 103 |
| 105 | Prototype 6 | 88 |
| 106 | Design & Build Functional Requirements FR38 through FR46 | |
| 107 | Initial Prototype Testing | 106 |
| 108 | Prototype 5 Integration | 107 |
| 109 | Prototype Integration Testing | 108 |
| 110 | Solicit & Review User Feed Back | 109 |
| 111 | Change Management Process | 110 |
| 112 | Revision 1 | 111 |
| 113 | Implement Revision 1 Changes | |
| 114 | Revision 1 Testing | 113 |
| 115 | Solicit & Review User Feed Back | 114 |
| 116 | Change Management Process | 115 |
| 117 | Revision 2 | 112 |
| 118 | Implement Revision 2 Changes | 116 |
| 119 | Revision 2 Testing | 118 |
| 120 | Create Documentation for Prototype | 117,110,112 |
| 121 | Sign Off | 120 |
| 122 | Prototype 7 | 105 |
| 123 | Design & Build Functional Requirements FR47 through FR55 | |
| 124 | Initial Prototype Testing | 123 |
| 125 | Prototype 6 Integration | 124 |
| 126 | Prototype Integration Testing | 125 |
| 127 | Solicit & Review User Feed Back | 126 |
| 128 | Change Management Process | 127 |
| 129 | Revision 1 | 128 |
| 130 | Implement Revision 1 Changes | 127 |
| 131 | Revision 1 Testing | 130 |
| 132 | Solicit & Review User Feed Back | 131 |
| 133 | Change Management Process | 132 |
| 134 | Revision 2 | 129 |
| 135 | Implement Revision 2 Changes | 133 |
| 136 | Revision 2 Testing | 135 |
| 137 | Create Documentation for Prototype | 134,127,129 |
| 138 | Sign Off | 137 |
| 139 | Prototype 8 | 122 |
| 140 | Design & Build Functional Requirements FR56 through FR66 | |
| 141 | Initial Prototype Testing | 140 |
| 142 | Prototype 7 Integration | 141 |
| 143 | Prototype Integration Testing | 142 |
| 144 | Solicit & Review User Feed Back | 143 |
| 145 | Change Management Process | 144 |
| 146 | Revision 1 | 145 |
| 147 | Implement Revision 1 Changes | 144 |
| 148 | Revision 1 Testing | 147 |
| 149 | Solicit & Review User Feed Back | 148 |
| 150 | Change Management Process | 149 |
| 151 | Revision 2 | 146 |
| 152 | Implement Revision 2 Changes | 150 |
| 153 | Revision 2 Testing | 152 |
| 154 | Create Documentation for Prototype | 151,144,146 |
| 155 | Sign Off | 154 |
| 156 | Tuning & Integration | 139 |
| 157 | Final Prototype Integration | 154 |
| 158 | Final Prototype Integration Testing | 157 |
| 159 | Solicit & Review User Feedback | 158 |
| 160 | Final Changes | 159 |
| 161 | Change Testing | 160 |
| 162 | Final Documentation | 161 |
| 163 | Sign off | 162 |
5.2 Resource Requirements and Allocation
5.2.1 Function Point Analysis
Function Point Analysis based upon IFPUG ISO 14143-1 standard has been done and can be found in section 6.2. Function Point Assignment of the Appendix.
Approximated entites where modeled for use in the Function Point Analysis, and can be found in section 6.1 Entity Diagram of the Appendix.
5.2.2 Resource Allocation
| ID | Task Name | Resource Names |
| 1 | Scheduling Software | Programmer 1,Programmer 2,Project Manager,Quality Engineer,Systems Analyst / Desinger |
| 2 | Initiating & Planning | Project Manager |
| 3 | Develop Project Charter | Project Manager |
| 4 | Develop Project Plan | Project Manager |
| 5 | Analysis | Project Manager |
| 6 | Prepare SUR & Acceptance Criteria | Project Manager |
| 7 | Design | Project Manager,Systems Analyst / Desinger |
| 8 | Functional Requirements | Project Manager,Systems Analyst / Desinger |
| 9 | Review Inputs | Project Manager,Systems Analyst / Desinger |
| 10 | Analyse Requirements | Project Manager,Systems Analyst / Desinger |
| 11 | Produce SRS | Project Manager,Systems Analyst / Desinger |
| 12 | System Design Document | Project Manager,Systems Analyst / Desinger |
| 13 | Review Inputs | Project Manager,Systems Analyst / Desinger |
| 14 | Analyse Requirements | Project Manager,Systems Analyst / Desinger |
| 15 | Produce System Design Document | Project Manager,Systems Analyst / Desinger |
| 16 | Test Plan | Project Manager,Quality Engineer |
| 17 | Review Inputs | Project Manager,Quality Engineer |
| 18 | Develop Test Strategy | Project Manager,Quality Engineer |
| 19 | Develop Test Cases | Project Manager,Quality Engineer |
| 20 | Produce Test Plan | Project Manager,Quality Engineer |
| 21 | Development & Integration Testing | Programmer 1,Programmer 2,Project Manager,Quality Engineer,Systems Analyst / Desinger |
| 22 | Prototype 1 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 23 | Design & Build Functional Requirement FR1 | Programmer 1,Programmer 2,Systems Analyst / Desinger |
| 24 | Initial Prototype Testing | Quality Engineer |
| 25 | Solicit & Review User Feed Back | Project Manager,Quality Engineer |
| 26 | Change Management Process | Programmer 1,Programmer 2,Project Manager,Systems Analyst / Desinger |
| 27 | Revision 1 | Programmer 1,Programmer 2,Project Manager,Quality Engineer,Systems Analyst / Desinger |
| 28 | Implement Revision 1 Changes | Programmer 1,Programmer 2 |
| 29 | Revision 1 Testing | Quality Engineer |
| 30 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 31 | Change Management Process | Project Manager,Systems Analyst / Desinger |
| 32 | Revision 2 | Programmer 1,Programmer 2,Quality Engineer |
| 33 | Implement Revision 2 Changes | Programmer 1,Programmer 2 |
| 34 | Revision 2 Testing | Quality Engineer |
| 35 | Create Documentation for Prototype | Programmer 1,Programmer 2,Quality Engineer |
| 36 | Sign Off | Project Manager |
| 37 | Prototype 2 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 38 | Design & Build Functional Requirements FR2 through FR10 | Programmer 1,Programmer 2,Systems Analyst / Desinger |
| 39 | Initial Prototype Testing | Quality Engineer |
| 40 | Prototype 1 Integration | Programmer 1,Programmer 2 |
| 41 | Prototype Integration Testing | Project Manager |
| 42 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 43 | Change Management Process | Programmer 1,Programmer 2,Project Manager |
| 44 | Revision 1 | Quality Engineer |
| 45 | Implement Revision 1 Changes | Project Manager,Quality Engineer |
| 46 | Revision 1 Testing | Project Manager,Systems Analyst / Desinger |
| 47 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 48 | Change Management Process | Programmer 1,Programmer 2 |
| 49 | Revision 2 | Quality Engineer |
| 50 | Implement Revision 2 Changes | Programmer 1,Programmer 2,Quality Engineer |
| 51 | Revision 2 Testing | Quality Engineer |
| 52 | Create Documentation for Prototype | Programmer 1,Programmer 2 |
| 53 | Sign Off | Project Manager |
| 54 | Prototype 3 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 55 | Design & Build Functional Requirements FR11 through FR19 | Programmer 1,Programmer 2,Systems Analyst / Desinger |
| 56 | Initial Prototype Testing | Quality Engineer |
| 57 | Prototype 2 Integration | Programmer 2,Programmer 1 |
| 58 | Prototype Integration Testing | Project Manager |
| 59 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 60 | Change Management Process | Programmer 1,Programmer 2,Project Manager |
| 61 | Revision 1 | Quality Engineer |
| 62 | Implement Revision 1 Changes | Project Manager,Quality Engineer |
| 63 | Revision 1 Testing | Project Manager,Systems Analyst / Desinger |
| 64 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 65 | Change Management Process | Programmer 1,Programmer 2 |
| 66 | Revision 2 | Quality Engineer |
| 67 | Implement Revision 2 Changes | Programmer 1,Programmer 2,Quality Engineer |
| 68 | Revision 2 Testing | Quality Engineer |
| 69 | Create Documentation for Prototype | Programmer 1,Programmer 2 |
| 70 | Sign Off | Project Manager |
| 71 | Prototype 4 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 72 | Design & Build Functional Requirements FR20 through FR28 | Programmer 1,Programmer 2,Systems Analyst / Desinger |
| 73 | Initial Prototype Testing | Quality Engineer |
| 74 | Prototype 3 Integration | Programmer 1,Programmer 2 |
| 75 | Prototype Integration Testing | Project Manager |
| 76 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 77 | Change Management Process | Programmer 1,Programmer 2,Project Manager |
| 78 | Revision 1 | Quality Engineer |
| 79 | Implement Revision 1 Changes | Project Manager,Quality Engineer |
| 80 | Revision 1 Testing | Project Manager,Systems Analyst / Desinger |
| 81 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 82 | Change Management Process | Programmer 1,Programmer 2 |
| 83 | Revision 2 | Quality Engineer |
| 84 | Implement Revision 2 Changes | Programmer 1,Programmer 2,Quality Engineer |
| 85 | Revision 2 Testing | Quality Engineer |
| 86 | Create Documentation for Prototype | Programmer 1,Programmer 2 |
| 87 | Sign Off | Project Manager |
| 88 | Prototype 5 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 89 | Design & Build Functional Requirements FR29 through FR37 | Programmer 1,Programmer 2,Systems Analyst / Desinger |
| 90 | Initial Prototype Testing | Quality Engineer |
| 91 | Prototype 4 Integration | Programmer 1,Programmer 2 |
| 92 | Prototype Integration Testing | Project Manager |
| 93 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 94 | Change Management Process | Programmer 1,Programmer 2,Project Manager |
| 95 | Revision 1 | Quality Engineer |
| 96 | Implement Revision 1 Changes | Project Manager,Quality Engineer |
| 97 | Revision 1 Testing | Project Manager,Systems Analyst / Desinger |
| 98 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 99 | Change Management Process | Programmer 1,Programmer 2 |
| 100 | Revision 2 | Quality Engineer |
| 101 | Implement Revision 2 Changes | Programmer 1,Programmer 2,Quality Engineer |
| 102 | Revision 2 Testing | Quality Engineer |
| 103 | Create Documentation for Prototype | Programmer 1,Programmer 2 |
| 104 | Sign Off | Project Manager |
| 105 | Prototype 6 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 106 | Design & Build Functional Requirements FR38 through FR46 | Programmer 1,Programmer 2,Systems Analyst / Desinger |
| 107 | Initial Prototype Testing | Quality Engineer |
| 108 | Prototype 5 Integration | Programmer 1,Programmer 2 |
| 109 | Prototype Integration Testing | Project Manager |
| 110 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 111 | Change Management Process | Programmer 1,Programmer 2,Project Manager |
| 112 | Revision 1 | Quality Engineer |
| 113 | Implement Revision 1 Changes | Project Manager,Quality Engineer |
| 114 | Revision 1 Testing | Project Manager,Systems Analyst / Desinger |
| 115 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 116 | Change Management Process | Programmer 1,Programmer 2 |
| 117 | Revision 2 | Quality Engineer |
| 118 | Implement Revision 2 Changes | Programmer 1,Programmer 2,Quality Engineer |
| 119 | Revision 2 Testing | Quality Engineer |
| 120 | Create Documentation for Prototype | Programmer 1,Programmer 2 |
| 121 | Sign Off | Project Manager |
| 122 | Prototype 7 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 123 | Design & Build Functional Requirements FR47 through FR55 | Programmer 1,Programmer 2,Systems Analyst / Desinger |
| 124 | Initial Prototype Testing | Quality Engineer |
| 125 | Prototype 6 Integration | Programmer 1,Programmer 2 |
| 126 | Prototype Integration Testing | Project Manager |
| 127 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 128 | Change Management Process | Programmer 1,Programmer 2,Project Manager |
| 129 | Revision 1 | Quality Engineer |
| 130 | Implement Revision 1 Changes | Project Manager,Quality Engineer |
| 131 | Revision 1 Testing | Project Manager,Systems Analyst / Desinger |
| 132 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 133 | Change Management Process | Programmer 1,Programmer 2 |
| 134 | Revision 2 | Quality Engineer |
| 135 | Implement Revision 2 Changes | Programmer 1,Programmer 2,Quality Engineer |
| 136 | Revision 2 Testing | Quality Engineer |
| 137 | Create Documentation for Prototype | Programmer 1,Programmer 2 |
| 138 | Sign Off | Project Manager |
| 139 | Prototype 8 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 140 | Design & Build Functional Requirements FR56 through FR66 | Programmer 1,Programmer 2,Systems Analyst / Desinger |
| 141 | Initial Prototype Testing | Quality Engineer |
| 142 | Prototype 7 Integration | Programmer 1,Programmer 2 |
| 143 | Prototype Integration Testing | Project Manager |
| 144 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 145 | Change Management Process | Programmer 1,Programmer 2,Project Manager |
| 146 | Revision 1 | Quality Engineer |
| 147 | Implement Revision 1 Changes | Project Manager,Quality Engineer |
| 148 | Revision 1 Testing | Project Manager,Systems Analyst / Desinger |
| 149 | Solicit & Review User Feed Back | Project Manager,Systems Analyst / Desinger |
| 150 | Change Management Process | Programmer 1,Programmer 2 |
| 151 | Revision 2 | Quality Engineer |
| 152 | Implement Revision 2 Changes | Programmer 1,Programmer 2,Quality Engineer |
| 153 | Revision 2 Testing | Quality Engineer |
| 154 | Create Documentation for Prototype | Programmer 1,Programmer 2 |
| 155 | Sign Off | Project Manager |
| 156 | Tuning & Integration | Programmer 1,Programmer 2,Project Manager,Quality Engineer,Systems Analyst / Desinger |
| 157 | Final Prototype Integration | Programmer 1,Programmer 2 |
| 158 | Final Prototype Integration Testing | Quality Engineer |
| 159 | Solicit & Review User Feedback | Project Manager,Systems Analyst / Desinger |
| 160 | Final Changes | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger |
| 161 | Change Testing | Quality Engineer |
| 162 | Final Documentation | Programmer 1,Programmer 2 |
| 163 | Sign off | Project Manager |
5.3 Schedule
| ID | Task Name | Duration | Start | Finish | Predecessors | Resource Names |
| 1 | Scheduling Software | 96.75 days | Mon 18/10/10 | Tue 1/03/11 | Programmer 1,Programmer 2,Project Manager,Quality Engineer,Systems Analyst / Desinger | |
| 2 | Initiating & Planning | 1 day | Mon 18/10/10 | Mon 18/10/10 | Project Manager | |
| 3 | Develop Project Charter | 1 day | Mon 18/10/10 | Mon 18/10/10 | Project Manager | |
| 4 | Develop Project Plan | 1 day | Mon 18/10/10 | Mon 18/10/10 | Project Manager | |
| 5 | Analysis | 1 day | Tue 19/10/10 | Tue 19/10/10 | 3 | Project Manager |
| 6 | Prepare SUR & Acceptance Criteria | 1 day | Tue 19/10/10 | Tue 19/10/10 | Project Manager | |
| 7 | Design | 9.5 days | Wed 20/10/10 | Tue 2/11/10 | Project Manager,Systems Analyst / Desinger | |
| 8 | Functional Requirements | 3 days | Wed 20/10/10 | Fri 22/10/10 | Project Manager,Systems Analyst / Desinger | |
| 9 | Review Inputs | 1 day | Wed 20/10/10 | Wed 20/10/10 | 6 | Project Manager,Systems Analyst / Desinger |
| 10 | Analyse Requirements | 1 day | Thu 21/10/10 | Thu 21/10/10 | 9 | Project Manager,Systems Analyst / Desinger |
| 11 | Produce SRS | 1 day | Fri 22/10/10 | Fri 22/10/10 | 10 | Project Manager,Systems Analyst / Desinger |
| 12 | System Design Document | 3 days | Mon 25/10/10 | Wed 27/10/10 | Project Manager,Systems Analyst / Desinger | |
| 13 | Review Inputs | 1 day | Mon 25/10/10 | Mon 25/10/10 | 11 | Project Manager,Systems Analyst / Desinger |
| 14 | Analyse Requirements | 1 day | Tue 26/10/10 | Tue 26/10/10 | 13 | Project Manager,Systems Analyst / Desinger |
| 15 | Produce System Design Document | 1 day | Wed 27/10/10 | Wed 27/10/10 | 14 | Project Manager,Systems Analyst / Desinger |
| 16 | Test Plan | 3.5 days | Thu 28/10/10 | Tue 2/11/10 | Project Manager,Quality Engineer | |
| 17 | Review Inputs | 0.5 days | Thu 28/10/10 | Thu 28/10/10 | 6,15 | Project Manager,Quality Engineer |
| 18 | Develop Test Strategy | 1 day | Thu 28/10/10 | Fri 29/10/10 | 17 | Project Manager,Quality Engineer |
| 19 | Develop Test Cases | 1 day | Fri 29/10/10 | Mon 1/11/10 | 18 | Project Manager,Quality Engineer |
| 20 | Produce Test Plan | 1 day | Mon 1/11/10 | Tue 2/11/10 | 19 | Project Manager,Quality Engineer |
| 21 | Development & Integration Testing | 78.75 days | Tue 2/11/10 | Mon 21/02/11 | 7 | Programmer 1,Programmer 2,Project Manager,Quality Engineer,Systems Analyst / Desinger |
| 22 | Prototype 1 | 8.25 days | Tue 2/11/10 | Fri 12/11/10 | 20 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 23 | Design & Build Functional Requirement FR1 | 1 day | Tue 2/11/10 | Wed 3/11/10 | Programmer 1,Programmer 2,Systems Analyst / Desinger | |
| 24 | Initial Prototype Testing | 0.25 days | Wed 3/11/10 | Wed 3/11/10 | 23 | Quality Engineer |
| 25 | Solicit & Review User Feed Back | 1 day | Wed 3/11/10 | Thu 4/11/10 | 24 | Project Manager,Quality Engineer |
| 26 | Change Management Process | 0.5 days | Thu 4/11/10 | Fri 5/11/10 | 25 | Programmer 1,Programmer 2,Project Manager,Systems Analyst / Desinger |
| 27 | Revision 1 | 2.75 days | Fri 5/11/10 | Tue 9/11/10 | 26 | Programmer 1,Programmer 2,Project Manager,Quality Engineer,Systems Analyst / Desinger |
| 28 | Implement Revision 1 Changes | 1 day | Fri 5/11/10 | Mon 8/11/10 | Programmer 1,Programmer 2 | |
| 29 | Revision 1 Testing | 0.25 days | Mon 8/11/10 | Mon 8/11/10 | 28 | Quality Engineer |
| 30 | Solicit & Review User Feed Back | 1 day | Mon 8/11/10 | Tue 9/11/10 | 29 | Project Manager,Systems Analyst / Desinger |
| 31 | Change Management Process | 0.5 days | Tue 9/11/10 | Tue 9/11/10 | 30 | Project Manager,Systems Analyst / Desinger |
| 32 | Revision 2 | 1.25 days | Wed 10/11/10 | Thu 11/11/10 | 27 | Programmer 1,Programmer 2,Quality Engineer |
| 33 | Implement Revision 2 Changes | 1 day | Wed 10/11/10 | Wed 10/11/10 | 31 | Programmer 1,Programmer 2 |
| 34 | Revision 2 Testing | 0.25 days | Thu 11/11/10 | Thu 11/11/10 | 33 | Quality Engineer |
| 35 | Create Documentation for Prototype | 1 day | Thu 11/11/10 | Fri 12/11/10 | 24,27,32 | Programmer 1,Programmer 2,Quality Engineer |
| 36 | Sign Off | 0.5 days | Fri 12/11/10 | Fri 12/11/10 | 35 | Project Manager |
| 37 | Prototype 2 | 9 days | Fri 12/11/10 | Thu 25/11/10 | 36 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 38 | Design & Build Functional Requirements FR2 through FR10 | 1 day | Fri 12/11/10 | Mon 15/11/10 | Programmer 1,Programmer 2,Systems Analyst / Desinger | |
| 39 | Initial Prototype Testing | 0.25 days | Mon 15/11/10 | Mon 15/11/10 | 38 | Quality Engineer |
| 40 | Prototype 1 Integration | 1 day | Tue 16/11/10 | Tue 16/11/10 | 39 | Programmer 1,Programmer 2 |
| 41 | Prototype Integration Testing | 1 day | Wed 17/11/10 | Wed 17/11/10 | 40 | Project Manager |
| 42 | Solicit & Review User Feed Back | 1 day | Thu 18/11/10 | Thu 18/11/10 | 41 | Project Manager,Systems Analyst / Desinger |
| 43 | Change Management Process | 0.5 days | Fri 19/11/10 | Fri 19/11/10 | 42 | Programmer 1,Programmer 2,Project Manager |
| 44 | Revision 1 | 2.75 days | Fri 19/11/10 | Wed 24/11/10 | 43 | Quality Engineer |
| 45 | Implement Revision 1 Changes | 1 day | Fri 19/11/10 | Mon 22/11/10 | Project Manager,Quality Engineer | |
| 46 | Revision 1 Testing | 0.25 days | Mon 22/11/10 | Mon 22/11/10 | 45 | Project Manager,Systems Analyst / Desinger |
| 47 | Solicit & Review User Feed Back | 1 day | Mon 22/11/10 | Tue 23/11/10 | 46 | Project Manager,Systems Analyst / Desinger |
| 48 | Change Management Process | 0.5 days | Tue 23/11/10 | Wed 24/11/10 | 47 | Programmer 1,Programmer 2 |
| 49 | Revision 2 | 1.25 days | Wed 24/11/10 | Thu 25/11/10 | 44 | Quality Engineer |
| 50 | Implement Revision 2 Changes | 1 day | Wed 24/11/10 | Thu 25/11/10 | 48 | Programmer 1,Programmer 2,Quality Engineer |
| 51 | Revision 2 Testing | 0.25 days | Thu 25/11/10 | Thu 25/11/10 | 50 | Quality Engineer |
| 52 | Create Documentation for Prototype | 1 day | Wed 24/11/10 | Thu 25/11/10 | 42,43,44 | Programmer 1,Programmer 2 |
| 53 | Sign Off | 0.5 days | Thu 25/11/10 | Thu 25/11/10 | 52 | Project Manager |
| 54 | Prototype 3 | 10.25 days | Thu 25/11/10 | Thu 9/12/10 | 53 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 55 | Design & Build Functional Requirements FR11 through FR19 | 1 day | Thu 25/11/10 | Fri 26/11/10 | Programmer 1,Programmer 2,Systems Analyst / Desinger | |
| 56 | Initial Prototype Testing | 0.25 days | Fri 26/11/10 | Fri 26/11/10 | 55 | Quality Engineer |
| 57 | Prototype 2 Integration | 1 day | Mon 29/11/10 | Mon 29/11/10 | 56 | Programmer 2,Programmer 1 |
| 58 | Prototype Integration Testing | 1 day | Tue 30/11/10 | Tue 30/11/10 | 57 | Project Manager |
| 59 | Solicit & Review User Feed Back | 1 day | Wed 1/12/10 | Wed 1/12/10 | 58 | Project Manager,Systems Analyst / Desinger |
| 60 | Change Management Process | 0.5 days | Thu 2/12/10 | Thu 2/12/10 | 59 | Programmer 1,Programmer 2,Project Manager |
| 61 | Revision 1 | 2.75 days | Thu 2/12/10 | Tue 7/12/10 | 60 | Quality Engineer |
| 62 | Implement Revision 1 Changes | 1 day | Thu 2/12/10 | Fri 3/12/10 | Project Manager,Quality Engineer | |
| 63 | Revision 1 Testing | 0.25 days | Fri 3/12/10 | Fri 3/12/10 | 62 | Project Manager,Systems Analyst / Desinger |
| 64 | Solicit & Review User Feed Back | 1 day | Fri 3/12/10 | Mon 6/12/10 | 63 | Project Manager,Systems Analyst / Desinger |
| 65 | Change Management Process | 0.5 days | Mon 6/12/10 | Tue 7/12/10 | 64 | Programmer 1,Programmer 2 |
| 66 | Revision 2 | 1.25 days | Tue 7/12/10 | Wed 8/12/10 | 61 | Quality Engineer |
| 67 | Implement Revision 2 Changes | 1 day | Tue 7/12/10 | Wed 8/12/10 | 65 | Programmer 1,Programmer 2,Quality Engineer |
| 68 | Revision 2 Testing | 0.25 days | Wed 8/12/10 | Wed 8/12/10 | 67 | Quality Engineer |
| 69 | Create Documentation for Prototype | 1 day | Wed 8/12/10 | Thu 9/12/10 | 66,59,61 | Programmer 1,Programmer 2 |
| 70 | Sign Off | 0.5 days | Thu 9/12/10 | Thu 9/12/10 | 69 | Project Manager |
| 71 | Prototype 4 | 10.25 days | Fri 10/12/10 | Fri 24/12/10 | 54 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 72 | Design & Build Functional Requirements FR20 through FR28 | 1 day | Fri 10/12/10 | Fri 10/12/10 | Programmer 1,Programmer 2,Systems Analyst / Desinger | |
| 73 | Initial Prototype Testing | 0.25 days | Mon 13/12/10 | Mon 13/12/10 | 72 | Quality Engineer |
| 74 | Prototype 3 Integration | 1 day | Mon 13/12/10 | Tue 14/12/10 | 73 | Programmer 1,Programmer 2 |
| 75 | Prototype Integration Testing | 1 day | Tue 14/12/10 | Wed 15/12/10 | 74 | Project Manager |
| 76 | Solicit & Review User Feed Back | 1 day | Wed 15/12/10 | Thu 16/12/10 | 75 | Project Manager,Systems Analyst / Desinger |
| 77 | Change Management Process | 0.5 days | Thu 16/12/10 | Thu 16/12/10 | 76 | Programmer 1,Programmer 2,Project Manager |
| 78 | Revision 1 | 2.75 days | Thu 16/12/10 | Tue 21/12/10 | 77 | Quality Engineer |
| 79 | Implement Revision 1 Changes | 1 day | Thu 16/12/10 | Fri 17/12/10 | Project Manager,Quality Engineer | |
| 80 | Revision 1 Testing | 0.25 days | Fri 17/12/10 | Fri 17/12/10 | 79 | Project Manager,Systems Analyst / Desinger |
| 81 | Solicit & Review User Feed Back | 1 day | Mon 20/12/10 | Mon 20/12/10 | 80 | Project Manager,Systems Analyst / Desinger |
| 82 | Change Management Process | 0.5 days | Tue 21/12/10 | Tue 21/12/10 | 81 | Programmer 1,Programmer 2 |
| 83 | Revision 2 | 1.25 days | Tue 21/12/10 | Wed 22/12/10 | 78 | Quality Engineer |
| 84 | Implement Revision 2 Changes | 1 day | Tue 21/12/10 | Wed 22/12/10 | 82 | Programmer 1,Programmer 2,Quality Engineer |
| 85 | Revision 2 Testing | 0.25 days | Wed 22/12/10 | Wed 22/12/10 | 84 | Quality Engineer |
| 86 | Create Documentation for Prototype | 1 day | Wed 22/12/10 | Thu 23/12/10 | 83,76,78 | Programmer 1,Programmer 2 |
| 87 | Sign Off | 0.5 days | Thu 23/12/10 | Fri 24/12/10 | 86 | Project Manager |
| 88 | Prototype 5 | 10.25 days | Fri 24/12/10 | Fri 7/01/11 | 71 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 89 | Design & Build Functional Requirements FR29 through FR37 | 1 day | Fri 24/12/10 | Mon 27/12/10 | Programmer 1,Programmer 2,Systems Analyst / Desinger | |
| 90 | Initial Prototype Testing | 0.25 days | Mon 27/12/10 | Mon 27/12/10 | 89 | Quality Engineer |
| 91 | Prototype 4 Integration | 1 day | Mon 27/12/10 | Tue 28/12/10 | 90 | Programmer 1,Programmer 2 |
| 92 | Prototype Integration Testing | 1 day | Tue 28/12/10 | Wed 29/12/10 | 91 | Project Manager |
| 93 | Solicit & Review User Feed Back | 1 day | Wed 29/12/10 | Thu 30/12/10 | 92 | Project Manager,Systems Analyst / Desinger |
| 94 | Change Management Process | 0.5 days | Thu 30/12/10 | Thu 30/12/10 | 93 | Programmer 1,Programmer 2,Project Manager |
| 95 | Revision 1 | 2.75 days | Fri 31/12/10 | Tue 4/01/11 | 94 | Quality Engineer |
| 96 | Implement Revision 1 Changes | 1 day | Fri 31/12/10 | Fri 31/12/10 | Project Manager,Quality Engineer | |
| 97 | Revision 1 Testing | 0.25 days | Mon 3/01/11 | Mon 3/01/11 | 96 | Project Manager,Systems Analyst / Desinger |
| 98 | Solicit & Review User Feed Back | 1 day | Mon 3/01/11 | Tue 4/01/11 | 97 | Project Manager,Systems Analyst / Desinger |
| 99 | Change Management Process | 0.5 days | Tue 4/01/11 | Tue 4/01/11 | 98 | Programmer 1,Programmer 2 |
| 100 | Revision 2 | 1.25 days | Tue 4/01/11 | Wed 5/01/11 | 95 | Quality Engineer |
| 101 | Implement Revision 2 Changes | 1 day | Tue 4/01/11 | Wed 5/01/11 | 99 | Programmer 1,Programmer 2,Quality Engineer |
| 102 | Revision 2 Testing | 0.25 days | Wed 5/01/11 | Wed 5/01/11 | 101 | Quality Engineer |
| 103 | Create Documentation for Prototype | 1 day | Thu 6/01/11 | Thu 6/01/11 | 100,93,95 | Programmer 1,Programmer 2 |
| 104 | Sign Off | 0.5 days | Fri 7/01/11 | Fri 7/01/11 | 103 | Project Manager |
| 105 | Prototype 6 | 10.25 days | Fri 7/01/11 | Fri 21/01/11 | 88 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 106 | Design & Build Functional Requirements FR38 through FR46 | 1 day | Fri 7/01/11 | Mon 10/01/11 | Programmer 1,Programmer 2,Systems Analyst / Desinger | |
| 107 | Initial Prototype Testing | 0.25 days | Mon 10/01/11 | Mon 10/01/11 | 106 | Quality Engineer |
| 108 | Prototype 5 Integration | 1 day | Mon 10/01/11 | Tue 11/01/11 | 107 | Programmer 1,Programmer 2 |
| 109 | Prototype Integration Testing | 1 day | Tue 11/01/11 | Wed 12/01/11 | 108 | Project Manager |
| 110 | Solicit & Review User Feed Back | 1 day | Wed 12/01/11 | Thu 13/01/11 | 109 | Project Manager,Systems Analyst / Desinger |
| 111 | Change Management Process | 0.5 days | Thu 13/01/11 | Fri 14/01/11 | 110 | Programmer 1,Programmer 2,Project Manager |
| 112 | Revision 1 | 2.75 days | Fri 14/01/11 | Tue 18/01/11 | 111 | Quality Engineer |
| 113 | Implement Revision 1 Changes | 1 day | Fri 14/01/11 | Mon 17/01/11 | Project Manager,Quality Engineer | |
| 114 | Revision 1 Testing | 0.25 days | Mon 17/01/11 | Mon 17/01/11 | 113 | Project Manager,Systems Analyst / Desinger |
| 115 | Solicit & Review User Feed Back | 1 day | Mon 17/01/11 | Tue 18/01/11 | 114 | Project Manager,Systems Analyst / Desinger |
| 116 | Change Management Process | 0.5 days | Tue 18/01/11 | Tue 18/01/11 | 115 | Programmer 1,Programmer 2 |
| 117 | Revision 2 | 1.25 days | Wed 19/01/11 | Thu 20/01/11 | 112 | Quality Engineer |
| 118 | Implement Revision 2 Changes | 1 day | Wed 19/01/11 | Wed 19/01/11 | 116 | Programmer 1,Programmer 2,Quality Engineer |
| 119 | Revision 2 Testing | 0.25 days | Thu 20/01/11 | Thu 20/01/11 | 118 | Quality Engineer |
| 120 | Create Documentation for Prototype | 1 day | Thu 20/01/11 | Fri 21/01/11 | 117,110,112 | Programmer 1,Programmer 2 |
| 121 | Sign Off | 0.5 days | Fri 21/01/11 | Fri 21/01/11 | 120 | Project Manager |
| 122 | Prototype 7 | 10.25 days | Fri 21/01/11 | Fri 4/02/11 | 105 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 123 | Design & Build Functional Requirements FR47 through FR55 | 1 day | Fri 21/01/11 | Mon 24/01/11 | Programmer 1,Programmer 2,Systems Analyst / Desinger | |
| 124 | Initial Prototype Testing | 0.25 days | Mon 24/01/11 | Mon 24/01/11 | 123 | Quality Engineer |
| 125 | Prototype 6 Integration | 1 day | Tue 25/01/11 | Tue 25/01/11 | 124 | Programmer 1,Programmer 2 |
| 126 | Prototype Integration Testing | 1 day | Wed 26/01/11 | Wed 26/01/11 | 125 | Project Manager |
| 127 | Solicit & Review User Feed Back | 1 day | Thu 27/01/11 | Thu 27/01/11 | 126 | Project Manager,Systems Analyst / Desinger |
| 128 | Change Management Process | 0.5 days | Fri 28/01/11 | Fri 28/01/11 | 127 | Programmer 1,Programmer 2,Project Manager |
| 129 | Revision 1 | 2.75 days | Fri 28/01/11 | Wed 2/02/11 | 128 | Quality Engineer |
| 130 | Implement Revision 1 Changes | 1 day | Fri 28/01/11 | Mon 31/01/11 | 127 | Project Manager,Quality Engineer |
| 131 | Revision 1 Testing | 0.25 days | Mon 31/01/11 | Mon 31/01/11 | 130 | Project Manager,Systems Analyst / Desinger |
| 132 | Solicit & Review User Feed Back | 1 day | Mon 31/01/11 | Tue 1/02/11 | 131 | Project Manager,Systems Analyst / Desinger |
| 133 | Change Management Process | 0.5 days | Tue 1/02/11 | Wed 2/02/11 | 132 | Programmer 1,Programmer 2 |
| 134 | Revision 2 | 1.25 days | Wed 2/02/11 | Thu 3/02/11 | 129 | Quality Engineer |
| 135 | Implement Revision 2 Changes | 1 day | Wed 2/02/11 | Thu 3/02/11 | 133 | Programmer 1,Programmer 2,Quality Engineer |
| 136 | Revision 2 Testing | 0.25 days | Thu 3/02/11 | Thu 3/02/11 | 135 | Quality Engineer |
| 137 | Create Documentation for Prototype | 1 day | Thu 3/02/11 | Fri 4/02/11 | 134,127,129 | Programmer 1,Programmer 2 |
| 138 | Sign Off | 0.5 days | Fri 4/02/11 | Fri 4/02/11 | 137 | Project Manager |
| 139 | Prototype 8 | 10.25 days | Mon 7/02/11 | Mon 21/02/11 | 122 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger,Project Manager |
| 140 | Design & Build Functional Requirements FR56 through FR66 | 1 day | Mon 7/02/11 | Mon 7/02/11 | Programmer 1,Programmer 2,Systems Analyst / Desinger | |
| 141 | Initial Prototype Testing | 0.25 days | Tue 8/02/11 | Tue 8/02/11 | 140 | Quality Engineer |
| 142 | Prototype 7 Integration | 1 day | Tue 8/02/11 | Wed 9/02/11 | 141 | Programmer 1,Programmer 2 |
| 143 | Prototype Integration Testing | 1 day | Wed 9/02/11 | Thu 10/02/11 | 142 | Project Manager |
| 144 | Solicit & Review User Feed Back | 1 day | Thu 10/02/11 | Fri 11/02/11 | 143 | Project Manager,Systems Analyst / Desinger |
| 145 | Change Management Process | 0.5 days | Fri 11/02/11 | Fri 11/02/11 | 144 | Programmer 1,Programmer 2,Project Manager |
| 146 | Revision 1 | 2.75 days | Fri 11/02/11 | Wed 16/02/11 | 145 | Quality Engineer |
| 147 | Implement Revision 1 Changes | 1 day | Fri 11/02/11 | Mon 14/02/11 | 144 | Project Manager,Quality Engineer |
| 148 | Revision 1 Testing | 0.25 days | Mon 14/02/11 | Mon 14/02/11 | 147 | Project Manager,Systems Analyst / Desinger |
| 149 | Solicit & Review User Feed Back | 1 day | Tue 15/02/11 | Tue 15/02/11 | 148 | Project Manager,Systems Analyst / Desinger |
| 150 | Change Management Process | 0.5 days | Wed 16/02/11 | Wed 16/02/11 | 149 | Programmer 1,Programmer 2 |
| 151 | Revision 2 | 1.25 days | Wed 16/02/11 | Thu 17/02/11 | 146 | Quality Engineer |
| 152 | Implement Revision 2 Changes | 1 day | Wed 16/02/11 | Thu 17/02/11 | 150 | Programmer 1,Programmer 2,Quality Engineer |
| 153 | Revision 2 Testing | 0.25 days | Thu 17/02/11 | Thu 17/02/11 | 152 | Quality Engineer |
| 154 | Create Documentation for Prototype | 1 day | Thu 17/02/11 | Fri 18/02/11 | 151,144,146 | Programmer 1,Programmer 2 |
| 155 | Sign Off | 0.5 days | Fri 18/02/11 | Mon 21/02/11 | 154 | Project Manager |
| 156 | Tuning & Integration | 6.5 days | Mon 21/02/11 | Tue 1/03/11 | 139 | Programmer 1,Programmer 2,Project Manager,Quality Engineer,Systems Analyst / Desinger |
| 157 | Final Prototype Integration | 1 day | Mon 21/02/11 | Tue 22/02/11 | 154 | Programmer 1,Programmer 2 |
| 158 | Final Prototype Integration Testing | 1 day | Tue 22/02/11 | Wed 23/02/11 | 157 | Quality Engineer |
| 159 | Solicit & Review User Feedback | 1 day | Wed 23/02/11 | Thu 24/02/11 | 158 | Project Manager,Systems Analyst / Desinger |
| 160 | Final Changes | 1 day | Thu 24/02/11 | Fri 25/02/11 | 159 | Programmer 1,Programmer 2,Quality Engineer,Systems Analyst / Desinger |
| 161 | Change Testing | 1 day | Fri 25/02/11 | Mon 28/02/11 | 160 | Quality Engineer |
| 162 | Final Documentation | 1 day | Mon 28/02/11 | Tue 1/03/11 | 161 | Programmer 1,Programmer 2 |
| 163 | Sign off | 0.5 days | Tue 1/03/11 | Tue 1/03/11 | 162 | Project Manager |
5.3.3 Gantt Chart
Appendix
6.1. Entity Diagram
6.2. Function Point Assignment
| I.D | Description | Type | Complexity | Points |
| FR1 | The system will have a master form containing tabs for each job elements | EQ | High | 6 |
| FR2 | The system will have a tab form for job element: Curtains/Sheers/Tie-backs/Cushions | ILF | Low | 7 |
| FR3 | The system will have a ‘reminder date to order/date to write worksheets’ inside tab job element: Curtains/Sheers/Tie-backs/Cushions | EQ | Low | 3 |
| FR4 | The system will have a popup ‘reminder date to order/date to write worksheets’ on tab job element: Curtains/Sheers/Tie-backs/Cushions inside diary | EQ | Low | 3 |
| FR5 | The system will have a ‘reminder date ordered/date worksheet given to maker’ inside tab job element: Curtains/Sheers/Tie-backs/Cushions | EQ | Low | 3 |
| FR6 | The system will have ‘follow up date if not arrived/completed by’ inside tab job element: Curtains/Sheers/Tie-backs/Cushions | EQ | Low | 3 |
| FR7 | The system will have popup ‘follow up date if not arrived/completed by’ on tab job element: Curtains/Sheers/Tie-backs/Cushions inside diary | EQ | Low | 3 |
| FR8 | The system will have ‘arrival date/completion date’ inside tab job element: Curtains/Sheers/Tie-backs/Cushions | EQ | Low | 3 |
| FR9 | The system will have ‘finalisation/outstanding items’ inside tab job element: Curtains/Sheers/Tie-backs/Cushions | EQ | Low | 3 |
| FR10 | The system will have ‘popup finalisation/outstanding items’ on tab job element: Curtains/Sheers/Tie-backs/Cushions inside diary | EQ | Low | 3 |
| FR11 | The system will have a form tab for job element: Tracks/Wooden-pelmets | ILF | Low | 7 |
| FR12 | The system will have ‘reminder date to order/date to write worksheets’ inside tab job element: Tracks/Wooden-pelmets | EQ | Low | 3 |
| FR13 | The system will have popup ‘reminder date to order/date to write worksheets’ on tab job element: Tracks/Wooden-pelmets | EQ | Low | 3 |
| FR14 | The system will have ‘reminder date ordered/date worksheet given to maker’ inside tab job element: Tracks/Wooden-pelmets | EQ | Low | 3 |
| FR15 | The system will have ‘follow up date if not arrived/completed by’ inside tab job element: Tracks/Wooden-pelmets | EQ | Low | 3 |
| FR16 | The system will have ‘follow up date if not arrived/completed by’ on tab job element: Tracks/Wooden-pelmets inside diary | EQ | Low | 3 |
| FR17 | The system will have ‘arrival date/completion date’ inside tab job element: Tracks/Wooden-pelmets | EQ | Low | 3 |
| FR18 | The system will have ‘finalisation/outstanding items’ inside tab job element: Tracks/Wooden-pelmets | EQ | Low | 3 |
| FR19 | The system will have ‘popup finalisation/outstanding items’ on tab job element: Tracks/Wooden-pelmets inside diary | EQ | Low | 3 |
| FR20 | The system will have a form tab for job element: Blinds/Shutters | ILF | Low | 7 |
| FR21 | The system will have ‘reminder date to order/date to write worksheets’ inside tab job element: Blinds/Shutters | EQ | Low | 3 |
| FR22 | The system will have popup ‘reminder date to order/date to write worksheets’ on tab job element: Blinds/Shutters inside diary | EQ | Low | 3 |
| FR23 | The system will have ‘reminder date ordered/date worksheet given to maker’ inside tab job element: Blinds/Shutters | EQ | Low | 3 |
| FR24 | The system will have ‘follow up date if not arrived/completed by’ inside tab job element: Blinds/Shutters | EQ | Low | 3 |
| FR25 | The system will have popup ‘follow up date if not arrived/completed by’ on tab job element: Blinds/Shutters inside diary | EQ | Low | 3 |
| FR26 | The system will have ‘arrival date/completion date’ inside tab job element: Blinds/Shutters | EQ | Low | 3 |
| FR27 | The system will have ‘finalisation/outstanding items’ inside tab job element: Blinds/Shutters | EQ | Low | 3 |
| FR28 | The system will have popup ‘finalisation/outstanding items’ on tab job element: Blinds/Shutters inside diary | EQ | Low | 3 |
| FR29 | The system will have a form tab for job element: Padded-pelmets | ILF | Low | 7 |
| FR30 | The system will have ‘reminder date to order/date to write worksheets’ inside tab job element: Padded-pelmets | EQ | Low | 3 |
| FR31 | The system will have popup ‘reminder date to order/date to write worksheets’ on tab job element: Padded-pelmets inside diary | EQ | Low | 3 |
| FR32 | The system will have ‘reminder date ordered/date worksheet given to maker’ inside tab job element: Padded-pelmets | EQ | Low | 3 |
| FR33 | The system will have ‘follow up date if not arrived/completed by’ inside tab job element: Padded-pelmets | EQ | Low | 3 |
| FR34 | The system will have popup ‘follow up date if not arrived/completed by’ on tab job element: Padded-pelmets inside diary | EQ | Low | 3 |
| FR35 | The system will have ‘arrival date/completion date’ inside tab job element: Padded-pelmets | EQ | Low | 3 |
| FR36 | The system will have ‘finalisation/outstanding items’ inside tab job element: Padded-pelmets | EQ | Low | 3 |
| FR37 | The system will have popup ‘finalisation/outstanding items’ on tab job element: Padded-pelmets inside diary | EQ | Low | 3 |
| FR38 | The system will have a form tab for job element: Installation/Customer notification – ready to collect | ILF | Low | 7 |
| FR39 | The system will have ‘reminder date to order/date to write worksheets’ inside tab job element: Installation/Customer notification – ready to collect | EQ | Low | 3 |
| FR40 | The system will have popup ‘reminder date to order/date to write worksheets’ on tab job element: Installation/Customer notification – ready to collect inside diary | EQ | Low | 3 |
| FR41 | The system will have ‘reminder date ordered/date worksheet given to maker’ inside tab job element: Installation/Customer notification – ready to collect | EQ | Low | 3 |
| FR42 | The system will have ‘follow up date if not arrived/completed by’ inside tab job element: Installation/Customer notification – ready to collect | EQ | Low | 3 |
| FR43 | The system will have popup ‘follow up date if not arrived/completed by’ on tab job element: Installation/Customer notification – ready to collect inside diary | EQ | Low | 3 |
| FR44 | The system will have ‘arrival date/completion date’ inside tab job element: Installation/Customer notification – ready to collect | EQ | Low | 3 |
| FR45 | The system will have ‘finalisation/outstanding items’ inside tab job element: Installation/Customer notification – ready to collect | EQ | Low | 3 |
| FR46 | The system will have popup ‘finalisation/outstanding items’ on tab job element: Installation/Customer notification – ready to collect inside diary | EQ | Low | 3 |
| FR47 | The system will have a form tab for job element: Fabric/Trims & Accessories being ordered | ILF | Low | 7 |
| FR48 | The system will have ‘reminder date to order/date to write worksheets’ inside tab job element: Fabric/Trims & Accessories being ordered | EQ | Low | 3 |
| FR49 | The system will have popup ‘reminder date to order/date to write worksheets’ on tab job element: Fabric/Trims & Accessories being ordered inside diary | EQ | Low | 3 |
| FR50 | The system will have ‘reminder date ordered/date worksheet given to maker’ inside tab job element: Fabric/Trims & Accessories being ordered | EQ | Low | 3 |
| FR51 | The system will have ‘follow up date if not arrived/completed by’ inside tab job element: Fabric/Trims & Accessories being ordered | EQ | Low | 3 |
| FR52 | The system will have popup ‘follow up date if not arrived/completed by’ on tab job element: Fabric/Trims & Accessories being ordered | EQ | Low | 3 |
| FR53 | The system will have ‘arrival date/completion date’ inside tab job element: Fabric/Trims & Accessories being ordered | EQ | Low | 3 |
| FR54 | The system will have ‘finalisation/outstanding items’ inside tab job element: Fabric/Trims & Accessories being ordered | EQ | Low | 3 |
| FR55 | The system will have popup ‘finalisation/outstanding items’ on tab job element: Fabric/Trims & Accessories being ordered inside diary | EQ | Low | 3 |
| FR56 | The system will have one tab on the master form for all recurring tasks such as BAS, cleaning the windows, cleaning showroom, check various stock levels, ETC | ILF | Low | 7 |
| FR57 | The system will have ‘date to start task’ for each task in the recurring task form | EQ | Low | 3 |
| FR58 | The system will have popup ‘date to start task’ from the recurring task form into the diary | EQ | Low | 3 |
| FR59 | The system will have ‘title of person who should do the task’ for all tasks inside the recurring task form | EQ | Low | 3 |
| FR60 | The system will have ‘name of person in current position to do task’ inside the recurring task form | EQ | Low | 3 |
| FR61 | The system will have ‘deadline to finish task’ inside the recurring task form | EQ | Low | 3 |
| FR62 | The system will have popup ‘deadline to finish task’ from recurring task form into diary | EQ | Low | 3 |
| FR63 | The system will have ‘user input notes section’ inside recurring task form | EQ | Low | 3 |
| FR64 | The system will have popup ‘alert to inform customers of delays’ into diary | EQ | Low | 3 |
| FR65 | The system will allow supervisors to sign off important tasks | ILF | Low | 7 |
| FR66 | The system will not allow jobs to be deleted without supervisor sign off | ILF | Low | 7 |
| Total | 237 |
6.3. MS Project 2010 File
Gantt & Network Diagrams are included as part of this file.
Please note this file uses the MS Project 2010 File Format.
6.4 Risk Assesment
| Risk No | Risk (Cause and Consequence) | Pre-Strategy Risk Exposure | Strategy Description | Residual Risk Exposure |
| R01 | Risk: Excelsior staff do not use system.
Cause: Lack of communication and business buy-in. Consequence: System perceived as a failure to business and benefits not realised. Likelihood: Medium |
High |
|
Medium |
| R02 | Risk: Lack of executive level support.
Cause: Competing priorities or lack of understanding. Consequence: Project does not progress, or is delayed excessively. Likelihood: Low |
Medium |
|
Low |
| R03 | Risk: Database system is poorly supported by Superlative post implementation.
Cause: Unclear handover from project team to operational team. Consequence: Database System is operationally unstable. Likelihood: Medium |
Medium |
|
Low |
| R04 | Risk: Scope Creep in project
Cause: Increased customer requirements added after planning stage of project. Consequence: Project is delayed. Likelihood: Medium |
Low |
|
Low |
| R05 | Risk: Lack of example documentation and project team experience with full ICT Project Lifecycle.
Cause: ICT Project Lifecycle has been reviewed and no example/case study documentation exists. Consequence: Project is delayed. Likelihood: Low |
Low |
|
Low |
| R06 | Risk: Failure to meet deadline of tasks
Cause: Tasks made unclear by Project Manager Consequence: Project is delayed Likelihood: Medium |
Medium |
|
Low |
| R07 | Risk: Changes to resource level
Cause: Staff find another job, staff have other priorities Consequence: Delay project Likelihood: Medium
|
Low |
|
Low |
| R08 | Risk: Change in client requirements
Cause: clients changes their mind Consequence: Scope change Likelihood: High |
Medium |
|
Medium |
| R09 | Risk: Hardware compatibility issues
Cause: any new hardware want communicate with existing infrastructure Consequence: Budget cost blow out and delay in project Likelihood: Low |
Low |
|
Low |
| R10 | Risk: Software compatibility issues
Cause: Proposed software want communicate with existing software Consequence: Blow out in budget and delay in project Likelihood: Medium |
Medium |
|
Medium |
| R11 | Risk: Budget problems
Cause: Client can not longer fund project Consequence: Project stop Likelihood: Medium |
High |
|
Medium |
| R12 | Risk: Poor communication
Cause: Project team and/or client are not communicating Consequence: Requirements not understood, Errors in project phases, delay in project, misunderstood scope, budget blow out Likelihood: High |
High |
|
Medium |
| R13 | Risk: Conflict among team members
Cause: Different personalities clashing Likelihood: Medium |
Medium |
|
Medium |