OBS 220
Chapter 7: scope planning
Plan scope management
• Project team members develop scope management plan, assess project
requirements, develop the projects scope and create a work breakdown structure
(WBS)
• When planning scope it is wise to plan for changes
• Plan scope management = the process of developing a plan that includes the total
scope of what needs to be done and what is excluded from the project;
implementation and validation of the scope and how to control deviations from the
scope statement
• Product scope = outputs the team will deliver to its customers
• Project scope =
the work needed
to be performed
in order to deliver
the projects
outputs
• The total scope
then consists of
the product scope
and project scope
Collect requirements
• A requirement condition or capability needed by a user to solve a problem or
achieve an objective that satisfies a standard, a specification or nay other formally
documented need
• Collect requirements is a systematic effort to understand and analyze stakeholder
needs to define and document these needs and requirements with a focus on
meeting project objectives
• First step in collecting requirements is to make sure project team is clear on project
objectives
• Collecting requirements same regardless of project type. Generally agile
documentation is less formal, thus allowing for progressive elaboration
Gather stakeholder input and needs
• Second step to gather input from various project stakeholders
• Project manager assigned and more detailed requirements assessment is done after
a project core team is selected
• Core team size depend on nature of project and number of disciplines required to
plan and execute the project
Created by: Sabrina Dias
, • Successful project managers know that for a project outcome to be useful to project
customers, the customers need to be able to use the output better serve their own
customers in turn
• Use the voice of customer techniques (VOC)
- Ask questions
- Place yourself in customers situation
• State customer desires in operational terms
• Traditional methods of obtaining and documenting requirements
- Meetings with stakeholders
- Interviews
- Focus groups
- Questionnaires
- Surveys
- Observations
- Prototype
- Industry standards
- Reference documents
- Market analysis
- Competitive analysis
- Client requests
- Standards specifications
• Seek a high level description of their reasons for the requested feature and then
guide the discussion with the following:
- what do we not understand about feature
- What is the business reason for the feature
- what is the impact of not providing this feature
- what action items need to be accomplished if we do this
- what impact will this have on other features of the project or elsewhere
• The requirements type suggests whether the requirement is functional,
nonfunctional or needed by a particular stakeholder
• Traceability matrix also includes the status of the requirement, its priority and who is
responsible for the requirement
• When requirements are complete each requirement needs to be:
- Traceable back to business
- Identified with stakeholders who need it
- Unambiguous
- Qualified by
measurable
conditions
- Validated for its
value and
completion
- Bounded by
constraints
- Prioritized
according to
Created by: Sabrina Dias
Chapter 7: scope planning
Plan scope management
• Project team members develop scope management plan, assess project
requirements, develop the projects scope and create a work breakdown structure
(WBS)
• When planning scope it is wise to plan for changes
• Plan scope management = the process of developing a plan that includes the total
scope of what needs to be done and what is excluded from the project;
implementation and validation of the scope and how to control deviations from the
scope statement
• Product scope = outputs the team will deliver to its customers
• Project scope =
the work needed
to be performed
in order to deliver
the projects
outputs
• The total scope
then consists of
the product scope
and project scope
Collect requirements
• A requirement condition or capability needed by a user to solve a problem or
achieve an objective that satisfies a standard, a specification or nay other formally
documented need
• Collect requirements is a systematic effort to understand and analyze stakeholder
needs to define and document these needs and requirements with a focus on
meeting project objectives
• First step in collecting requirements is to make sure project team is clear on project
objectives
• Collecting requirements same regardless of project type. Generally agile
documentation is less formal, thus allowing for progressive elaboration
Gather stakeholder input and needs
• Second step to gather input from various project stakeholders
• Project manager assigned and more detailed requirements assessment is done after
a project core team is selected
• Core team size depend on nature of project and number of disciplines required to
plan and execute the project
Created by: Sabrina Dias
, • Successful project managers know that for a project outcome to be useful to project
customers, the customers need to be able to use the output better serve their own
customers in turn
• Use the voice of customer techniques (VOC)
- Ask questions
- Place yourself in customers situation
• State customer desires in operational terms
• Traditional methods of obtaining and documenting requirements
- Meetings with stakeholders
- Interviews
- Focus groups
- Questionnaires
- Surveys
- Observations
- Prototype
- Industry standards
- Reference documents
- Market analysis
- Competitive analysis
- Client requests
- Standards specifications
• Seek a high level description of their reasons for the requested feature and then
guide the discussion with the following:
- what do we not understand about feature
- What is the business reason for the feature
- what is the impact of not providing this feature
- what action items need to be accomplished if we do this
- what impact will this have on other features of the project or elsewhere
• The requirements type suggests whether the requirement is functional,
nonfunctional or needed by a particular stakeholder
• Traceability matrix also includes the status of the requirement, its priority and who is
responsible for the requirement
• When requirements are complete each requirement needs to be:
- Traceable back to business
- Identified with stakeholders who need it
- Unambiguous
- Qualified by
measurable
conditions
- Validated for its
value and
completion
- Bounded by
constraints
- Prioritized
according to
Created by: Sabrina Dias
