100% tevredenheidsgarantie Direct beschikbaar na betaling Zowel online als in PDF Je zit nergens aan vast
logo-home
Summary OBS220 Notes Covering Ch 7,8,11,14 PM (2022 Semester Test 2) €4,31   In winkelwagen

Samenvatting

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

 14 keer bekeken  0 keer verkocht
  • Vak
  • Instelling
  • Boek

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.,...

[Meer zien]

Voorbeeld 3 van de 28  pagina's

  • Nee
  • 7, 8, 11, 14
  • 5 oktober 2022
  • 28
  • 2022/2023
  • Samenvatting
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

Voordelen van het kopen van samenvattingen bij Stuvia op een rij:

Verzekerd van kwaliteit door reviews

Verzekerd van kwaliteit door reviews

Stuvia-klanten hebben meer dan 700.000 samenvattingen beoordeeld. Zo weet je zeker dat je de beste documenten koopt!

Snel en makkelijk kopen

Snel en makkelijk kopen

Je betaalt supersnel en eenmalig met iDeal, creditcard of Stuvia-tegoed voor de samenvatting. Zonder lidmaatschap.

Focus op de essentie

Focus op de essentie

Samenvattingen worden geschreven voor en door anderen. Daarom zijn de samenvattingen altijd betrouwbaar en actueel. Zo kom je snel tot de kern!

Veelgestelde vragen

Wat krijg ik als ik dit document koop?

Je krijgt een PDF, die direct beschikbaar is na je aankoop. Het gekochte document is altijd, overal en oneindig toegankelijk via je profiel.

Tevredenheidsgarantie: hoe werkt dat?

Onze tevredenheidsgarantie zorgt ervoor dat je altijd een studiedocument vindt dat goed bij je past. Je vult een formulier in en onze klantenservice regelt de rest.

Van wie koop ik deze samenvatting?

Stuvia is een marktplaats, je koop dit document dus niet van ons, maar van verkoper nichav. Stuvia faciliteert de betaling aan de verkoper.

Zit ik meteen vast aan een abonnement?

Nee, je koopt alleen deze samenvatting voor €4,31. Je zit daarna nergens aan vast.

Is Stuvia te vertrouwen?

4,6 sterren op Google & Trustpilot (+1000 reviews)

Afgelopen 30 dagen zijn er 81311 samenvattingen verkocht

Opgericht in 2010, al 14 jaar dé plek om samenvattingen te kopen

Start met verkopen
€4,31
  • (0)
  Kopen