Kami Anak Malaysia

Bersama Berganding Bahu Kearah Membina Generasi Gemilang.

Merialisasikan Impian Untuk Semua

Bekerjasama Tanpa Diskriminasi

Adik-Adik kami Bimbing dan Sahabat Kami Pimpin

Mengamalkan Perkongsian dan Amalan Terbaik

10 Program Utama Untuk Semua

Program Yang Akan Mengubah Sikap dan Menambah Ilmu

Konsep Penglibatan Peserta dan Pembelajaran Aktif

Yang Berat Sama Di Pikul dan Ringin Sama Di Jinjing

Showing posts with label PM-Project Scope Statements. Show all posts
Showing posts with label PM-Project Scope Statements. Show all posts

Wednesday, August 4, 2010

Project Scope Statements

During this evening presentation (Wednesday: 9.00pm-11.20pm), there are many of you didn't mention about the project scope statements. Project scope statements are very important while building your WBS. Project scope statement is one of the key input in WBS together with 'Requirements Documentations' and 'Organizational Process Asset'.

A detailed project scope statements contains six elements:
1. product scope description (details all the features and function a product must have)
2. project deliverables (details all the work that needs to be done to complete the project)
3. product acceptance criteria (outline the requirement the project must meed before stakeholders accept the final product or service)
4. project constraints (specify the limitations and restrictions the project faces)
5. project assumption (factor that are considered to be true about a project)
6. project exclusions (clearly stipulate what is not included in the project)

Questions?
How do the elements of project scope statements contribute to creating the WBS?

Answers?
-project deliverables assist in identifying what tasks should be included in the WBS
-the product scope description assists in the process of breaking down deliverables in the WBS
-project exclusions help identifying what tasks are not appropriate to include in the WBS


Regards


MZA