Pmi-Pba - Traceability & Monitority

Front 1

___ is at the heart of organizing and management requirements

Back 1

Traceability

Front 2

What area of knowledge crosses multiple domains?

Back 2

Traceability & Monitoring

Front 3

The requirements traceability plan includes what?

Back 3

Documentatio, management, and communication of requirements through the requirements life cycle

Front 4

What are the themes of the "Traceability & Monitoring" domain?

Back 4

- Consider the life cycle approach- Traceability

Front 5

What is the mnemonic for the tasks of the "Traceability & Monitoring" domain?

Back 5

TMUCC (Too Many Undertones Cause Confusion"

Front 6

What are the five tasks of the "Traceability & Monitoring" domain?

Back 6

- Trace Requirements- Montior Requirements' Status- Update Requirements' Status- Communicate Requirements- Manage Changes to Requirements

Front 7

What is the defintion of th etask "Trace Requirements" in the "Traceability & Monitoring" domain?

Back 7

Use a traceability artifact or tool, capture the requirements' status, sources, and relationships (including depdencies), in order to provid evidence that the requirements are deliverd as stated

Front 8

What is the definition of the task "Monitor Requirements Status"?

Back 8

Monitor requiremenst throughout their lifecycles using a traceability artifact or tool in order to ensure the appropriate supporting requirements artifacts (such as models, documentation, and test cases) are produed, reviewed, and approved at each point in the lifecycle

Front 9

Wahat is the definition of the task "Update Requirements Status"?

Back 9

Update a requirement's status as it moves through its lifecycle states by communicating with appropriate stakeholders and recording changes in the traceability artifact or tool in order to track requirements toward closure

Front 10

What is the definition of the task "Communicate Requirements Status"?

Back 10

Communicate requirements status to the project manaager and other stakeholders using communication methods in order to keep them informed of requirements issues, conflicts, changes, risks, and overall status

Front 11

What is the defintiion of the task "Manage Changes to Requirements"?

Back 11

Manage changes to requirements by assessing impacts, dependencies, and risks in accordance with the Change Control Plan, an dcomparing tot the requirements baseline in order to maintain the integrity of the requirements and associated artifacts

Front 12

What is "Requirements Traceability"?

Back 12

The ability to trace a requirement's relationships through the development life cycle. It should be bi-directional, to trace requirements back to the business need for them, and forward through design and implementation

Front 13

What is the term used for forward traceability?

Back 13

Allocation

Front 14

What is the term used for backward traceability?

Back 14

Derivation

Front 15

Derivation describes the ___ of a requirements by tracing back to the business need

Back 15

Lineage

Front 16

Allocation traces a requirement through what?

Back 16

Development, testing, and implementation

Front 17

How does traceability help manage scope?

Back 17

By connecting requirements to the business need behind an initiative

Front 18

What additional things might Traceability support?

Back 18

- Risk Management- Cost management- Communication Management

Front 19

Traceability is useful for identifying ___ functionality

Back 19

Missing

Front 20

Waht is a "rogue" requirement?

Back 20

A requirement or functionality that is added that doesn't support the business objectives

Front 21

What are the different levels that traceability may be performed at?

Back 21

- Requirement level- Group level- Feature or function level

Front 22

What factors are involved in determining the proper level for traceability?

Back 22

- Kind of project being developed- Amount of time available- Regulations- Organizational preferences

Front 23

What is an "Interrelationship"?

Back 23

Requirements that have relationships to other requirements and deliverables

Front 24

Why is it important to document interrelationships between requiremetns?

Back 24

- Assists in impact analysis- Shows requirements coverage- Requirements allocation

Front 25

What type of analysis is greatly aided by traceability?

Back 25

Impact Analysis

Front 26

What performing the task "Trace Requirements", what are some important considerations?

Back 26

- Relationships- Requirements Management Tools- Adaptive Project Approaches

Front 27

Waht are the categories of relationships to be considered in requirements traceability?

Back 27

Necessity, Effort, Subset, Cover, Value

Front 28

What does the "necessity" relationships mean?

Back 28

Represents a dependency, where one requirements is only pertinent when another is included

Front 29

What does the "Effort" relationship mean?

Back 29

If one requirement is implemented, it makes it easier to implement another

Front 30

What does the "Subset" relationship mean?

Back 30

One requirement may be a decomposed subset of another

Front 31

What does the "Cover" relationship mean?

Back 31

One requirement fully includes one or more othe requirements

Front 32

What does the "Value" relationship mean?

Back 32

One requirement affecst the desireability of another, either positively or negatively

Front 33

When would it be most advatageous to use a requirements management tool?

Back 33

When there are large numbers of requirements that need to be traced

Front 34

What are the advatnageds of using a requirements management tool?

Back 34

- Ability to configure and customize the input of requirements- Improves requirements communication- May provide diagramming and wireframe tools

Front 35

What do most organizations rely on for traceability (in absence of a requirements managemnet tool)?

Back 35

Office productivity software, such as Word and Excel

Front 36

True or False: a requirements traceability matrix will be used on an adaptive project

Back 36

FALSE. Instead, stakeholder level requirements will be traced and maintained via the product backlog

Front 37

What is a "Product Backlog"?

Back 37

A list of stack-ranked, prioritized list of user stories representing stakeholder requirements

Front 38

User stories are typically recorded in the least ___ way that will support their development within the iteration

Back 38

Formal

Front 39

What techniques are used in the task "Trace Requirements"?

Back 39

- Backlog managemnet- Isuse (problem) tracking- REquirements traceability matrix

Front 40

What ist he output of the atsk "Trace Requirements"?

Back 40

Requirements Traceability Matrix (updated), if using a Predictive approach, OR groomed product backlog if using Adaptive

Front 41

What governs the tools, process, and items to be included on a RTM?

Back 41

Requirements Management Plan

Front 42

Actively ___ and ___ the RTM is key to effective traceability and quality requirements

Back 42

Monitoring and Updating

Front 43

Who is responsible for making sure the RTM has the information is needs?

Back 43

Business Analyst

Front 44

What are the considerations for the task "Montior Requirements Status"?

Back 44

- Progressive Elaboration- Business Analysis Work Products- Team Deliverables- Issue and Problem Tracking

Front 45

As requirements move through the lifecycle, additional ___ may emerge

Back 45

Details about Requirements

Front 46

True or False: Requirements and specifications that emerge in support of already approved requirements are considered a support detail rather than a new requirement

Back 46

TRUE. These are not considered new requirements.

Front 47

Where should references to BA Work Products be recorded and tracked?

Back 47

Requirements Traceability Matrix

Front 48

Why might it be helpful to track BA work products?

Back 48

May highlight if a requirement has not been further analyzed if no work products are found or referenced

Front 49

True or False: Team deliverables should not be included in the RTM

Back 49

FALSE. This is a good way to track the status of team deliverables, such as test cases, design docs, etc.

Front 50

What are some conditions that requirements are in that may make them "not suitable for development"?

Back 50

- Conflicts exist in the requirements- Unconfirmed assumptions are not resolved- Open questions exist

Front 51

True or False: Issues are not tracked on the RTM

Back 51

Neither. They may or may not be tracked on an RTM. They could also be individually tracked with a reference on the RTM

Front 52

What techinques are used for the task "Monitor Requirements Status"?

Back 52

- Backlog management- Requirements Traceability Matrix- Issue (Problem) Tracking

Front 53

What is the output of the task "Monitor Requirements Staus"?

Back 53

Updated Requirements Traceability Matrix (or backlog)

Front 54

What is the purpose of the task "Update Requirements Status"?

Back 54

To keep the status up-to-date throughout the requirements lifecycle process

Front 55

What is an important element of the task "Monitor Requirements Status"?

Back 55

Being proactive in working with the team to monitor the status so updates can be mad ein a timely manner

Front 56

What are some possible open statuses of requirements?

Back 56

Proposed, approved, in progress, completed

Front 57

What are some possible closed statuses of requirements?

Back 57

Rejected, cancelled, deferred, implemented

Front 58

What is a "Requirements Life Cycle State Diagram"?

Back 58

A diagram depecting the state of requirements in a typical project lifecycle

Front 59

What is the purpose of the task "Communicate Requirements STatus"?

Back 59

To advise stakeholders of current requirements status and keep them aprised of issues, conflicts, and risks

Front 60

How does communicating requirements status help a project?

Back 60

- Giving stakeholders the opportunity to help facilitate resolution of any issues that may exist- Helping to manage expectactions by providing early notification of potential risks

Front 61

What are the considerations for communicating requirements status?

Back 61

- Communication Plan- Communication by Role

Front 62

Who should teh BA collaborate with on creating the requirements communication plan?

Back 62

Project Manager

Front 63

In communicating requirements status to stakeholders, what is important to consider?

Back 63

The presentation preferences of the stakeholders, and the level of formality that is applied

Front 64

True or False: All stakeholders require full details of all requiremetns

Back 64

FALSE. Different stakeholders care about different levels of information relating to requirements

Front 65

What is the definition of a backlog?

Back 65

Planned work that is not yet completed

Front 66

What are some common roles or groups that the BA may need to communicate requirements status to?

Back 66

- Executive Management- Project Sponsor- Technology team- Project Manager- Business Stakeholders- Quality Assurance

Front 67

Who should receive a high-level summary when communicating requirements stauts?

Back 67

Executive Management

Front 68

Who should receive detail functional and non-functional requirements?

Back 68

Technology and QA

Front 69

Who should review the Business Requirements?

Back 69

Project Sponsor

Front 70

Who needs to see detailed requirements in business language?

Back 70

Business Stakeholders

Front 71

Who needs to receive the Requirements Package?

Back 71

Project Manager

Front 72

What is the output of the task "Update Requirements Status"?

Back 72

Requirements status communicated at the appropriate level of detail for the recipient

Front 73

What is the purpose of the task "Manage Changes to Requirements"?

Back 73

To manage changes to requirements once they are baselined (in predictive projects), using a change control process

Front 74

In adaptive projects, at what point are requirements not allowed to change?

Back 74

Within the current sprint or iteration

Front 75

What is a Change Control Plan?

Back 75

The process that governs how change will be managed and controled in a predictive environment

Front 76

Following the ___ ___ Plan is the first defense against scope creep

Back 76

Change Control

Front 77

Who is responsible for managing the product scope?

Back 77

Business Analyst

Front 78

Who is responsbiel for managing the project scope and processes?

Back 78

Project Manager

Front 79

True or False: The BA is responsible for managing the project scope and processes

Back 79

FALSE. This is the role of the project manager

Front 80

True or False: The BA is repsonsible for managing the product scope

Back 80

TRUE. This is the BA's responsiblity

Front 81

What is a CCB?

Back 81

Change Control Board

Front 82

What is Impact Analysis?

Back 82

To assess the impact of a change to determine the potential resulting effects of the change.

Front 83

When a change happens, what must be updated?

Back 83

The Requirements, and any related impacted artifacts or work products

Front 84

What aids in ensuring that the most recent document is being used (when changes have been made)?

Back 84

Version control

Front 85

What additional type of techniques (besides traceability) are used in the task "Manage Changes to Requirements"?

Back 85

Change Control, Version Control

Front 86

What change control technique is used in the task "Manage Changes to Requirements'?

Back 86

Configuration Management System (CMS)

Front 87

What version control techinque is used to "Manage Changes to Requirements"?

Back 87

Version Control System (VCS)

Front 88

What are the outputs of the task "Manage Changes to Requirements"?

Back 88

- Updated RTM- Requirements Baseline updated

Front 89

What is Backlog Management?

Back 89

The tools and techniques used to manage and maintain backlog work to be completed

Front 90

What is a Backlog?

Back 90

A prioritized list of user stories with the highest priority stories at the top

Front 91

Who maintains the Product Backlog?

Back 91

Product Owner

Front 92

What elements might be included in an Issue log?

Back 92

Description, date discovered, impact, priority, date needed by, owner, status, date closed, etc.

Front 93

Unique identified, WBS cross reference, and Version are examples of elements of what type of document?

Back 93

Requirements Traceability Matrix

Front 94

True or False: sophisticated tools to capture, update, and communicate versions are the only way to perform version control

Back 94

FALSE. A version control "system" may include a manual set of processes to manage versions