My Wiki!

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
cloudsa:projectmanagement:requirementanalysis:requirementscope [2025/03/15 15:46] – created tdcloudsa:projectmanagement:requirementanalysis:requirementscope [2025/03/17 09:39] (current) – old revision restored (2025/03/15 17:29) td
Line 7: Line 7:
 sometimes the collect requirements process is followed by develop scope and the requirements sometimes the collect requirements process is followed by develop scope and the requirements
 documents is assumed to be the scope statement. However, for a large project, it is different. First, you documents is assumed to be the scope statement. However, for a large project, it is different. First, you
-collect the project requirements and then develop the scope statement. Here, although the scope statement is based on the requirements documents, it is different. To achieve your project’s success you have+collect the project requirements and then develop the scope statement. Here, although the scope statement  
 +is based on the requirements documents, it is different. To achieve your project’s success you have
 to collect requirements from all stakeholders and develop the scope based on them. to collect requirements from all stakeholders and develop the scope based on them.
 You record the project requirements in the requirements documents and the project scope in the scope You record the project requirements in the requirements documents and the project scope in the scope
Line 13: Line 14:
 statement is an output of define scope process. statement is an output of define scope process.
  
-Project Requirements+===== Project Requirements =====
  
 To collect project requirements, you meet with all project stakeholders and discover their needs, To collect project requirements, you meet with all project stakeholders and discover their needs,
Line 22: Line 23:
 tie in with the scope statement. These requirements are the basis for the scope statement and work tie in with the scope statement. These requirements are the basis for the scope statement and work
 breakdown structure. breakdown structure.
-How to collect Project Requirements+ 
 +==== How to collect Project Requirements ==== 
 Collecting project requirements is a lengthy process and involves many activities. You will meet with Collecting project requirements is a lengthy process and involves many activities. You will meet with
 important stakeholders and ask for their requirements. You may also call for a group discussion or hold important stakeholders and ask for their requirements. You may also call for a group discussion or hold
Line 29: Line 32:
 team members. If any clarification or further information is required, you will have another meeting or team members. If any clarification or further information is required, you will have another meeting or
 session. session.
 +
 What do these Requirements include? What do these Requirements include?
 +
 The requirements may include the following: The requirements may include the following:
 +
 1. Business Requirements 1. Business Requirements
 +
 2. Product Requirement 2. Product Requirement
 +
 3. Project Requirements 3. Project Requirements
 +
 4. Quality Requirements 4. Quality Requirements
 +
 The business requirements are high-level requirements and describe what benefits the project will bring The business requirements are high-level requirements and describe what benefits the project will bring
 to the organization or the reasons for the project’s initiation. The product requirements can include what to the organization or the reasons for the project’s initiation. The product requirements can include what
Line 40: Line 50:
 expectations of your project, such as how they wish to be communicated the status or progress reports. expectations of your project, such as how they wish to be communicated the status or progress reports.
 The quality requirements include the inclusion of tests, quality checks, physical inspections, etc. The quality requirements include the inclusion of tests, quality checks, physical inspections, etc.
-Project Scope Statement+ 
 +==== Project Scope Statement ==== 
 The project scope statement has a detailed description on how you are going to complete the project, and The project scope statement has a detailed description on how you are going to complete the project, and
 the features of the product. To build your scope statement, you use the requirements documents and the features of the product. To build your scope statement, you use the requirements documents and
Line 47: Line 59:
 included in the scope statement. included in the scope statement.
  
-===== How the Project Scope Statement is defined =====+=== How the Project Scope Statement is defined ===
  
 The method of defining the scope statement is somewhat similar to collecting the requirements. You meet The method of defining the scope statement is somewhat similar to collecting the requirements. You meet
Line 55: Line 67:
 deliverables. This is an important step and the description of the product should be with as much details deliverables. This is an important step and the description of the product should be with as much details
 as possible. as possible.
 +
 What does the Scope Statement include? What does the Scope Statement include?
 +
 The scope statement may include the following: The scope statement may include the following:
 +
 ▪ Project Scope ▪ Project Scope
 +
 ▪ Product Description ▪ Product Description
 +
 ▪ Project Deliverables ▪ Project Deliverables
 +
 ▪ Project Exclusion ▪ Project Exclusion
 +
 ▪ Acceptance Criteria ▪ Acceptance Criteria
-Project Scope+ 
 +== Project Scope == 
 + 
 The project scope includes all work that you will carry out to complete the project and deliver the project’s The project scope includes all work that you will carry out to complete the project and deliver the project’s
 output to the client. It includes developing the plan, executing the work, monitoring and controlling, and output to the client. It includes developing the plan, executing the work, monitoring and controlling, and
 closing the project. closing the project.
-Product Description+ 
 +== Product Description == 
 + 
 Here you will describe the product in detail, its characteristics, how it will behave and its functional Here you will describe the product in detail, its characteristics, how it will behave and its functional
 requirements. requirements.
-Project Exclusion+ 
 +== Project Exclusion == 
 + 
 Sometimes it becomes necessary to include what is not included in the project scope to bring clarity and Sometimes it becomes necessary to include what is not included in the project scope to bring clarity and
 clear any doubts. So, you will mention all project exclusions here. clear any doubts. So, you will mention all project exclusions here.
-Acceptance Criteria+ 
 +== Acceptance Criteria == 
 + 
 This is the most important part of scope statement. This is where you will mention what conditions the This is the most important part of scope statement. This is where you will mention what conditions the
 deliverable should meet so that the client will accept it. deliverable should meet so that the client will accept it.
Line 78: Line 109:
 The project requirements and scope statement are not competing for the same space. Without the project The project requirements and scope statement are not competing for the same space. Without the project
 requirements, you cannot develop the scope statement. requirements, you cannot develop the scope statement.
 +
 The main differences between them are as follows: The main differences between them are as follows:
 +
 ▪ The requirements show the stakeholders’ requirements and expectations while the scope statement ▪ The requirements show the stakeholders’ requirements and expectations while the scope statement
 defines the project boundaries, what is included and what is not. defines the project boundaries, what is included and what is not.
 +
 ▪ Requirements are collected directly from stakeholders while the scope statement is derived from the ▪ Requirements are collected directly from stakeholders while the scope statement is derived from the
 project requirements documents. project requirements documents.
 +
 ▪ The client or external stakeholders usually describe requirements, and the project manager and team ▪ The client or external stakeholders usually describe requirements, and the project manager and team
 members usually determine the project scope. members usually determine the project scope.
 +
 ▪ The requirements documents are an output of the collect requirements process and the scope ▪ The requirements documents are an output of the collect requirements process and the scope
 statement is an output of the define scope process. statement is an output of the define scope process.
-Summary+ 
 +==== Summary ==== 
 + 
 Collecting requirements and defining scope are the basis of your planning process and your project’s Collecting requirements and defining scope are the basis of your planning process and your project’s
 success depends on them. The requirements documents show the needs and expectations of your success depends on them. The requirements documents show the needs and expectations of your
 project’s stakeholders and its deliverables. On the other hand, the scope statement shows what works project’s stakeholders and its deliverables. On the other hand, the scope statement shows what works
 needs to be done to complete the work and the features and behavior of the product. needs to be done to complete the work and the features and behavior of the product.

Trace: • start_developing_odl_openstack

Navigation