Managing Project Execution & Managing Issues and Changes Flashcards

1
Q

this matrix creates a path between a project’s requirements and the artifacts that resolve it.

a) redundancy matrix
b) strong matrix
c) requirements traceability matrix

A

requirements traceability matrix (RTM)

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

a visual task tracking tool

a) fishbone diagram
b) data flow chart
c) task board

A

task board

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

traceability tools for source code

a) java
b) version control
c) nmap

A

version control

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

to delete old code blocks

a) refactor
b) modify
c) reshape

A

refactor

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

this log tracks and manages issues

a) company log
b) risk log
c) issue log

A

issue log

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

an issue found in software development

a) deformity
b) deficiency
c) defect

A

defect

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

this chart measures the total amount of work completed each day

a) throughput chart
b) burnup chart
c) brundown chart

A

burnup chart

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

this chart measures how much work is remaining each day

a) velocity chart
b) burnup chart
c) burndown chart

A

burndown chart

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

this chart measures the number of items completed per iteration

a) velocity chart
b) throughput chart
c) sprint chart

A

throughput chart

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

this chart measures how many story points are completed per iteration

a) velocity chart
b) throughput chart
c) sprint chart

A

velocity chart

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

this meeting is held at the beginning of each sprint, and the team plans their work for the upcoming sprint

a) delivarable planning
b) milestone planning
c) sprint planning

A

sprint planning

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

this meeting occurs when the project moves from one phase to the next

a) consumer review
b) phase gate review
c) ad hoc meeting

A

phase gate review

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

a meeting where you share project information with an audience or a request for data

a) ad hoc report
b) issue report
c) user report

A

ad hoc report

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

this process process makes it more likely that issues will appear in the log before they are forgotten

a) risk tracking
b) issue tracking
c) escaltion tracking

A

issue tracking

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

the events that will activate a need to notify increasingly higher levels of authority

a) issues
b) points of risks
c) points of escalation

A

points of escalation

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

this analysis helps you understand and solve the real problems in a project instead of repeatedly fixing surface issues

a) root cause analysis
b) scatter analysis
c) positive analysis

A

root cause analysis

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

this diagram graphically demonstrates the relationship between two variables

a) correlation diagram
b) mind map
c) scatter diagram

A

scatter diagram

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

as one value increases, so does the other

a) positive correlation
b) negative correlation
c) no correlation

A

positive correlation

19
Q

one variable decreases as the other increases.

a) positive correlation
b) negative correlation
c) no correlation

A

negative correlation

20
Q

no clear relationship between the variables

a) positive correlation
b) negative correlation
c) no correlation

A

no correlation

21
Q

this chart shows time or sequence on the horizontal axis

a) run chart
b) five-why chart
c) data flow chart

A

run chart

22
Q

this analysis starts by defining a problem you experience. Then asks why the issue occurred, which will reveal a new cause for the issue. Next, asks why this cause arose, and repeat the process until you reach what you believe is a solvable root cause

a) cost-benefit analysis
b) five-why analysis
c) trade analysis

A

Five-Why analysis

23
Q

this diagram is helpful for identifying multiple potential causes for a single problem

a) Gantt diagram
b) scatter diagram
c) fishbone diagram

A

fishbone diagram

24
Q

this reflects how it will impact the end-users of a product

a) severity
b) urgency
c) impact

A

severity

25
Q

this measures the time sensitivity of an issue; it should tell you how soon the issue needs to be addressed

a) severity
b) urgency
c) impact

A

urgency

26
Q

this measures how much or how many are affected by an issue

a) severity
b) urgency
c) impact

A

impact

27
Q

a separate process that ensures critical risks and issues receive appropriate follow-up
a) issue escalation
b) control chart
c) change control

A

issue escalation

28
Q

statistical charts that track the variation in a process. It shows if the process is performing as it usually does

a) milestone chart
b) control chart
c) kanban chart

A

control chart

29
Q

shows the highest expected value for the process, assuming everything is under control.

a) lower limit control
b) maximum limit control
c) upper limit control

A

upper control limit (UCL)

30
Q

shows the lowest expected value for the process, assuming everything is under control

a) lower limit control
b) maximum limit control
c) upper limit control

A

lower control limit (LCL)

31
Q

the variation you expect to see

a) special cause variation
b) common cause variation
c) change control variation

A

common cause variation

32
Q

the variation you want to detect when monitoring any project

a) change control variation
b) common cause variation
c) special cause variation

A

special cause variation

33
Q

a formal series of artifacts and procedures that tracks modifications to a project, product, or system

a) change control
b) change log
c) standard changes

A

change control

34
Q

this form collects information about one change request

a) change control
b) change request form
c) change log

A

change request form

35
Q

this log contains all the change requests for the project

a) change control
b) change request form
c) change log

A

change log

36
Q

this limits downtime by creating a timebox where multiple teams can perform functions on a system

a) maintenance windows
b) standard changes
c) release

A

maintenance windows

37
Q

the version of a product that is accessible to end-users in a production environment

a) maintenance windows
b) release
c) standard changes

A

release

38
Q

these are recurring, routine changes with set policies and procedures

a) maintenance windows
b) release
c) standard changes

A

standard changes

39
Q

these are modifications that do not have a set process and do not happen often

a) normal changes
b) standard changes
c) emergency changes

A

normal changes

40
Q

these are unplanned, recovery events

a) normal changes
b) emergency changes
c) standard changes

A

emergency changes

41
Q

this will remove all the new changes, including your changes.

a) emergency changes
b) defect log
c) rollback

A

rollback

42
Q

Defects found in production are recorded on the

a) defect log
b) change log
c) backlog

A

defect log

43
Q

this creates separate environments, allowing more people to work on a product without placing the customer or source code at risk

a) beta testing
b) teired software architecture
c) quality assurance

A

tiered software architecture