Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Project Scope Documentation

3 replies [Last post]
Mahendra Gupta
User offline. Last seen 4 weeks 4 hours ago. Offline
Joined: 25 Feb 2020
Posts: 13
Groups: None

Even though defining all the project attributes right from the start is essential, project managers sometimes fail to compile them all effectively, thereby leading to roadblocks later on. So, what should be the approach to create a comprehensive project scope document that can help avoid discrepancies?

Replies

Patrick Weaver
User offline. Last seen 5 days 4 hours ago. Offline
Joined: 18 Jan 2001
Posts: 303
Groups: None

The client's role should be to define the scope of the project - the project is intended to deliver a solution to a requirement the client has. However, clients are rarely capable of fully defining their needs and require assistance from the SMEs in the delivery team.

Requirements gathering is basically a structured investigation: https://mosaicprojects.com.au/PMKI-PBK-015.php#Process1

The way this is done depends on the project’s relationship to the client and the way the project is being managed. Agile projects evolve, other ‘hard’ projects need the scope defined up front. But this can be difficult, on mega-projects it is not uncommon to see up to 20% of the scope missed from the initial contract documents. There’s a series of reports on this, see the ‘Scope for Improvement’ series at: https://mosaicprojects.com.au/PMKI-ITC-010.php#Overview

Peter Holroyd
User offline. Last seen 1 week 23 hours ago. Offline
Joined: 6 Jun 2005
Posts: 126

This is the area of Requirements Engineering. ALL the contract documents are deconstructed into a deliverables list which are tracked throughout the project. When you've handed over all requirements job finished

Peter

Zoltan Palffy
User offline. Last seen 2 days 22 hours ago. Offline
Joined: 13 Jul 2009
Posts: 3052
Groups: None

you should re-take off the documents and do ANOTHER estimate to make sure that you did not miss anything because a lot of the times the person taking of the inital bid estimate are not the same people excuting the work.