100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
Summary OBS220 Notes Covering Ch 7,8,11,14 PM (2022 Semester Test 2) $4.54   Add to cart

Summary

Summary OBS220 Notes Covering Ch 7,8,11,14 PM (2022 Semester Test 2)

 15 views  0 purchase
  • Course
  • Institution
  • Book

Theses are detailed notes covering chapters 7,8,11, and 14 from the Project Management textbook. These notes have been compiled in conjunction with the textbook and lecture slides. These notes have also been made for semester test 2 of 2022. Textbook used: Project management: Kloppenborg, T.J.,...

[Show more]

Preview 3 out of 28  pages

  • No
  • 7, 8, 11, 14
  • October 5, 2022
  • 28
  • 2022/2023
  • Summary
avatar-seller
CHAPTER 7: Scope Planning


(1.1.)Scope Planning Process
(1) Plan Scope Management
(2) Collect project requirements
(3) Define project scope
(4) Create work breakdown structure (WBS)
(5) Establish change control




Flow of Scope Planning
Plan Scope Management
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.


Total Scope = Product Scope + Project Scope



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

(1.2.)Collect Requirements
Make sure the project team is absolutely clear on the project objectives.

Collect Requirements: a systematic effort to understand and analyse stakeholder needs to define and
document these needs and requirements with a focus on meeting project objectives.

(1.2.1.)Gather Stakeholder Input & Needs
Use voice of the customer techniques (VOC)
▪ Ask questions
▪ Place yourself in the customer’s situation
▪ State customer desires in operational terms

,Collecting requirements is same regardless of type of project. Generally Agile documentation is less formal,
thus allowing for progressive elaboration
Common methods for obtaining & documenting requirements:
▪ Meetings with Stakeholders
▪ Interviews
▪ Focus Groups
▪ Questionnaires
▪ Surveys
▪ Observations
▪ Prototypes
▪ Industry Standards
▪ Reference Documents
▪ Market Analysis
▪ Competitive Analysis
▪ Client Requests
▪ Standard Specifications


Seek a high-level description:

What do we not understand about the 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?



Requirements Traceability Matrix

, (1.3.)Define Scope
Define Scope: the process of translation stakeholder needs and requirements into detailed specifications of
the project outcomes & products.

Reasons to Define Scope ▪ All other planning is based on the project scope
▪ Needed to preventing scope creep
How to Define Scope (1) List project deliverables (Determine
acceptance criteria)
(2) Establish project boundaries
a. In scope vs. Out of scope
b. Understand constraints
(3) Create a Scope Definition

Defining Scope in Agile ▪ At beginning of project, overall scope only identified at high level
Projects ▪ Backlog of possible work identified also
▪ Use smaller, frequent iterations to get feedback, as customer desires evolve
over time
▪ Customer representative (“owner”) prioritizes scope based on business need,
value, cost, & risk.




(1.4.)WORK BREAKDOWN STRUCTURE (WBS)

WBS: Tool to progressively divide project deliverables into smaller pieces. It Identifies all deliverables. A
framework for further planning, execution, and control.


Define Activity: a project planning process which identifies and determines specific actions to develop and
deliver the project outcomes, such as products, services or results


(1.4.1)Purpose of WBS:
▪ Ensures all parts of project are considered
▪ Adds discipline and visibility to project planning
▪ Basis for planning schedule, resources, cost, quality, & risk
▪ Useful in determining where and why problems occur
▪ Helpful in project communications

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 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 these notes from?

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

Will I be stuck with a subscription?

No, you only buy these notes for $4.54. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

67096 documents were sold in the last 30 days

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

Start selling

Recently viewed by you


$4.54
  • (0)
  Add to cart