Scope + Requirements Flashcards
What is the primary purpose of defining the project scope in project management?
A. To outline the project’s budget and cost estimation
B. To establish the project’s timeline and milestones
C. To specify the boundaries of the project, including deliverables, objectives, and constraints
D. To identify potential risks and develop a risk management plan
C. To specify the boundaries of the project, including deliverables, objectives, and constraints
Defining the project scope involves specifying the boundaries of the project, which includes identifying the deliverables, objectives, and constraints. This ensures that all stakeholders have a clear understanding of what is included and excluded from the project, thereby guiding the project’s execution and preventing scope creep.
Where do you find the project plan?
Scope Management Plan
What is a scope statement?
A general description of the project
During the execution of your project, a need arises to modify the Requirements Management Plan to better align with new stakeholder needs and project objectives. What must be done to implement these changes?
A. The project team can make the changes informally as needed.
B. Submit a change request for review and approval through the Change Control Process.
C. Notify stakeholders of the changes without any formal process.
D. Update the Requirements Management Plan immediately and communicate the changes afterward.
B. Submit a change request for review and approval through the Change Control Process.
In an Agile project, the project team maintains a prioritized list of features, enhancements, and fixes that are needed to deliver the product. What is this list commonly referred to as?
A. Work Breakdown Structure (WBS)
B. Product Backlog
C. Requirements Traceability Matrix
D. Project Charter
B. Product Backlog
In Agile project management, the Product Backlog is a prioritized list of features, user stories, enhancements, and bug fixes that are required to develop the product. The backlog items are continuously reviewed and prioritized by the Product Owner to ensure that the most valuable items are addressed first.
When looking at an Agile project Requirements Mgmt Plan… who decides which backlog occur in which sprint?
The Product Owner along with the Team (NOT the scrum master)
Once all the Requirements for a project are determined, where are they placed?
In a requirement matrix
When prioritizing requirements, one technique used is MoSCoW, define:
M=MUST have
S=SHOULD have
C=COULD have
W=WON’T have
{benefit: focus on most important features; common in Agile}
You are managing a project to develop a new product, and your team is identifying and prioritizing features that will impact customer satisfaction. You want to differentiate between features that are basic expectations, those that will delight customers, and those that are simply satisfiers. Which method should you use to classify these features?
A. MoSCoW Prioritization
B. Pareto Analysis
C. Kano Method
D. SWOT Analysis
C. Kano Method
Kano Method: The Kano Method is used to categorize product features into different types based on their impact on customer satisfaction:
Must-be (Basic) attributes: Features that customers expect and take for granted.
Performance attributes: Features where customer satisfaction is proportional to the level of functionality.
Delighters (Exciters): Features that provide high satisfaction when present but do not cause dissatisfaction when absent.
Your project team has generated a large number of ideas during a brainstorming session to solve a complex problem. To organize these ideas into meaningful categories and identify patterns, which tool should you use?
A. Gantt Chart
B. Affinity Diagram
C. Work Breakdown Structure (WBS)
D. Fishbone Diagram
B. Affinity Diagram
Post it Notes
Affinity Diagram: An affinity diagram is a tool used to organize a large number of ideas or data points into groups based on their natural relationships. It helps in identifying patterns, common themes, and key areas of focus, making it easier to analyze and understand complex information.
As a project manager, you need to visually represent how your project’s system interacts with external entities, such as users, other systems, and external organizations. This representation should provide a high-level overview of the system’s boundaries and relationships. Which tool should you use?
A. Flowchart
B. Work Breakdown Structure (WBS)
C. Context Diagram
D. Fishbone Diagram
C. Context Diagram
{hint: on exam the diagram depicting requirements with people is Context.}
A Context Diagram is a high-level diagram that shows the system under consideration as a single process and how it interacts with external entities (actors, systems, etc.).
In project management, which technique is used to decompose a product into its constituent parts to ensure detailed understanding and management of the product’s components?
Answer Choices:
A. Work Breakdown Structure (WBS)
B. Product Breakdown Structure (PBS)
C. Requirements Traceability Matrix (RTM)
D. Agile Product Roadmap
B. Product Breakdown Structure (PBS)
The Product Breakdown Structure (PBS) is used to decompose a product into its individual components or parts, providing a detailed understanding of the product’s structure. This is essential for managing and controlling the product’s development and ensuring that all necessary components are identified and addressed.
In a software development project, the product breakdown might include decomposing the software into major modules (e.g., user interface, database management, and application logic), then further breaking down each module into individual components (e.g., login system, data processing engine, etc.).
In a complex project, you are tasked with analyzing and defining product requirements and ensuring that all system components work together effectively. Which approach would be most appropriate to use for this comprehensive analysis and integration?
A. Cost-Benefit Analysis
B. Systems Engineering
C. SWOT Analysis
D. Monte Carlo Simulation
B. Systems Engineering
Systems Engineering: This approach is used for analyzing and defining the system requirements and ensuring that all components of the system work together as intended.
Define WBS
Work Breakdown Structure
What is the work defined at the lowest level of the work breakdown structure?
Work Package
A Work Package is a detailed, discrete component of work within the Work Breakdown Structure (WBS) that is defined by its scope, time, and cost. It is the smallest unit of work that can be assigned to a team member or a team, and its completion is necessary to achieve the project’s objectives.
The Work Package is a component of the WBS, which is a hierarchical decomposition of the total scope of the project into smaller, manageable parts. The WBS helps in organizing and defining the total project work, with Work Packages being the lowest level of detail.
