1
Contents
1.0 Goals and Objectives
1.1 Project name
1.2 Business goals
1.2.1 Project goals
1.3 Scope
1.4 Time and budget constraints
Schedule
Budget Estimation
1.5 General and technical requirements
2.0 Project Estimates
2.1 People cost
Historical estimation of data
2.2 Equipment costs
2.3 Estimation techniques
2.3.1 Process based estimation
2.3.2 Time-phased estimation i.e. top down approach
Analysis of two cost-estimation techniques
3.0 Project Schedule
4.0 Staff Organization
4.1 Team structure
4.2 Management reporting and communication
5.0 Risk management
5.1 Project Risks
5.2 Risk Table
5.3 Risk Mitigation, Monitoring, Management Strategy
6.0 Tracking and Control Mechanisms
6.1 Quality assurance and control
6.2 Change management and control
1.0 Goals and Objectives
1.1 Project name
Website development for Matco LTD
1.2 Business goals
Following are the key business goals:
- Increase in user base - The website will help the non-profit organization to increase its reach to more people.
- Increase in awareness - The website will help the organization to increase awareness among the users and they will come forward to contribute in it.
1.2.1 Project goals
Purpose for this project is to design and develop a website for the not-for-profit organization. It includes all activities related to website development starting from gathering requirements to the final stage of testing and delivering a usable website. Objective here being that the organization needs to be able to leverage demands to serve their members and people they serve. Their members should be able to gather the required information about the organization and its activities among other things from their website. The website should support the organization in their efforts and endeavors the best way it can and help make a name for themselves and carve out a space for themselves.
1.3 Scope
The scope of the website is to design and develop a fully functional website which works and functions based on the requirements framed out by the organization. The website will be divided into two parts i.e., a front-end and a backend part. The frontend part will be for the people the organization serves and the back-end would be for those who will be responsible for managing the contents of the website. Website development involves listing out requirements, getting it approved from the organization, developing a prototype for the website, designing the look, feel and the interface of the website, coding, finally ending up with testing and delivery. The website will be developed in the given timeline and budget. This project does not take into account activities such as raising finance, marketing and allied activities among others.
1.4 Time and budget constraints
Following are some of the constraints which affect the current project:
- Time: This project must complete within the identified time frame or else it would require an additional set of resources and budget.
- Budget: This project must complete within the identified budget or else sponsors would have to provide additional funding’s should the project overshoots its budget.
- Resources: The project must have skilled and dedicated resources. They should be available throughout or on the basis of their requirements in the project.
- Standards: The website would be developed using standard industry best practices so as to ensure maximum compatibility and acceptable level of security. Along with this, validation services such as W3C would be used to further improve the website. It will be developed using licensed and legal technologies.
Schedule
This project is expected to complete within a period of 92 days. It will begin on 3rd of November 2014 and end on 10th March 2015. All of the resources assigned to the project must work for 8 hours a day and be available as long as the project requires them after factoring in Saturdays, Sundays as well as other holidays.
Budget Estimation
The market has been studied thoroughly to come up with the best possible and closest cost for the project. This includes taking references from similar companies who have done similar project. The phases of project are coordinated with the help of time and cost estimation techniques. In early phase of planning i.e., the assumptions, scope, method as well as current situation, early time and cost estimation all would be done with the help of components, bucket method while keeping contingency levels in the range of -50 to +100%. In WBS, detailed time estimation will be done with the help of PERT, project budget, bottom-up cost estimation technique while keeping contingency levels in the range of -10 to +15%.
1.5 General and technical requirements
Best ($) / Worth ($) / Average ($)Hardware resources / Server resources / 300 / 250 / 250
DB server / 300 / 250 / 250
Machines (2) / 400 / 500 / 400
Software resources / MS Office Suite / 400 / 400 / 400
Programming languages / Open source (Php) / -
Database / Open source (MySQL) / -
Application server / Open source (Apache Tomcat) / -
Office space / - / 500 / 600 / 550
Team / Project manager (PM) / 120 / 130 / 125
System Analyst (SA) / 90 / 90 / 90
Network Engineer (NE) / 40 / 50 / 45
Staffing Manager (SM) / 85 / 80 / 80
Cost Manager (CM) / 70 / 70 / 70
Developer head (DH) / 90 / 90 / 90
DBA / 80 / 80 / 80
Testing head (TH) / 70 / 70 / 70
2.0 Project Estimates
Budget estimation has been done for the Matco LTD new project of website development. The costs have been prepared from historical data collected from similar projects. In addition to this, two cost estimations techniques have also been employed.
2.1 People cost
Historical estimation of data
In order to estimate the average salaries of resources involved in the project, local data and salary data of similar projects are collected. Following table depicts the collected data:
Role / Avg. Salary($) / Administrative cost (30%) ($) / Avg. salary/month ($)Project manager / 55,000 / 82500 / 6875
System analyst / 45000 / 67500 / 5625
Network engineer / 35000 / 52500 / 4375
Staffing manager / 65000 / 97500 / 8125
Cost manager / 67000 / 100500 / 8375
Developer head / 70000 / 105000 / 8750
DBA / 55000 / 82500 / 6875
Testing head / 44000 / 66000 / 5500
The table above shows average salary for the of all professionals. This average salary however does not include administrative costs which are associated with every employee. An approximate figure of 30% of every employee’s salary is typically included in the administrative costs. This salary value is displayed in second last column of table. The last column adjusts salary on a per month basis.
2.2 Equipment costs
Following table depicts the hardware and software costs associated with the project:
Best ($) / Worth ($) / Average ($)Hardware resources / Server resources / 350 / 250 / 300
Database server / 350 / 250 / 200
Machines (2) / 500 / 500 / 350
Software resources / MS Office Suite / 450 / 400 / 425
Programming languages / Php / -
Database / MySQL / -
Application server / Apache Tomcat / -
2.3 Estimation techniques
To arrive at a project cost, a good study of the market is to be done. The similar projects done by other organizations were also considered as a reference. The project also took care of uncommon necessities through the contingencies. The cost and time estimation methods were also used to coordinate project planning phases. Initial planning stage which comprises of methods, scoping, assumptions and current situations, time and cost estimation could be done by the component and the bucket method by taking contingency in the range of -50 to +100%. The project plan includes work breakdown structure or WB and it also includes the activity list. The detailed time estimate could be calculated by using the bottom-up cost estimation technique, PERT, project budget and while taking the contingency level in the ranges of -10 to +15%.
The project uses following two cost estimation approaches:
2.3.1 Process based estimation
This estimation involves breaking the project into smaller set of task as mentioned below:
- No.
1 / Design user interfaces / DUI
2 / Design database / DD
3 / Develop searching mechanism / DSM
4 / Develop calculation algorithm / DCA
5 / Develop authentication mechanism / DAM
6 / Database automatic backup / DAB
7 / Report generation / RG
Activity / Planning / Risk / Analysis / Design / Code / Test / Evaluation / Total
DUI / 0.07 / 0.05 / 0.35 / 0.4 / 0.4 / 0.4 / 0.2 / 1.87
DD / 0.06 / 0.03 / 0.38 / 0.35 / 0.29 / 0.33 / 0.08 / 1.52
DSM / 0.04 / 0.04 / 0.25 / 0.3 / 0.4 / 0.35 / 0.04 / 1.42
DCA / 0.07 / 0.03 / 0.11 / 0.25 / 0.45 / 0.4 / 0.04 / 1.35
DAM / 0.04 / 0.02 / 0.12 / 0.38 / 0.45 / 0.4 / 0.05 / 1.46
DAB / 0.03 / 0.03 / 0.11 / 0.25 / 0.3 / 0.2 / 0.03 / 0.95
RG / 0.02 / 0.01 / 0.13 / 0.2 / 0.15 / 0.1 / 0.03 / 0.64
Total / 0.33 / 0.21 / 1.45 / 2.13 / 2.44 / 2.18 / 0.47 / 9.21
%effort / 3.50% / 2.20% / 15% / 23% / 26% / 23% / 5% / 100%
The calculation depicts that the project will take 9.21person-months to complete. The project team consists of:
- Project manager
- System analyst
- Network engineer
- Staffing manager
- Cost manager
- Developer head
- DBA
- Testing head
All the team members contribute to the project but in a varying range i.e. project manager 100% involves in the project, system analyst will be involved 25% of the project time, network engineer and testing head will be 15% of the project time.
But above this, there will be an extra over and above the base project time because of the communication lag which happens among the team member. The required amount of time to complete the project:
9.21*1.35/4 = 3.22 months.
Role / CostProject manager / 22137.5
System analyst / 18112.5
Network engineer / 14087.5
Staffing manager / 26162.5
Cost manager / 26967.5
Developer head / 28175
DBA / 22137.5
Testing head / 17710
Total cost / 175490
Total cost of the project team = $175490
2.3.2 Time-phased estimation i.e. top down approach
Cost estimation in this project was done on basis of a top-down approach. The time phased approach could not be implemented in this case as it’s an unusual system development project wherein particular task takes days extending upto weeks in comparison to other projects. Each of the activity is assigned a particular resource along with a cost correspondingly. Budget allocation of each activity was done on basis of prior experience and Internet references. Prior experience includes contingencies, which aren’t catered to at time of budget allocation. There are risks involved as well. To manage the risk, a risk management plan needs to be drafted which will then help sort the risks based on priority, impact among other things and help list down whether they should be accepted, avoided, eliminated or transferred. Internet references are not credible always; hence it should be associated with some risks and contingencies too.
Analysis of two cost-estimation techniques
The time-phased and process-based takes WBS as their base. This is the key similarity however; in time phased the budget is allocated only after breaking down the project into fine grain levels. But the process based keep the budget allocation limited to key requirements of the project i.e. fully developed WBS is not required in process-based estimation.
3.0 Project Schedule
This section presents an overview of project tasks and the output of a project scheduling tool.
The High Level plan in terms of Summary Tasks can be shown as:
Task Mode / Task Name / Duration / Start / FinishAuto Scheduled / Baseline Planning for Website / 8 days / Mon 11/3/14 / Wed 11/12/14
Auto Scheduled / Architectural plan of Website / 4 days / Thu 11/13/14 / Tue 11/18/14
Auto Scheduled / Preliminary design / specification / 20 days / Wed 11/19/14 / Tue 12/16/14
Auto Scheduled / Website Development / 30 days / Wed 12/17/14 / Tue 1/27/15
Auto Scheduled / Test Run Completion / 25 days / Wed 1/28/15 / Tue 3/3/15
3.1 Project task list
The Detailed plan can be shown as:
Auto Scheduled / Baseline Planning for Website / 8 days / Mon 11/3/14 / Wed 11/12/14
Auto Scheduled / Start the Base Line Planning / 8 days / Mon 11/3/14 / Wed 11/12/14
Auto Scheduled / Stakeholder Analysis / 3 days / Mon 11/3/14 / Wed 11/5/14
Auto Scheduled / Identify all the Stakeholders / 1 day / Mon 11/3/14 / Mon 11/3/14
Auto Scheduled / Discuss the scope with all the stakeholders / 1 day / Tue 11/4/14 / Tue 11/4/14 / 4
Auto Scheduled / Take Input and approvals from all the stakeholders / 1 day / Wed 11/5/14 / Wed 11/5/14 / 5
Auto Scheduled / Discussion with project sponsor / 5 days / Thu 11/6/14 / Wed 11/12/14
Auto Scheduled / Meeting with Project sponsors / 1 day / Thu 11/6/14 / Thu 11/6/14 / 6
Auto Scheduled / Convey plan to all sponsors / 1 day / Fri 11/7/14 / Fri 11/7/14 / 8
Auto Scheduled / Take budgetary approvals / 1 day / Mon 11/10/14 / Mon 11/10/14 / 9
Auto Scheduled / Discuss future meeting plan / 1 day / Tue 11/11/14 / Tue 11/11/14 / 10
Auto Scheduled / Discuss the base line planning / 1 day / Wed 11/12/14 / Wed 11/12/14 / 11
Auto Scheduled / Architectural plan of Website / 4 days / Thu 11/13/14 / Tue 11/18/14
Auto Scheduled / Architectural Discussion / 4 days / Thu 11/13/14 / Tue 11/18/14
Auto Scheduled / Discuss Architectural plan with stakeholders / 4 days / Thu 11/13/14 / Tue 11/18/14 / 12
Auto Scheduled / Preliminary design / specification / 20 days / Wed 11/19/14 / Tue 12/16/14
Auto Scheduled / Specify the design of web pages / 5 days / Wed 11/19/14 / Tue 11/25/14 / 15
Auto Scheduled / Specify layout of web pages / 5 days / Wed 11/26/14 / Tue 12/2/14 / 17
Auto Scheduled / Specify design for forms on website / 10 days / Wed 12/3/14 / Tue 12/16/14 / 18
Auto Scheduled / Website Development / 30 days / Wed 12/17/14 / Tue 1/27/15
Auto Scheduled / Assessment phase / 15 days / Wed 12/17/14 / Tue 1/6/15
Auto Scheduled / Study industry wide standards / 2 days / Wed 12/17/14 / Thu 12/18/14 / 19
Auto Scheduled / Follow best practices / 3 days / Wed 12/17/14 / Fri 12/19/14 / 19
Auto Scheduled / Requirement gathering for Assessment / 5 days / Mon 12/22/14 / Fri 12/26/14 / 23
Auto Scheduled / Develop the Home Page / 5 days / Mon 12/29/14 / Fri 1/2/15 / 24
Auto Scheduled / Share design with stakeholders / 1 day / Mon 1/5/15 / Mon 1/5/15 / 25
Auto Scheduled / Take input from project sponsors / 1 day / Tue 1/6/15 / Tue 1/6/15 / 26
Auto Scheduled / Pilot phase / 5 days / Wed 1/7/15 / Tue 1/13/15
Auto Scheduled / Start the development of all web pages / 5 days / Wed 1/7/15 / Tue 1/13/15 / 27
Auto Scheduled / Periodic review and quality check / 2 days / Wed 1/7/15 / Thu 1/8/15 / 27
Auto Scheduled / Divide the development into different phases / 3 days / Wed 1/7/15 / Fri 1/9/15 / 27
Auto Scheduled / Support / 12 days / Mon 1/12/15 / Tue 1/27/15
Auto Scheduled / Support for modification / 4 days / Mon 1/12/15 / Thu 1/15/15 / 31
Auto Scheduled / Provision for 24X7 support / 2 days / Fri 1/16/15 / Mon 1/19/15 / 33
Auto Scheduled / Learning from industry / 4 days / Tue 1/20/15 / Fri 1/23/15 / 34
Auto Scheduled / Continuous Improvement / 2 days / Mon 1/26/15 / Tue 1/27/15 / 35
Auto Scheduled / Test Run Completion / 25 days / Wed 1/28/15 / Tue 3/3/15
Auto Scheduled / Test Strategy / 6 days / Wed 1/28/15 / Wed 2/4/15
Auto Scheduled / Define Test Strategy / 2 days / Wed 1/28/15 / Thu 1/29/15 / 36
Auto Scheduled / Take Signoff from sponsor for Test Strategy / 2 days / Fri 1/30/15 / Mon 2/2/15 / 39
Auto Scheduled / Discuss test strategyforum larger audience / 2 days / Tue 2/3/15 / Wed 2/4/15 / 40
Auto Scheduled / Unit Testing / 6 days / Thu 2/5/15 / Thu 2/12/15
Auto Scheduled / Unit Testing of Web pages / 2 days / Thu 2/5/15 / Fri 2/6/15 / 41
Auto Scheduled / Test the basic elements / 2 days / Mon 2/9/15 / Tue 2/10/15 / 43
Auto Scheduled / Test basic functionalities / 2 days / Wed 2/11/15 / Thu 2/12/15 / 44
Auto Scheduled / Integration testing / 5 days / Fri 2/13/15 / Thu 2/19/15
Auto Scheduled / Test workflows / 2 days / Fri 2/13/15 / Mon 2/16/15 / 45
Auto Scheduled / Test integrated system / 1 day / Tue 2/17/15 / Tue 2/17/15 / 47
Auto Scheduled / Test integration with other systems / 2 days / Wed 2/18/15 / Thu 2/19/15 / 48
Auto Scheduled / User Acceptance testing / 8 days / Fri 2/20/15 / Tue 3/3/15
Auto Scheduled / Include end use for testing / 3 days / Fri 2/20/15 / Tue 2/24/15 / 49
Auto Scheduled / Perform UAT testing in testing environment / 2 days / Wed 2/25/15 / Thu 2/26/15 / 51
Auto Scheduled / Extend the system from test environment to real environment / 3 days / Fri 2/27/15 / Tue 3/3/15 / 52
3.2 Task network
Project tasks and their dependencies are noted in this diagrammatic form.
3.3 Timeline chart
a project timeline chart (Gantt chart) is presented.
4.0 Staff Organization
Staff are organized according to an employee hierarchy starting at the top from a ACM ( Account manager ) and drilling down to all sort of departments main components of staff are segregated into mangers , team leaders and team members , all reporting to a department manager who is directly connected to the ACM
4.1 Team structure
Account manager: Is responsible for the entire account, he is the first point of contact when the project is initiated and last person to get the sign off from the customer.
Sales manager: Is directly responsible for the sales of any matter that the project may need
Sales Director: Is responsible for the sales negotiation and contracts handling
Marketing president: responsible for proper marketing of products and any new features that may arise in the project.
AccountmanagerAssistant: The person whom the account managerdelegates a few of his responsibilities
Development manager: is the key person in charge of the development process of the project
System analyst: Is the person responsible in analyzing the customer requirements and translating the data given by the customer, into use-case diagrams.
Web designer: Is responsible for the GUI interface design of the website, all the graphics and colorings are within his scope, translating the customer vision into an artistic reality.
Software quality engineer: is responsible for the project quality, making sure all references and documentation is adhered to, also code cleanliness is taken care of by him.
Test engineer: Is responsible for testing the entire phases of the project until reaching the project completion, reporting any bugs that may come up and reporting them to the developers.
4.2 Management reporting and communication
Management reporting will be through the company ERP program, referring to the hirarchery explained in the organizational and team structure, each member will be reporting to the team member above him, each team will have a weekly meeting, sending the meeting outcomes to the team leaders and thus to the department managers, the account manager will regularly check the meetings points to identify any potential project dead locks that may arise. A common escalation point will be in the hands of the HR, the HR will follow all the process needed to ensure total fairness to all team members with alignment to the company policy.
5.0 Risk management
5.1 Project Risks
Business Impact Risk: (BU).
This risk is in the form of not meeting the customer bossiness requirements by having software that does not satisfy his needs.