Project Scope Managementإدارة نطاق المشروع
مقدمة الفصل
ماذا ستتعلم في هذا الفصل
- What is project scope management.
- Project scope management processes.
- Explain the scope definition process and describe the contents of a project scope statement.
- Discuss the process for creating a work breakdown structure using different methods.
- Importance of verifying and controlling scope.
أقسام الفصل
- 1Scope and scope management processesالنطاق وعمليات إدارته
- 2Planning scope management and collecting requirementsتخطيط إدارة النطاق وجمع المتطلبات
- 3Defining scopeتحديد النطاق
- 4Creating the work breakdown structureإنشاء هيكل تجزئة العمل
- 5Validating and controlling scopeالتحقق من النطاق والتحكم فيه
تلميح: استخدم أسهم لوحة المفاتيح للتنقل بين الشرائح.
What is project scope management?ما إدارة النطاق؟
Scope and scope management processes
| Initiating | Planning | Executing | Monitoring & Control | Closing |
|---|---|---|---|---|
| — | Plan scope management, collect requirements, define scope, create WBS | لا تذكر الشرائح شيئًا هنا. | Validate scope, control scope | لا تذكر الشرائح شيئًا هنا. |
Refers to all the work involved in creating the products of the project and the processes used to create them.
Includes the processes involved in defining and controlling what is and is not included in a project.
Scope management processesعمليات إدارة النطاق
| Processالعملية | What it involvesماذا تتضمن | Outputsالمخرجات |
|---|---|---|
| Planning scope management | Determining how the project's scope and requirements will be managed. |
|
| Collecting requirements | Defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them. |
|
| Defining scope | Reviewing the project charter, requirements documents, and organizational process assets to create a scope statement. |
|
| Creating WBS | Subdividing the major project deliverables into smaller, more manageable components. |
|
| Validating scope | Formalizing acceptance of the project deliverables. |
|
| Controlling scope | Controlling changes to project scope throughout the life of the project. |
|
The first four are in the planning process group; validating and controlling scope are in monitoring and controlling.
سؤال سريع
Scope and scope management processes
1. Planning scope managementتخطيط إدارة النطاق
Planning scope management and collecting requirements
The scope management plan is a subsidiary part of the project management plan.
Scope management plan contents:
- How to prepare a detailed project scope statement.
- How to create a WBS.
- How to maintain and approve the WBS.
- How to obtain formal acceptance of the completed project deliverables.
- How to control requests for changes to the project scope.
المخرجات
- Scope management plan
- Requirements management plan
2. Collecting requirementsجمع المتطلبات
Planning scope management and collecting requirements
Slide 14 (a cartoon of a tree swing)
- Ten panels show how one requirement drifts: how the customer explained it, how the project leader understood it, how the engineer designed it, how the programmer wrote it, how the sales executive described it, how the project was documented, what operations installed, how the customer was billed, how the helpdesk supported it — and what the customer really needed (a simple tyre swing).
فئات المتطلبات
- Hardware requirements
- Software requirements
- Functional requirements
- Service requirements
- Performance requirements
- Quality requirements
- Training requirements
| Techniqueالأسلوب | Note from the slideملاحظة من الشريحة |
|---|---|
| Interviewing stakeholders one on one | Often very effective, although it can be expensive and time-consuming. |
| Focus group | Normally faster and less expensive than one-on-one interviews. |
| Questionnaires | Can be efficient ways to collect requirements as long as key stakeholders provide honest and thorough information. |
| Observation | Can also be a good technique for collecting requirements, especially for projects that involve improving work processes and procedures. |
| Prototyping | For software development projects, which help to clarify the interfaces and boundaries of a project or process. |
| Benchmarking | Comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization. |
Requirements traceability matrixمصفوفة تتبع المتطلبات
Planning scope management and collecting requirements
A table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed. Project teams often create it in addition to the requirements documentation.
| Requirement No. | Name | Category | Source | Status |
|---|---|---|---|---|
| R32 | Laptop memory | Hardware | Project charter and corporate laptop specifications | Complete. Laptops ordered meet requirement by having 4GB of memory. |
To maintain the linkage from the source of each requirement through its decomposition to implementation and validation.
مخرجات جمع المتطلبات
- Requirements documentation
- Requirements traceability matrix
سؤال سريع
Planning scope management and collecting requirements
3. Defining scopeتحديد النطاق
Provides a detailed definition of the work required for the project.
Sample of project charter (partial) — slide 21
- The slide reuses the IT Upgrade Project charter of Lecture 3 (title, start March 4, finish December 4, key schedule milestones, budget $1,000,000 for hardware and software and $500,000 for labor, objectives, success criteria and approach) as an input to defining scope.
Key inputs for preparing the project scope statement:
- The project charter.
- Requirements documentation.
- Organizational process assets, such as policies and procedures related to scope statements.
Project scope statements should include:
- At least, a product scope description, product user acceptance criteria, and detailed information on all project deliverables.
- Project boundaries, constraints, and assumptions.
- Reference supporting documents, such as product specifications that will affect what products are created or purchased, or corporate policies, which might affect how products or services are produced.
As time progresses, the scope of a project should become more clear and specific.
المخرجات
- Project scope statement
- Project requirements updates
4. The work breakdown structureهيكل تجزئة العمل
Creating the work breakdown structure
A deliverable-oriented grouping of the work involved in a project that defines the total scope of the project. A foundation document that provides the basis for planning and managing project schedules, costs, resources, and changes.
Main inputs:
- The project scope management plan.
- Scope statement.
- Requirements documentation.
- Organizational process assets.
Subdividing project deliverables into smaller pieces.
Work packagesحزم العمل
Creating the work breakdown structure
- A work package (WP) is a task at the lowest hierarchical level in each branch of the WBS.
- It also represents the level of work that the project manager monitors and controls.
- Work packages cannot be sub-divided any further; tasks that are sub-divided are called sub-tasks (ST).
1 Project
1.1 Phase A
1.1.1 WP1.1.2 WP
1.2 Phase B
1.2.1 WP1.2.2 WP
1.2.3 ST
1.2.3.1 WP1.2.3.2 WP
1.3 Phase C
1.3.1 WP
1.4 Phase D
1.4.1 WP
1.4.2 ST
1.4.2.1 WP1.4.2.2 WP
Sample WBS: an intranet projectمثال: هيكل مشروع إنترانت
Creating the work breakdown structure
Intranet
Web site design
Site mapGraphic designPrograms
Home page design
TextImagesHyperlinks
Marketing pages
TextImagesHyperlinks
Sales pages
TextImagesHyperlinks
Determine the work package! In this WBS the items at the lowest level of each branch (site map, graphic design, programs; text, images, hyperlinks) are the work packages.
Tabular form with PMI numbering (slide 32, partial):
- 1.1 Concept
- 1.1.1 Evaluate current systems
- 1.1.2 Define requirements (1.1.2.1 Define user requirements; 1.1.2.2 Define content requirements; 1.1.2.3 Define system requirements; 1.1.2.4 Define server owner requirements)
- 1.1.3 Define specific functionality
- 1.1.4 Define risks and risk management approach
- 1.1.5 Develop project plan
- 1.1.6 Brief web development team
- 1.2 Website design
- 1.3 Website development
- 1.4 Roll out
- 1.5 Support
The WBS is the basis for project schedules (slide 33: the WBS tasks become the rows of the Gantt chart).
Approaches to developing WBSsطرق إنشاء الهيكل
Creating the work breakdown structure
تذكّر كل منهج قبل أن تكشفه.
- 1Using guidelines
Many organizations provide guidelines and templates for developing WBSs, as well as examples of WBSs from past projects.
- 2The analogy approach
Review WBSs of similar projects and tailor to your project.
- 3The top-down approach
Start with the largest items of the project and break them down.
- 4The bottom-up approach
Start with the specific tasks and roll them up.
- 5Mind-mapping approach
A technique that uses branches radiating out from a core idea to structure thoughts and ideas.
WBS dictionary and scope baselineقاموس الهيكل وخط أساس النطاق
Creating the work breakdown structure
A document that provides detailed information about each WBS item — a definition of the work involved in the task, a clarification that makes the summary description in the WBS easier to understand in terms of the approach taken to complete the work.
Slide 38 shows a sample entry: project title, WBS item number (2.2) and name (Update Database), and a description of the work, who is involved, and its dependencies (it depends on item 2.1 and must precede item 3.0).
مخرجات إنشاء الهيكل
- Scope baseline
- Project requirements updates
سؤال سريع
Creating the work breakdown structure
5. Validating scopeالتحقق من النطاق
Validating and controlling scope
The tendency for project scope to keep getting bigger and bigger — many IT projects suffer from it.
- To minimize scope changes, it is crucial to validate project scope.
- Scope validation involves formal acceptance of the completed project deliverables.
- Acceptance is often achieved by a customer inspection and then sign-off on key deliverables.
المخرجات
- Accepted deliverables
- Change requests
- Work performance information
- Project documents update
6. Controlling scopeالتحكم في النطاق
Validating and controlling scope
Scope control involves controlling changes to the project scope.
Control scope — outputs (slide 44)
- Work performance information
- Change requests
- Project management plan update
- Project documents update
- Organizational process assets update
Goals of scope control:
- Influence the factors that cause scope changes.
- Assure changes are processed according to procedures developed as part of integrated change control.
- Manage changes when they occur.
An important tool to perform scope control. Variance is the difference between planned and actual performance.
المخرجات
- Work performance information
- Change requests
- Project management plan update
- Project documents update
- Organizational process assets update
سؤال سريع
Validating and controlling scope
الخلاصة
أنهيت الدرس
الخطوة التالية: ثبّت المعلومات بالبطاقات، ثم اختبر نفسك بالأسئلة.