Running Head: WEBSITE DEVELOPMENT PROJECT MANAGEMENT
“Title”
0501426 Project Management
Dr Ahmad Ghandour
Summer Semester II, 2017
Group #
Student name: without ID
Student Name: without ID
.
.
.
TABLE OF CONTENTS
Overview of the Project...................................................................................................................2
Financial Section of Business Case for Project...............................................................................3
Project Charter.................................................................................................................................3
Problem/Opportunity...................................................................................................................3
Key Stakeholders.........................................................................................................................4
Project Milestones........................................................................................................................4
Project Budget..............................................................................................................................4
Constraints, Assumptions, Risks and Dependencies...................................................................4
Approval Signatures.....................................................................................................................5
Scope Statement for Project.............................................................................................................5
Work Breakdown Structure for Project (WBS)...............................................................................5
Activity List, Attributes, Network Diagrams, CPM & Gantt Charts...............................................7
Key Schedule Influencers..............................................................................................................10
Monitoring Progress......................................................................................................................12
Metrics, reports & graphs...........................................................................................................12
Determining Cause of Variation................................................................................................12
Responding to Deviations..........................................................................................................13
References......................................................................................................................................14
WEBSITE DEVELOPMENT PROJECT
MANAGEMENT
Overview of the Project
A website development project has been proposed by ABC organization. The fully
accessible website would be created to enhance the procurement management and the resources
of the vendors and suppliers of the company. The website will deal with the challenges which are
faced by the organization regarding procurement and the development of the fully accessible
website would also enhance the visibility of the company[ CITATION Bja08 \l 3081 ].
This project would result in a completely designed online presence of the company and
also the development of the supporting documentation. This would serve as the primary
communication tool and the information source where dealings and business with the suppliers
and vendors would be conducted[ CITATION Har04 \l 3081 ]. This is a 6 months project and the
budget allocated by the project sponsor for website development if $ 500,000. This report details
all the necessary components of project management and develops the detailed website
development project.
Financial Section of Business Case for Project
The financial analysis has been performed assuming that the project would be completed
within 6 months. However, this is just an assumption the actual project completion time has been
computed later through the use of critical path method. Based on the given benefits and operating
expenses and a discount rate of 6%, the financial returns of this project would be as follows:
PROJECT FINANCIAL ANALYSIS
Year 0 1 2 3
Initial Costs 500000
Annual Operating Costs 150000 150000 150000
Estimated Benefits 400000 400000 400000
Cash Flows 250000 250000 250000
Net FCF -500000 250000 250000 250000
Discount Rate 6.50%
NPV 162118.88
IRR 23%
Payback CF -250000 0 250000
Payback Period (years) 2
Project Charter
The purpose of the Project Charter is to define the scope, project organization, objectives
and the overall approach for the project. This is shown below:
Problem/Opportunity
We want to develop a website for our business / Organization in order to enhance Procurement
Management and Resources with suppliers and vendors.
Goals
Enhance the relationships with the suppliers and vendors.
Make the transaction processing more quick and user friendly.
Increase the revenues by approaching new suppliers and lowering acquisition costs.
Key Stakeholders
Client Suppliers and Vendors
Sponsor Dr. Ahmed Ghandour
Project manager Hasan Al Hosani
Project team Hamad, Rashed, Hussein and Nayef
members
Project Milestones
The project milestone would be achieved when the programming of the website would be
completed.
Project Budget
The total budget for this project is $ 500,000
Constraints, Assumptions, Risks and Dependencies
Constraints Cost is the main constraint here
Assumptions Consistent Inflation, high demand of organization’s products, superior
after sales service
Risks and Increases in website development costs, missing the deadline, increased
Dependencies costs due to delays.
Approval Signatures
Project Client Project Manager Project Sponsor
Scope Statement for Project
The website development project is a 6 months project which will develop the website for
the organization. This project is associated with addressing the challenges associated with
procuring from the suppliers and doing business with the vendors. The project would begin on
1ST January 2018 and end on 1 July 2018. An accessible website will be created by our team
which will enhance the visibility of the organization, expand our supplier base and the
WordPress platform would be used to design the website. The final deliverable of this project is
the fully accessible website built through WordPress and serves as the central location for all the
information for the suppliers and vendors.
Work Breakdown Structure for Project (WBS)
The work breakdown structure for the website development project is shown below:
WORK BREAKDOWN STRUCTURE (WBS)
Duration Dependenc Statu
WMS Activities
(Days) y s
1.1 Developing a Project Charter 2
1.2 Submitting Project Charter 1 1.1 Open
I. Initiation 1.3 Review of Project Charter by
2 1.2
Sponsor Open
1.4 Approval of Project Charter 1 1.3 Open
2.1 Creating scope statement for
1 -
Website Development Project (WDP) Open
2.2 Identify project team member for
3 -
WDP including newly hired Open
II. Planning 2.3 Kickoff meeting between project
1 2.2
team members Open
2.4 Development & Submission of
3 -
Project Plan Open
2.5 Apporval of project plan 1 2.4 Open
III. 3.1 Verification of customer
2 -
Execution requirements Open
3.2 Designing of website
3 3.1, I, II
methodology Open
3.3 Procurement of technological
2 3.1
tools & softwares/hardwares Open
3.4 Installation of development 4 3.3 Open
system and website designing
3.5 Training newly hired staff and
7 3.4
testing for a week Open
3.6 Finally implementing live system
3 3.5
in action Open
4.1 Meeting with project members for
3 -
keeping track of project Open
4.2 Managing change within the
7 4.2
department and organization Open
4.3 Risk management and making
2 4.2
emergency plans more strong Open
4.4 Implementing feedack system
fortaking timely feedback from 2 4.1,4.2,4.3
IV. Control Pediatrics department patients Open
4.5 Implementing system for taking
complaints from vendors about service 2 -
and staff quality Open
Operations Management/ Site
2 -
Maintenance Open
Web User Interface 2 - Open
4.6 Update/Change project plan as
3 -
and when required Open
5.1 Perform documentation for future
3 -
projects Open
5.2 Audit by external consultants 5 4 Open
5.3 Updating all records and files of
3 5.2
the department Open
5.4 End user documentation 2 5.3 Open
V. Closeout
5.5 Application Administration
2 5.4
Documentation Open
5.6 System Administrator
2 5.5
Documentation Open
5.7 Disaster Recovery 2 5.6 Open
5.8 Archiving all documentation 3 5.7 Open
The work breakdown structure tree has also been generated which is shown below:
WDP
Initiation Planning Execution Control Closeout
Develop PC Create SS Requiremen
t verification
Documentati
on LEGEND:
Identify
project team PRM Meeting Sytem &
Submit PC
Operational
= Level 1
methodology
Kickoff
meting Records
Review PC Procurement Change updating
Project plan Manageement
Approve PC
submission
Archiving = Level 2
files
Approval of Installation of Risk
PP tools management
= Level 3
Feedback
Traiining of system
staff
Complaint
Implementat system
ion
Updating
project plan
Activity List, Attributes, Network Diagrams, CPM & Gantt Charts
The activity list and the activity attributes with their duration in days and dependencies
have been generated in the excel spreadsheet to perform a CPM exercise. These are shown in the
table below:
ESTIMATION OF EFFORTS, DURATION & COSTS FOR WBSITE
DEVELOPMENT
Activity Predecesso Duration Normal
list Activity Attributes rs (days) Costs
Project Definition & Site
A Architecture - 10 4,000
B Information Design A 5 5,000
C GUI Design (Graphic) A 8 6000
D Programming A,B,C 1.5 10,000
E Usability Testing A 5 2,000
F Competitive Analysis D 3 1000
G Copywriting D,F 7 3000
H QA/Testing G 2 2500
The network diagram of all the above activities is shown in the diagram below:
We have also generated the results of the total project completion time in days and the
critical paths have also been identified for the project. The critical paths are activity A, B, C, D
and F, G.[ CITATION Ker13 \l 3081 ] The total time for the completion of the project is 16 days. The
results are shown in the table below:
Results
Late
Task Early Start Early Finish Start Late Finish Slack
A 0 10 0 10 0
B 10 11 10 11 0
C 10 11 10 11 0
D 11 12 11 12 0
E 10 12 14 16 4
F 12 13 12 13 0
G 13 16 13 16 0
H 0 2 14 16 14
Project Completion Time 16 days
Early start computations
A 0 0 0 0 0 0
B 10 0 0 0 0 0
C 10 0 0 0 0 0
D 10 11 11 0 0 0
E 10 0 0 0 0 0
F 0 0 0 12 0 0
G 0 0 0 12 0 13
H 0 0 0 0 0 0
Late finish computations
A B C D E F G H
A 16 16 16 16 16 16 16 16
B 10 16 16 16 16 16 16 16
C 10 16 16 16 16 16 16 16
D 11 11 11 16 16 16 16 16
E 14 16 16 16 16 16 16 16
F 16 16 16 12 16 16 16 16
G 16 16 16 13 16 13 16 16
H 16 16 16 16 16 16 16 16
10 11 11 12 16 13 16 16
Finally, the Gantt chart for the website development project has also been drawn with the help of
MS project as shown below:
WDP
Start Date: 1/01/2018
Tasks Start Date Days Completed Remaining
Task 1 01/01/18 10 112 102
Task 2 02/01/18 5 102 97
Task 3 03/03/18 8 97 89
Task 4 04/01/18 2 89 88
Task 5 05/01/18 5 88 83
Task 6 06/13/18 3 83 80
Task 7 06/14/18 7 5 2
Task 8 06/15/18 2 2 0
Dec-12 Apr-14
GANTT CHART
Sep-15 Jan-17 May-18 Oct-19 Feb-21
Task 1
Task 2
Task 3
Task 4
Task 5
Task 6
Task 7
Task 8
Start Date
Completed
Key Schedule Influencers
There are a number of key schedule influencers which can impact on the projects negatively
or positively. One of the research shows that 75% to 90% of the project fail because of their
failure to meet their project objectives. This same research also identified that there mainly the
human behaviors are the one which are responsible for the failure of the projects as the
negatively impact on the schedule of these projects[ CITATION Ker13 \l 3081 ]. The main key
schedule influencers who can impact upon small or large projects are as follows:
Failure to align the project priorities is one of the key influencer due to which projects
fail. When the project managers fail to derail the program priorities, then the schedule for
the projects deviates.
If any project has unequipped or unmotivated team members then that project is likely to
fail. According to research 80% of the projects fail because the members of the team are
not able to track and support the schedule of the project optimally.
Fact free planning is also a key schedule influencer. 85% of the projects fail because of
setting the resource limits and the deadlines without considering the external realities or
taking input from experienced consultants.
Finally, the failure to build the most effective direction setting alliances is another key
schedule influencer. 65% of the projects fail because of negative impact on their
schedules due to lack of sponsorship which proves to be insufficient to achieve the
intended purpose of the project.
Handling the above key schedule influencers is highly important for achieving the purpose
and successful completion of the projects. One of the most important solution for managing and
handling such key schedule influencers is to form a ‘Net Map’ which will identify the influence
networks and depict the complete project information in a quantitative and intuitive
manner[ CITATION Mil05 \l 3081 ]. All the participants of the project can easily visualize their own
networks within the group network. Apart from this, influence maps can also be used to identify
the stakeholders who can influence the project schedule and then it could be used as a guide to
manage the various relationships among them.
Monitoring Progress
The monitoring and the control activities for the project take place at the same time and these
consist of all those activities which are performed for observing the execution of the project and
potential problems could be identified in advance and immediate corrective action could be
taken. We will be monitoring the project by identifying the critical path activities. Along with
this a milestone slip chart can also be produced or a Gantt chart could be generated to monitor
the progress of the project.
Metrics, reports & graphs
A range of different metrics, reports and graphs will be used to monitor the progress of the
project. For the graphs we will use the milestone slip chart, Gantt chart and the precedence chart
to monitor the progress of the activities. The project budget monitoring can be performed by
filming the S curve[ CITATION Woo12 \l 3081 ]. Apart from this, many other metrics could be used
to monitor the progress of the project such as Pareto analysis and Earned Value Analysis.
Determining Cause of Variation
The milestone slip chart and the Gantt chart would work in similar fashion and both can be
created using MS Project. These charts will highlight the key milestones with their respective
dates and then comparison could b easily made with the actual progress of the project. The
precedence chart can be used to guide the project execution and help us to monitor why
particular activity is dependent on another activity. The Pareto Analysis can help us to determine
the 20% of the activities which are responsible for 80% of the costs of the project. After these are
identified we can adjust our monitoring and focus on these activities. Finally, the EVA can be
used to find out that whether the project is getting value for money or not.
Responding to Deviations
When particular deviations are identified in the project by using the above monitoring tools
and techniques then immediate corrective actions will be taken. If the project is running over the
budget then the contingency budget would be utilized however, before that the causes for the
deviation will be identified and removed. If the project is running before the schedule and not
making significant progress then management can decrease the time for non-critical activities
and utilize that time for the completion of the critical activities of the project. Overall, when the
project would deviate from the baseline then updated risk identification and risk analysis will be
performed. The contingency plan would be applied in such situations. If the deviation is still not
handled then a request for the change of the project plan would be submitted.
References
Bjarne. (2008). Project Management –. Theory and practice. Nyt Teknisk Forlag , 59.
Harrison. (2004). Advanced project management: a structured approach. Gower Publishing, Ltd .
Kerzner. (2013). Project Management: A Systems Approach to Planning, Scheduling, and
Controlling (8th ed.). Project Management Institute .
Milosevic. (2005). Project Management ToolBox: Tools and Techniques for the Practicing
Project Manager. Wiley .
Woolf. (2012). CPM Mechanics: The Critical Path Method of Modeling Project Execution
Strategy . ICS-Publications .