Project Time and Cost Management: Running Case

Recreation & Wellness Project: Part 1

2

Recreation & Wellness Project

Project 1: The three new activities include;

i. High-Level and Low-level Design. Breaking the system into two viewpoints is part of this effort. The foremost entity, often known as a high-level design, which depicts the system's primary components. The second step is to break down high-level design into micro workflows, also called low-level design.

ii. Interface design. This activity entails creating the project's user interface. It will determine which information will be shared from the end user as well as how it will be communicated.

iii. Installation of software and hardware. After the system has been setup, software and hardware must be installed in order for it to function effectively.

Project 2: The 9 milestones proposed include:

i. Complete requirements. This milestone ensures that the planned recreation project's needs have tested solutions for each one. The project's needs will be frozen after the established requirements have been signed off by top level management. It will need a project manager as well as an analyst to complete it. Whenever requirements are finished yet change often, there will still be a lot of modification, resulting in a waste of resources and cash. Even the deadline might be overlooked. It takes 1 to 1.5 weeks to complete.

ii. Complete user interface design. This phase represents the completion of the user interface design, and how the interface will seem to the user. It can only be accomplished once high-level management has approved the design interface. To do this, the project requires analysts and programmers, which includes two programmers, Dylan and me. There cannot be any more GUI creation if indeed the user interface is not finished. It will result in missed deadlines. It will take 1 to 1.5 weeks to complete.

iii. Complete the design. This milestone is in charge of defining the low-level and high-level design. It is a critical task since coding cannot take place till it is completed. It will be accomplished after the user interface is completed. Dylan and I are the two analysts working on the project. This will take 3 to 4 weeks to complete.

iv. Develop the graphical user interface. The sign-offs and development of GUI are depicted in this milestone. It is a key stage because the project will not be able to move on with the initial phase without it. After the design has been decided, GUI development may begin. Dylan and I are the two programmers who will complete this project. It will take about 4 to 5 weeks to complete.

v. Alpha version release. This milestone denotes the completion of the project's alpha phase, without which the beta version cannot be completed. Dylan and I are accessible as required resources. It will take 3 to 4 weeks to complete.

vi. Beta version release - This milestone denotes the start of the project's beta phase, which is required for quality testing. The necessary resources, such as myself, are accessible. This will require approximately one week.

vii. Q/An acceptance. This milestone shows that the project was completed according to the project management quality requirements. Dylan and I are accessible as required resources. This will take approximately one to one and a half weeks.

viii. Go-Live - The delivery of the project to the client is shown by this milestone. Peter, Dylan, and all the other resources Sue and I are both available. It will require approximately 17 days to complete.

Project 3: Gantt chart

Project 4: The most critical component in resource allocation is to keep the resources level. There must be no overabundance of work on any one resource. For this case, we have two programmers/analysts conducting the majority of the project's technical work in the provided situation. It is possible that they will be overburdened as a result. However, we have distributed resources in a different way such that they stay balanced.

Task Name	Resource Name	Days	Hours per Day	Total Hours	Cost Per Task ($)
Requirement Analysis	Nancy	4	9	36	1500
Sign offs	Peter	3	9	27	2300
Design Interface	Dylan	5	9	45	3000
Sign offs	Peter	3	9	27	2500
High level design	Dylan	5	9	45	3000
Low level design	Me	14	9	126	12000
Sign offs	Peter	3	9	27	2500
Develop GUI	Dylan	21	9	169	15000
Evaluate user interface	Me	7	9	63	4500
Unit Testing	Dylan	7	9	63	4000
System Testing	Me	7	9	63	5000
Application Testing	Dylan	7	9	63	4500
Fix bugs of alpha phase	Me	5	9	45	4000
Fix bugs of beta phase	Dylan	5	9	45	3000
Quality checks	Me	5	9	45	3200
Fix quality issues	Dylan	4	9	36	2500
Installation of server and software	Me	17	3	51	3000
	Peter	17	2	34	1500
	Dylan	17	1	17	2700
	Sue	17	2	34	2300
Total				1061	82000