Chapter 5: Stakeholders Flashcards

1
Q

During Trace Requirements, what Stakeholder is affected by how and when requirements are implemented, and may have to be consulted about, or agree to, the traceability relationships?

A

Customers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

During Trace Requirements, what Stakeholder may have recommendations regarding the set of requirements to be linked to a solution component or to a release?

A

Domain Subject Matter Expert

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

During Trace Requirements, what Stakeholder may require specific dependency relationships that allow certain requirements to be implemented at the same time or in a specific sequence?

A

End User

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

During Trace Requirements, what Stakeholder utilises traceability to ensure the solution being developed meets the business need and brings awareness of dependencies between solution components during implementation?

A

Implementation Subject Matter Expert

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

During Trace Requirements, what Stakeholder utilises traceability documentation provides another reference source for help desk support?

A

Operational Support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

During Trace Requirements, what Stakeholder utilises traceability to support project change and scope management?

A

Project Manager

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

During Trace Requirements, what Stakeholder is required to approve the various relationships?

A

Sponsor

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

During Trace Requirements, what Stakeholder is affected by how and when requirements are implemented?

A

Suppliers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

During Trace Requirements, what Stakeholder needs to understand how and where requirements are implemented when creating test plans and test cases, and may trace test cases to requirements?

A

Tester

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

During Maintain Requirements, what Stakeholder references maintained requirements on a regular basis to ensure they are accurately reflecting stated needs?

A

Domain Subject Matter Expert

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

During Maintain Requirements, what Stakeholder utilizes maintained requirements when developing regression tests and conducting impact analysis for an enhancement?

A

Implementation Subject Matter Expert

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

During Maintain Requirements, what Stakeholder references maintained requirements to confirm the current state?

A

Operational Support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

During Maintain Requirements, what Stakeholder references maintained requirements to confirm compliance to standards?

A

Regulator

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

During Maintain Requirements, what Stakeholder references maintained requirements to aid in test plan and test case creation?

A

Tester

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

During Prioritise Requirements, what Stakeholder verifies that the prioritized requirements will deliver value from a customer or end-user perspective, and can also negotiate to have the prioritization changed based on relative value?

A

Customer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

During Prioritise Requirements, what Stakeholder verifies that the prioritized requirements will deliver value from a customer or end-user perspective?

A

End User

17
Q

During Prioritise Requirements, what Stakeholder provides input relating to technical dependencies and can negotiate to have the prioritization changed based on technical constraints?

A

Implementation Subject Matter Expert

18
Q

During Prioritise Requirements, what Stakeholder uses the prioritization as input into the project plan and into the allocation of requirements to releases?

A

Project Manager

19
Q

During Prioritise Requirements, what Stakeholder can verify that the prioritization is consistent with legal and regulatory constraints?

A

Regulator

20
Q

During Prioritise Requirements, what Stakeholder verifies that the prioritized requirements will deliver value from an organizational perspective?

A

Sponsor

21
Q

During Assess Requirements Changes, what Stakeholder provides feedback concerning the impact the change will have on value?

A

Customer

22
Q

During Assess Requirements Changes, what Stakeholder has expertise in some aspect of the situation and can provide insight into how the change will impact the organization and value?

A

Domain Subject Matter Expert

23
Q

During Assess Requirements Changes, what Stakeholder uses the solution or is a component of the solution, and can offer information about the impact of the change on their activities?

A

End User

24
Q

During Assess Requirements Changes, what Stakeholder provides information on both their ability to support the operation of the solution and their need to understand the nature of the change in the solution in order to be able to support it?

A

Operational Support

25
Q

During Assess Requirements Changes, what Stakeholder reviews the requirements change assessment to determine if additional project work is required for a successful implementation of the solution?

A

Project Manager

26
Q

During Assess Requirements Changes, what Stakeholder references changes by auditors to confirm compliance to standards?

A

Regulator

27
Q

During Assess Requirements Changes, what Stakeholder is accountable for the solution scope and can provide insight to be utilized when assessing change?

A

Sponsor

28
Q

During Assess Requirements Changes, what Stakeholder is consulted for establishing impact of the proposed changes?

A

Tester

29
Q

During Approve Requirements, what Stakeholder may play an active role in reviewing and approving requirements and designs to ensure needs are met?

A

Customer

30
Q

During Approve Requirements, what Stakeholder may be involved in the review and approval of requirements and designs as defined by stakeholder roles and responsibilities designation?

A

Domain Subject Matter Expert

31
Q

During Approve Requirements, what Stakeholder uses the solution, or a solution component, and may be involved in the review, validation, and prioritization of requirements and designs as defined by the stakeholder roles and responsibilities designation?

A

End User

32
Q

During Approve Requirements, what Stakeholder is responsible for ensuring that requirements and designs are supportable within the constraints imposed by technology standards and organizational capability plans, and may have a role in reviewing and approving requirements?

A

Operational Support

33
Q

During Approve Requirements, what Stakeholder is responsible for identifying and managing risks associated with solution design, development, delivery, implementation, operation and sustainment, and may manage the project plan activities pertaining to review and/or approval?

A

Project Manager

34
Q

During Approve Requirements, what Stakeholder is an external or internal party who is responsible for providing opinions on the relationship between stated requirements and specific regulations, either formally in an audit, or informally as inputs to requirements life cycle management tasks?

A

Regulator

35
Q

During Approve Requirements, what Stakeholder is responsible to review and approve the business case, solution or product scope, and all requirements and designs?

A

Sponsor

36
Q

During Approve Requirements, what Stakeholder is responsible for ensuring quality assurance standards are feasible within the business analysis information. For example, requirements have the testable characteristic?

A

Tester