Final Exam Flashcards
(38 cards)
Collect requirements - outputs
Outputs
1. Requirements documentation
2. Requirements Traceability matrix
What is a BRD
Business Requirements Document
-Details the business solution (customer needs)
-Gain agreement with the stakeholders
-Used for communication and understanding
What are functional or Non-Functional requirements
-Requirements are brief, clear and concise statements with verbs like “shall” and “will ( not “should”)
- Measurable and clear
-Don’t combine multiple requirements into one statement
What is a functional requirement
Part of the BRD- business requirement document
Functional requirement is a feature or component of the system.
Example a website Shall… have a about us page
- Inputs, behaviors, outputs
-Specifies what the system should do - Requirements must be measurable and clear (especially when writing quantities – no ambiguity like “some” or “a few”)
What is a non functional requirement - NFR
Part of the BRD - Business requirements document
Non functional - Properties that a product must have, perhaps
-Cost or schedule
-System responsiveness
-Security
-Reliability
-Usability
- Don’t combine multiple requirements into one requirements statement
What is a requirements traceability matrix
Output of the Collect requirements
- Table used to link requirements to their origin and traces them throughout the project lifecycle
- Ensures requirements add business value by linking to business/project objective
- Ensures requirements are completed
- Detailed description of the project and product scope
–– Product scope:
e.g., features, functionality
of deliverables
–— Project scope:
e.g., budget, schedule
Scope statement checklist
– Business Needs (project objectives,needs and wants)
– Deliverables (What’s in & whats out)
– Milestones
– Technical requirements
– Key resources
- Risks
- High level budget
– Authorization - (acceptance process)
– Assumptions and Constraints
Whats the purpose of the scope statement
- Tells you what’s in the project… and what’s out
- Basis to make future decisions
- Common understanding (objectives and deliverables)
- Can measure performance
- Evaluate change requests against jump off points for the project plan
- Does not include a detailed budget/schedule or specific work steps
Examples of assumptions for a construction project:
- Heavy construction equipment will be available
- The weather will be favorable
- We will be able to obtain construction permits in a timely manner (without delays)
CONTRIBUTORS TO THE SCOPE STATEMENT
Experts
Templates
Forms
Past history
Talk to other project managers
Stakeholders
The customer
What is included in the Scope statement?
***** * The customer, sponsor, or other stakeholders must be able to read the scope statement and agree to WHAT IS BEING CREATED (and what is NOT being created)
*
Contains a detailed description of the project and product scope
– **Product scope: **
e.g., features, functionality
of deliverables
**– Project scope: **
e.g., budget, schedule
Examples of constraints for a construction project:
- Project must be completed before a specified date
- Workers cannot work during the night or while it’s raining
- The project cannot exceed the $2 million budget
- We must use unionized construction workers
WBS > T&T > What is Decomposition
- Breaking the scope and deliverables into a hierarchy of increasingly smaller chunks of work
- Assigning identification codes (WBS codes) to each component at each level
- lowest level of the WBS (smallest unit of work) consists of work packages
- Work package: the lowest level of the WBS for which cost and duration can be estimated and managed
WBS> T&T > Expert Judgement
Different approaches may be used
* Using pre-existing organizational templates
* Top-down approach for creating WBS
* Bottom-up approach when integrating
sub-components
WBS > What are 2 T&T
Expert Judgement
Decomposition
T or F - If you decompose WBS too much, it is inefficient to manage
T
Do all of the work packages, combined, make up the entire scope of the project (the “100 percent rule”)
T
WBS structures consist of deliverables, NOT TASKS OR ACTIVITIES (use nouns, not verbs)
T
Should also WBS include project management work
T
What is rolling wave planning
You might not have enough information to decompose some deliverables at the start of the project – some decomposition may be undertaken as the project goes along and information becomes known.
What are you doing when creating a WBS
- Subdividing project deliverables into smaller, more manageable components
- Deliverable-oriented hierarchical decomposition of the work
- Defines the total work of the project
Create WBS Output
- Scope baseline
a. Scope statement
b. WBS
c. WBS dictionary - Project documents updates
a. Assumption log
b. Requirements documentation
5 Validate Scope Inputs
-Scope baseline
-Requirements documentation
-Requirements traceability matrix
-Verified deliverables
-Work performance data
3 Validate Scope Output
Accepted deliverables
Work performance information
Change requests
