Project management for Greendale Stadium Case


This assignment consists of two (2) parts: a project schedule, and a written response. You must submit both parts as separate files for the completion of this assignment. Label each file name according to the part of the assignment it is written for.

Part A: Project Schedule
(Submit as one [1] Microsoft Project file)
1.Create a multi-level work breakdown structure (WBS) and detailed project schedule, using the information from the “Greendale Stadium Case” located at the end of Chapter 6, and incorporating the following constraints.
Note: When you create your MS Project schedule, you will need to update your project per the following constraints: ?The project must consist of at least twenty (20) tasks.
?Each task must have a start and finish date that matches the duration noted in the assignment.
?Each task must be assigned to a resource (e.g., Demolishing Crew; Construction Crew; Landscaping Crew).
?Assume that the crew works during normal weekdays (no weekend work) under normal conditions (8 hours per day).
?In terms of holidays, you can assume no work will be done the following days: New Year’s Day, President’s Day, Good Friday, Good Monday, Friday before Memorial Day, Memorial Day, the business day before Independence Day, Independence Day, the Friday before Labor Day, Labor Day, the day before Thanksgiving Day, Thanksgiving Day, Black Friday (day after Thanksgiving), the business day before Christmas, Christmas Day, the business day after Christmas Day, and New Year’s Eve.

Part B: Written Response
(Submit as a Microsoft Word file)
1.Respond to the following questions in a one to two (1-2) page paper based on your project schedule. ?When will the project be completed?
?What is the critical path for the project?
?How much slack / float is in your project? What activities have the greatest slack / float?
?Identify the top three (3) activities that you believe could impact the project completion date.
?What additional activities you would add to this project to make it more complete, from a project management viewpoint?

Sample paper

Project management

Project management is one of the important professions in the globe today considering that it helps with the identification, management, and control of a project until the objectives and goals of the project are achieved. The critical path of a project comprises of the sequence of a project network activity that talks the longest overall duration irrespective or whether that duration has a float or not. The identification and establishment of a critical project path are essential to any project as it helps to identify the most substantial and necessary tasks in a project. In the project described above, it is easy to identify the critical path (Project Management Institute, 2017). Given the duration of activities in the project, the critical path of the project comprises of:

Designing 30 days + Web User Interface  17 days + Functional Specifications 10days + Conduct Design Preview  2 days + Obtain User Signoff  3 days + Technical Specification  15 days + SQL Database 25 days + Interface  10 days =112 days.

Through the identification of the critical path of the project, the project manager gets an opportunity to reduce the timelines to meet the specified and expected duration as well as reducing if not eliminating overall timeframe of the project.

On the other hand, the float or slack of a project is often comprised of the amount of time a particular task in the project can be delayed without causing a substantial effect on the overall timeframe of the project. Therefore, the slack or float time of a project can be calculated by getting the difference between the time it takes to complete a project and the projected project timeline. From the projected timeline, the project can be said to have an overall of 15 days float time (Baguley, 2008). However, the designing phase of the project has the slackest time to give a room for errors as well as the implementation of corrective action. Notably, if this phase is wrong or has errors that can significantly affect the project them the whole project can be wrong. Therefore, there is the need to leave room for errors and time to correct these errors. The designing phase of the project has a slack time of 4 days. Furthermore, another activity that has the slackest time SQL Database phase. Just like the designing phase, this is an important phase of the project, and the slightest error or mistake can put the entire project in jeopardy. Therefore, there is need to allow more time for the completion of the activity to ensure that the project meets the objectives and the required standards.

The designing phase of the project, Web User Interface and the creation of the SQL Database are the top three activities in this project.  Therefore, to protect the credibility and quality of the project, there is the need to ensure that these three activities are given the attention and time they require considering that they shoulder the weight of the entire project. Slightest error or delay can put the entire project in jeopardy.

To improve the quality and success of the project, there is the need to include the closing of the project in the project schedule. A project is often closed during the closing phase of the project management where construction workers put the finishing touches on their work, managers finalize their reports, and the new product is launched (Kerzner, 2017). Therefore, to make this project more complete, I would initiate product launching to celebrate the success.


Baguley, P. (2008). Project management. London: Hodder Education.

Kerzner, H. R. (2017). Project management. Place of publication not identified: John Wiley & Sons.

Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK guide).


Number Task name Duration Start date Finish date Resource
1 Designing 30 days 7/3/2016 5/4/2017 Designing team
2 Web User Interface 17 days 6/4/2017 22/4/2017 I.T team
3 Functional Specifications 10 days 24/4/2017 2/5/2017 Designing team
4 Create User Interface Mock ups 4 days 2/5/2017 6/5/2017 I.T team
5 Conduct Design Preview 2 days 7/5/2017 8/5/2017 Designing team
6 Obtain User Sign off 3 days 9/5/2017 11/5/2017 I.T team
7 Technical Specification 15 days 12/5/2017 26/5/2017 Designing team
8 Review Tech Specs with Project Team 3 days 27/5/2017 30/5/2017 I.T team
9 Obtain User Sign off 2 days 31/5/2017 1/6/2017 I.T team
10 SQL Database 25 days 2/6/2017 26/6/2017 Construction team
11 Develop Tech Specs 2 days 27/6/2017 28/6/2017 Designing team
12 Review Tech Specs with Project Team 2 days 29/6/2017 30/6/2017 Designing team
13 Obtain User Sign off 2 days 1/7/2016 2/7/2017 I.T team
14 Interface 10 days 3/7/2017 12/7/2017 I.T team
15 Define User needs 7day 13/7/2017 19/7/2017 Construction team
16 Define IT needs 4 days 20/7/2017 23/7/2017 Construction team
17 Define Interface 3 days 24/7/2017 26/7/2017 Construction team
18 Obtain User Sign off 2 days 24/7/2017 28/7/2017 I.T team
19 Reports 15 days 29/7/2017 13/8/2017 Project managers
20 Functional Specifications 12 days 14/8/2017 25/8/2017 Designing team