Day 2 Flashcards
What is the Scope Management Plan (traditional)?
✓ Enables the creation of the WBS from the detailed project scope statement
✓ Establishes how the scope baseline will be approved and maintained
✓ Specifies how formal acceptance of the completed project deliverables
will be obtained.
✓ Can be formal or informal, broadly framed or highly detailed.
What should the Scope Management Plan include?
✓ Should include processes to prepare a project scope statement
What are some Scope Management Tools and Techniques?
- Expert judgement- internal and external experts
- Alternatives analysis- Used to evaluate identified options in order to select the options or approaches to use to execute and perform the work of the project
- Meetings- Team members help create the scope management plan
Why are Project and Product Requirements important?
✓ High-level requirements might be documented in the project charter.
✓ Verify that all requirements are determined and documented.
✓ Provide the foundation for building the WBS.
What is the Predictive Project and Product Scope?
✓ Predictive- The scope baseline for the project is the approved version
of the project scope statement, work breakdown structure (WBS), and associated WBS dictionary.
What is an Agile Project and Product Scope?
✓ Agile - Backlogs (including product requirements and user stories)
reflect current project (stakeholder) needs.
What do you measure the completion of the project scope against?
✓ Measure completion of project scope against the project management plan.
What do you measure the completion of the product scope against?
✓ Measure completion of the product scope against product
requirements.
What does a Tolerance Level enable you to do?
Tolerance levels enable you to effectively manage an issue without needing to escalate it every time.
What might an area of Tolerance include?
Areas of tolerance might include:
✓ Budget
✓ Schedule
✓ Quality
✓ Accepted or baselined requirements, including:
- Solution – functional/non-functional
- Business and Stakeholder
- Quality
What are Enterprise Environmental Factors (EEFs)?
Factors that you cannot control but still have an impact on your project; internal and external
What are some internal Enterprise Environmental Factors (EEFs)?
✓ Organizational culture, structure, and governance
✓ Geographic distribution of facilities and resources
✓ Infrastructure
✓ Resource availability
✓ Employee capability
What are some external Enterprise Environmental Factors (EEFs)?
✓ Marketplace conditions
✓ Social and cultural influences and issues
✓ Legal restrictions
✓ Commercial databases
✓ Academic research
✓ Government or industry standards
✓ Financial considerations
✓ Physical environmental elements
What are Organizational Process Assets (OPAs)?
Processes, policies, and procedures are:
✓ Established by the project management office (PMO) or another function outside of the project.
✓ Not updated as part of project work
✓ Templates, lifecycles, and checklists can be tailored, but not updated, for a project.
What are Organizational knowledge bases in an Organizational Process
Assets (OPAs)?
Organizational knowledge bases are:
✓ Updated throughout the project with project information
✓ Updated information such as financial performance, lessons learned, performance metrics and issues, and defects.
What is meant by document analysis?
Derive new project requirements from existing documents such as:
✓ Business plans
✓ Service agreements
✓ Marketing materials
✓ Current process diagrams
✓ Application software documentation
What are focus groups?
✓ Loosely structured, information-sharing sessions
✓ Moderator-guided, interactive
✓ Includes stakeholders and SMEs
✓ Qualitative research
When would you use Questionnaires and Surveys?
Often used data gathering technique:
* With varied audiences
* When a quick turnaround is needed
* When respondents are geographically dispersed
* Where statistical analysis could be appropriate.
What is benchmarking?
✓ Evaluates and compares a business’ or project’s practices with others.
✓ Identifies best practices in order to meet or exceed them.
What are interviews used for?
✓ Helps to identify a stakeholder’s requirements, goals, or expectations
for a project.
✓ Use to identify/define features and functions of desired project’s deliverables.
What is Voting in the Group Decision-Making Techniques?
Collective decision-making and assessment; Determines several alternatives, with future actions as the expected outcome; Use to generate, classify, and prioritize product requirements
What is Autocratic decision making in the Group Decision-Making Techniques?
One team member makes the decision for the group.
What is multicriteria decision analysis in the Group Decision-Making Techniques?
Method - Establish criteria in decision matrix e.g. risk levels, uncertainty, and
valuation; Uses a systematic, analytical approach; Evaluate and rank many ideas
What are the types of voting?
Unanimity
Majority
Plurality
Agile Methods
What is the unanimity type of voting?
Everyone agrees on a single course of action; Useful in project teams with great cohesion.
Example: Delphi technique
What is the Majority type of voting?
Decision reached with > 50% of group support Tip: Create groups of an uneven number of participants to ensure decisions are made and tie
votes avoided.
What is the Plurality type of voting?
Decision reached with largest block in a group deciding, even if majority is not achieved.
Use this method when more than 2 options are nominated.
What is the Agile Method type of voting?
Thumbs up/down/sideways
Fist of Five
What is mind mapping?
✓ Mind Mapping – Consolidate ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas
What is an affinity diagram?
✓ Affinity Diagram – Allows large numbers of ideas to be classified into groups for review and analysis
What is a context diagram?
A context diagram outlines how external entities interact with an internal software system.
It’s primarily used to help businesses wrap their heads around the scope of a system. As a result, they can figure out how best to design a new system and its requirements or how to improve an existing system.
How do you document requirements?
✓ Describes how individual requirements meet project business need.
✓ Starts at a high level before providing details.
✓ Requirements need to be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders.
✓ Format can be simple (document listing all requirements, categorized by
stakeholder and priority) or more elaborate (executive summary, detailed
descriptions, attachments).
What are business requirements?
Higher-level needs of the organization e.g. business issues or opportunities, and reasons why a project has been undertaken.
What are stakholder requirements?
Stakeholder or stakeholder group needs. Reporting requirements.
What are transition and readiness requirements?
Temporary capabilities e.g. data conversion and training requirements needed to transition from the current as-is state to the desired future state.
What are quality requirements?
Condition or criteria needed to validate the successful completion of a project deliverable or fulfilment of other project requirements e.g. tests, certifications, validations.
What are project requirements?
Actions, processes, or other conditions the project needs to meet e.g. milestone dates, contractual obligations, constraints.
What are solutions requirements?
Describe features, functions, and characteristics of the product, service, or result that will meet the business and stakeholder requirements.
(functional and non-functional)
What are solutions (functional) requirements?
Functional requirements - Describe the behaviors of the product; e.g. actions, processes, data, and interactions that the product should execute.
What are solutions (non-functional) requirements?
Non-functional requirements - Supplement functional requirements to describe environmental conditions or qualities required for the product to be effective; e.g. reliability, security, performance, safety, level of service, supportability, retention/purge, etc.
What are the types of the non-functional requirements?
Availability
* How and when is the service available?
* If the service were to become unavailable, how quickly can it be restored to working?
Capacity
* What level of service performance, speed, and throughput is required?
* Given the number of stakeholders using the service, is there enough supply to meet demand?
Continuity
* If there were a disaster of some kind, how quickly could the service be recovered to support operations.
Security
* How well is the service and its information protected from security risks and threats?
* How do you guarantee the confidentiality, integrity, and availability of the information?
What is a Requirements Management Plan?
✓ Planning, tracking, and reporting information for requirements activities.
✓ Configuration management activities:
- Version control rules
- Impact analysis
- Tracing, tracking, and reporting
✓ Required authorization levels for change approval
✓ Prioritization criteria / process
✓ Product metrics and accompanying rationale
✓ Traceability structure, including requirement attributes
What is a requirements traceability matrix?
A requirements traceability matrix is a document that demonstrates the relationship between requirements and other artifacts. It’s used to prove that requirements have been fulfilled. And it typically documents requirements, tests, test results, and issues.
Detailed business requirements
What are the project requirements that you need to collect?
– Scope management plan
– Requirements management plan
– Stakeholder engagement plan
– Project charter
– Stakeholder register
Use tools and techniques such as interviews, focus groups, facilitated
workshops, group creativity techniques.
What are scope tools and techniques?
- Expert judgement
- Facilitation
- Product Analysis
- Multi-criteria decision analysis
- Alternatives analysis
How do you develop a project scope statement?
- Review:
- Scope management plan (developing, monitoring, and controlling project
scope activities) - Project charter (high-level project description and product characteristic
and project approval requirements) - Requirements documentation
- OPAs – templates, processes, and procedures
- Use tools and techniques to define the project scope (expert judgment,
product analysis, alternatives generation, and facilitated workshops). - Document the project scope statement and update project documents.
What can a WBS include?
✓ Code of account identifier
✓ Description of work
✓ Assumptions and constraints
✓ Responsible organization
✓ Schedule milestones
✓ Associated schedule activities
✓ Resources required to complete
the work
✓ Cost estimations
✓ Quality requirements
✓ Acceptance criteria
✓ Technical references
✓ Agreement information
How do you plan work using a WBS?
✓ A control account has two or more work packages.
✓ A planning package may or may not be used.
✓ Each work package is part of a single control account.
✓ Identifiers provide a structure for hierarchical summation of costs,
schedule, and resource information and form a code of accounts.
What is a work breakdown structure (WBS)?
A work-breakdown structure in project management and systems engineering is a deliverable-oriented breakdown of a project into smaller components. A work breakdown structure is a key project deliverable that organizes the team’s work into manageable sections.
