0% found this document useful (0 votes)
15 views2 pages

RACI Matrix and Project Management Tools

The document contains a series of questions and answers related to project management techniques and tools. Key concepts include the RACI matrix for defining roles, the burndown chart for tracking project progress, multivoting for prioritizing requirements, and the Work Breakdown Structure (WBS) for organizing project scope. Additionally, it highlights the importance of including high-level requirements and risks in a project charter for sponsor approval.

Uploaded by

kab1976
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views2 pages

RACI Matrix and Project Management Tools

The document contains a series of questions and answers related to project management techniques and tools. Key concepts include the RACI matrix for defining roles, the burndown chart for tracking project progress, multivoting for prioritizing requirements, and the Work Breakdown Structure (WBS) for organizing project scope. Additionally, it highlights the importance of including high-level requirements and risks in a project charter for sponsor approval.

Uploaded by

kab1976
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Q1. Which technique is used to identify roles and the level of responsibilities?

A. Capability table
B. Dependency and responsibility tracker
C. Responsible, accountable, consulted, and informed (RACI) matrix
D. Affinity diagram

Q1. Answer: C
Explanation: The RACI matrix is correct because it clearly defines roles and responsibilities within a
project or process. It helps identify who is Responsible, Accountable, Consulted, and Informed for each
task or decision. This ensures clarity, avoids confusion, and improves communication and accountability
among team members, making it an effective tool for role identification.

Q2. What is an agile control method that shows where the project is going over time?
A. Burnup chart
B. Backlog
C. Kanban board
d. Burndown chart

Q2. Answer: D
Explanation: A burndown chart is the agile control method that shows where a project is going over
time. It plots remaining work (story points) against time, trending downward as tasks are completed.
Widely used in Scrum, it predicts completion, helping teams adjust if progress lags, aligning with PMI’s
focus on tracking sprint or project trajectory.

Q3. At a requirements workshop, the attendees have stated that all of the elicited requirements are
"must haves." Which tool can be used to prioritize the requirements?
A. Use case
B. Multivoting
C. Peer review
D. Wireframe

Q3. Answer: B
Explanation: Multivoting is a prioritization technique used when a group needs to narrow down a list of
options. In a requirements workshop, if all requirements are seen as "must haves," multivoting allows
participants to vote on the most critical items. This helps the team reach consensus and focus on high-
priority requirements without bias or conflict.

Q4. A project team is working closely with the product owner in order to determine inputs for the
scope. Due to the complexity of the project, the team will develop a hierarchical description of the
project requirements in order to deliver the expected business value. Which artifact will be
developed?
A. Risk breakdown structure (RBS)
B. Definition of done (DoD)
C. Return on investment (ROI)
D. Work breakdown structure (WBS)

Q4. Answer: D
Explanation: A Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of
work required to complete a project. It helps break down complex projects into manageable sections. In
this scenario, the team uses the WBS to organize requirements and ensure all elements needed to
deliver business value are clearly defined and structured.

Q5. A project manager has finished the project charter draft and presents it to the sponsor. However,
the sponsor notifies the project manager that two items are missing in order to obtain document
approval. Which two of the following should be included? (Choose two)
A. High-level requirements
B. Stakeholder register
C. Assigned team members
D. High-level risks
E. Assumption lo

Q5. Answer: A & D


Explanation: The project charter is a foundational document that formally authorizes a project. It
typically includes high-level requirements to define what the project must achieve and high-level risks to
highlight potential challenges. These elements help ensure alignment with business objectives and
prepare stakeholders for potential issues, making them essential for sponsor approval.

Common questions

Powered by AI

The elements of the project charter essential for obtaining sponsor approval include high-level requirements and high-level risks. High-level requirements define what the project must achieve, while high-level risks highlight potential challenges, ensuring alignment with business objectives and preparing stakeholders for potential issues .

A burndown chart facilitates progress tracking in agile project management by plotting the remaining work (in story points) against time. This chart trends downward as tasks are completed, providing a visual representation of project progress and predicting completion dates. It is widely used in Scrum to help teams adjust their pace if progress is lagging, aligning with PMI's focus on tracking sprint or project trajectory .

The use of an affinity diagram is most appropriate in project management when there is a need to organize a large amount of brainstorming data into categories. This tool helps project teams identify patterns and surface common themes, which is particularly useful during initial phases when project ideas or issues need to be structured to guide strategic planning and decision-making .

Not including high-level risks in the project charter can have several potential consequences, including misalignment with business objectives and unexpected challenges during project execution. High-level risks provide early visibility into potential obstacles, enabling proactive planning and stakeholder preparedness. Their exclusion may result in unanticipated delays, increased costs, and decreased project quality .

A team might opt to use a wireframe over a use case document in the early stages of gathering software requirements because wireframes provide a visual representation of the user interface, which can be more effective for stakeholders to understand and communicate features and user interactions. This can lead to better insights into user experience and functionality needs, facilitating a more engaging and intuitive design process .

A Work Breakdown Structure (WBS) is critical for managing complex projects because it breaks down the project requirements into a hierarchical description, making it easier to organize and manage. By ensuring all elements needed to deliver business value are clearly defined and structured, a WBS helps teams manage scope, schedule, and deliverables effectively .

Multivoting is particularly useful during a requirements workshop when all elicited requirements are perceived as 'must haves,' and the group needs to prioritize and narrow down a long list of options. This technique allows participants to vote on the most critical items, facilitating consensus and focusing on high-priority requirements without bias or conflict .

The dependency and responsibility tracker and the RACI matrix differ in their approach to assigning project roles. A RACI matrix explicitly identifies and clarifies roles—who is Responsible, Accountable, Consulted, and Informed—ensuring accountability and transparency. In contrast, a dependency and responsibility tracker focuses on tracking task dependencies and corresponding responsibilities, potentially leading to less clarity in roles compared to the structured designation of the RACI matrix .

The primary purpose of a RACI matrix in project management is to clearly define roles and responsibilities within a project or process. It helps identify who is Responsible, Accountable, Consulted, and Informed for each task or decision, ensuring clarity, avoiding confusion, and improving communication and accountability among team members .

Burnup charts complement burndown charts in agile project management by showing the amount of work completed against the total scope over time. While burndown charts display the remaining work, burnup charts track progress towards completion and can highlight scope changes. Together, they provide a comprehensive view of both the work done and the work left, allowing teams to better manage and adjust their project trajectory .

You might also like