100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
Summary OBS 220 Project management chp 7 R50,00   Add to cart

Summary

Summary OBS 220 Project management chp 7

 35 views  0 purchase

OBS 220 project management chp 7. detailed notes to help better apply the knowledge on application question. notes are made from both slides and textbook

Preview 2 out of 7  pages

  • No
  • Chp 7
  • October 13, 2020
  • 7
  • 2020/2021
  • Summary
book image

Book Title:

Author(s):

  • Edition:
  • ISBN:
  • Edition:
All documents for this subject (10)
avatar-seller
029sabrinadias
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

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

Guaranteed quality through customer reviews

Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.

Quick and easy check-out

Quick and easy check-out

You can quickly pay through EFT, credit card or Stuvia-credit for the summaries. There is no membership needed.

Focus on what matters

Focus on what matters

Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!

Frequently asked questions

What do I get when I buy this document?

You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.

Satisfaction guarantee: how does it work?

Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.

Who am I buying this summary from?

Stuvia is a marketplace, so you are not buying this document from us, but from seller 029sabrinadias. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy this summary for R50,00. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

75323 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy summaries for 14 years now

Start selling
R50,00
  • (0)
  Buy now