Traceability and Monitoring Domain Flashcards
Jim was hired as the lead business analyst on a factory refurbishment project. Jim identified the key stakeholders and concluded product requirements elicitation and analysis activities. He now has a solid product requirements traceability matrix that he will continue to update throughout the product development. The project is most likely following:
A predictive lifecycle
An adaptive lifecycle
An Agile lifecycle
An incremental lifecycle
A predictive lifecycle
The scenario is implying a firm sequence of requirements management processes, this is typical of predictive projects. Predictive projects provide a better case for formal traceability than adaptive projects. [The PMI Guide to Business Analysis, page 259]
When analyzing relationships between product requirements, each product requirement is examined from various lenses to understand its relationships with other product requirements. Which of the following is NOT a valid example of a relationship between product requirements?
Implementation dependency
Value dependency
Subsets
Discretionary dependency
Discretionary dependency
Discretionary dependency is a concept in project scheduling, and it exists between project tasks and not product requirements. The rest of the choices are all valid product requirement relationship types. [The PMI Guide to Business Analysis, page 259]
Your project’s scope was earlier represented by epics. However, these have now been replaced with user stories. What is the relationship between epics and user stories?
Implementation dependency
Subsets
Discretionary dependency
Value dependency
Subsets
Discretionary dependency is a concept in project scheduling; this dependency exists between project tasks and not product requirements. The rest of the choices are all valid product requirements relationship types. Epics are broken down into smaller user stories, hence the relationship between them is “subsets”. [The PMI Guide to Business Analysis, page 259]
You are managing a complex workflow automation project. The customer values module A more and wants that to be delivered as soon as possible. However, the module A cannot be delivered prior to delivering module B due to some technical limitations. What is the relationship between module A and B?
Subsets
Value dependency
Implementation dependency
Soft dependency
Implementation dependency
This is an example of an implementation dependency; some requirements are dependent on the implementation of other requirements before they can be implemented. [The PMI Guide to Business Analysis, page 259]
You have recently joined a team that is developing a management information system. You are surprised to find that although a thorough list of product components and sub-components exists, no documentation exists that establishes relationships between these. Which of the following is a graphical tool you should use to fill-in this gap?
Salience model
Feature model
PERT diagram
Fishbone diagram
Feature model
A feature model is a scope model that visually represents all the features of a solution arranged in a tree or hierarchical structure. The feature model helps teams establish and communicate relationships between different features. [The PMI Guide to Business Analysis, page 260]
You are leading an organizational transformation project. The lead business analyst on this project has recently resigned and now you are responsible for all business analysis activities on the project. The previous analyst has done a good job collecting, analyzing and documenting the requirements. However, you are worried that, given the number of requirements and the agility required by the project environment, maintaining audit trails and managing version control will be difficult. Which of the following should you consider at this stage?
Developing a work breakdown structure
Developing a feature model
Using a requirements management tool
Using a stakeholder engagement register
Using a requirements management tool
A requirements management tool allows requirements and other product information to be captured and stored in a central repository. Such a tool typically has the ability to maintain audit trails and perform version control to assist with change management. None of the other choices have the capability or ability to perform this. [The PMI Guide to Business Analysis, page 260]
You have recently taken over a project which is currently in its early planning stage. You are not happy with the documented product requirements as you think they are too broad. Which of the following technique is used to breakdown higher level user stories into lower level user stories for manageability and ease of development?
Story mapping
Storyboarding
Story slicing
Storytelling
Story slicing
Story slicing is a technique used to split requirements or user stories from a higher level to a lower level. Story mapping is a technique used to sequence user stories. The other two choices are not user story management techniques. [The PMI Guide to Business Analysis, page 261]
You are leading an automobile engine design project. A number of product requirements were elicited and analyzed. Which of the following business analysis projects will you perform in order to confirm which requirements should be incorporated within an iteration, release or project?
Verify Requirements
Prioritize Requirements and Other Product Information
Validate Requirements
Select and Approve Requirements
Select and Approve Requirements
Select and Approve Requirements is the process of facilitating discussions with stakeholders to negotiate and confirm which requirements should be incorporated within an iteration, release, or project. Note that this process is performed after the Verify Requirements and Validate Requirements processes. [The PMI Guide to Business Analysis, page 263]
A requirements baseline serves as the backbone of all predictive projects. Which of the following correctly defines the requirements baseline on a typical waterfall project?
Verified requirements
Prioritized requirements
Approved requirements
Validated requirements
Approved requirements
Approving requirements is performed to obtain agreement that the requirements accurately depict what the product team is being asked to build. Requirements that are approved establishes the requirements baseline. [The PMI Guide to Business Analysis, page 264]
The product owner has just asked your team to drop a user story from the current sprint. According to the product owner, the business requirements have changed and so have the priorities of the user stories on your Agile project. What should you do next?
Move the story back into the backlog.
Request the product owner to initiate a formal change enablement.
Mark the story as unwanted.
Complete the story during the sprint but do not release it.
Move the story back into the backlog.
The user story is not wanted at this stage. However, it has not been established that it is unwanted. The best course of action is to move the story back into the product backlog where it will be reprioritized. [The PMI Guide to Business Analysis, page 264]
You want to initiate a major organizational change. The initiative, if successful, will significantly impact the organization’s bottom line. However, given the magnitude of the change, significant resistance to change is also expected from the staff. Which of the following tools could help you analyze this change initiative and its impact?
Pareto analysis
Fishbone analysis
Force field analysis
Kano analysis
Force field analysis
Force field analysis is a decision-making technique that can be used to help teams analyze whether there is enough support to pursue a change. Forces FOR the change are compared with forces AGAINST the change to determine the overall impact of the change initiative. [The PMI Guide to Business Analysis, page 266]
You conducted a requirements approval workshop with the key stakeholders. Most of the requirements were approved by all stakeholders without any disagreements. However, there was one particular requirement that attracted a lot of debate. Voting was carried out to the resolve the matter and the following results were obtained: 45% of the stakeholders approved the requirement, 40% rejected the requirement, while 5% said they were indifferent. Based on this result, you decided to consider the requirement approved. What group decision-making technique was used?
Plurality
Majority
Unanimity
Autocracy
Plurality
Majority is reached when more than 50% of people are in support of an outcome. Plurality is obtained by the taking the most common answer received from the decision makers; the number of votes are more than any other but does not receive a majority. [The PMI Guide to Business Analysis, page 267]
Your team has decided to test Agile methods on your current project. You have agreed to this request, however, you would like the team to understand and agree on some basic Agile principles and concepts. On adaptive projects, sprint planning means:
Identifying a subset of product backlog for development in the rest of the project sprints.
Identifying a subset of sprint backlog for development in the rest of the project sprints.
Identifying a subset of product backlog for development in the next sprint.
Identifying a subset of sprint backlog for development in the next sprint.
Identifying a subset of product backlog for development in the next sprint.
In adaptive projects, iteration planning, or sprint planning, is the activity used to identify the subset of project backlog items from the product backlog that the development team will work on for the current/upcoming iteration or sprint. The iteration/sprint planning plans one iteration/sprint at a time, not all of the remaining iterations/sprints. [The PMI Guide to Business Analysis, page 267]
Which of the following statements regarding requirements management is correct for projects following a predictive lifecycle?
Requirements validation ensures quality delivery in conformance to standards and regulations.
Requirements verification ensures delivery meeting business needs and stakeholder requirements.
Requirements should be approved after verification and validation.
When requirements are approved, they are automatically considered to be verified and validated.
Requirements should be approved after verification and validation.
Approved requirements are requirements that are verified and validated. This doesn’t mean that when requirements are approved, they are automatically considered to be verified and validated. The Select and Approve Requirements process is performed after the Verify Requirements and Validate Requirements processes. [The PMI Guide to Business Analysis, pages 263, 268]
Agile projects typically do not schedule formal requirements approval workshops. On such projects, product requirements are often considered approved after:
Scrum master assigning user stories to sprint backlog.
The product owner’s prioritization of the backlog.
The team agreeing with the project charter.
The team concluding a retrospective.
The product owner’s prioritization of the backlog.
On adaptive projects, the product owner has the authority to approve requirements. Typically, on these projects, the product owner’s prioritization of the backlog is generally interpreted as approval. [The PMI Guide to Business Analysis, page 268]
