Project Scope

Project Scope

Melody Cobb

ITCO 311 IT Project and Team Management

January 20, 2013

Project Scope

PROJECT SCOPE: Build a house within 4 months on a specified budget of $200,000.

PROJECT TASKS:

1. 2000 Sq Ft house with 1 and a half baths, 3 bedrooms, living room, dining room, kitchen all on one story.

2. Attached garage with flooring.

3. Kitchen appliances, stainless steel. (Fridge, Stove, and dishwasher)

TIMELINE: Project starts April 1st.

1. Get construction permits by April 7th.

2. Foundation by April 14th.

3. House frame up by May 1st.

4. House interior, electrical wiring, plumbing, windows installed by June 15th.

5. Garage attached with first inspection by June 25th.

6. Fix all inspection problems by June 30th.

7. Final inspection July 1st.

I feel it is critical to understand the scope with objectives because you need to know what the project entails. If there were no scope or objectives, you would just build a house. By having specific tasks and guidelines lets you know what type of house the stakeholder wants and what they want in it.

The timeline is a guide to help you complete your project in a timely manner. If you do not have a proper timeline something can go wrong. For example, let’s say there was not a deadline for the 1st inspection and you had your final inspection the day you were to complete the project. The final inspection shows there are some problems with the wiring and you need another 5 days to fix the issues. You would then be over your deadline to have it completed. The project would fail.

I would sue the waterfall methodology for this project because it is the most used. The high level phases would contribute a lot to this project. They are requirement specifications, design, construction, integration, testing and debugging, installation and maintenance.

Quality should be managed to make sure the project specifications, standards, and requirements are being followed...