WorksheetsDomain#6 Problem Detection and Resolution Mike Griffith
Total questions: 20
Worksheet time: 10mins
Name
Class
Date
1.
A new risk has been discovered halfway through the project. What should your team do first?
a)
Add it to the top of the backlog.
b)
Ask a subject matter expert to assessits probability and impact.
c)
Evaluate its root cause.
d)
Schedule a risk-based spike to resolve or minimize it.
2.
What would be most helpful for improving a team's problem-solving proficiency?
a)
Focus on keeping arguments and disagreements to a minimum.
b)
Encourage them to share their mistakes and problems with each other.
c)
Ask more experienced team members to mentor their peers.
d)
Score their suggestionsand post a leaderboard in the team space to encourage competition.
3.
Which tool or metric would allow a team to find problems most quickly?
a)
Varianceanalysis
b)
Technical debt
c)
Risk burn-up chart
d)
Defect cycletime
4.
As the coach of an agile team, you expect the team members to:
a)
Come to you whenever they encounter a problem
b)
Report all their problems in the daily stand-up meeting
c)
Solve most problems collectively as the work proceeds
d)
Figure out the best solution on their own
5.
Ideally, who will catch and fix a coding error?
a)
The customer will spot it in the demo.
b)
The developers will find it during unit testing.
c)
The reviewer will catch it during pair programming.
d)
The testers will find it in testing.
6.
Two team members are having a difference of opinion about how to build the next user story. What should be done?
a)
The team coach should assessthe level of conflict and intervene appropriately.
b)
The Scrum Master should decide the issue, since it is becoming an impediment to progress.
c)
The product owner should be consulted.
d)
The team should gather to discuss the issue and come up with a collective solution.
7.
Ideally, what does your team want to see on the top line of your risk burn-down graph?
a)
A steady, consistent upward trend
b)
A sharp upward trend as early as possible in the project
c)
A steady, consistent downward trend
d)
A sharp downward trend as early as possible in the project
8.
As the lead tester on an XP team, you discover a problem. What should you do?
a)
Discuss the issue with the developer.
b)
Try to fix the problem yourself
c)
Tell the customer.
d)
Alert the other coders to the problem.
9.
An agile team is refactoring their code. Why are they doing this?
a)
To check the unit tests for errors
b)
To make sure the tests are ready before the code is written
c)
To make the code easier to update and maintain
d)
To get a consistent level of technical debt that will make it easier to forecast velocity
10.
We put risk mitigation stories in the backlog to:
a)
Avoid having to keep a separate list of threats and issues.
b)
Keep the team focused on risks.
c)
Ensure that risk reduction efforts are done in the early iterations.
d)
Make sure the team doesn't forget to do something about the risks.
11.
Which scenario is an example of treating a change as coming from common causes of variation, when it actually comes from a special cause?
a)
Gathering the team to investigate why their last retrospective ran 15 minutes longer than the 2-hour tirnebox
b)
Sending a mass e-mail to stakeholders to remind them not to interrupt the team members during an iteration
c)
Asking the product owner to delay the release deadline next month because the team won't have finished all the release scope by then
d)
Assuring the sponsor that the team will finish the release on time next month based on their historical average velocity, even though the senior developer just broke her leg and will be out for six weeks
12.
As the team lead, you have been asked to explain to the business what the project team has accomplished during Iteration 0. Which of the following tools would you use for this presentation?
a)
Technical debt burnup chart
b)
Risk burndown graph
c)
Risk-adjusted backlog
d)
Average defects per release
13.
As the team's agile coach, you measure small amounts of variance in task durations. What should you do?
a)
Undertake root cause analysis to eliminate it.
b)
Engage the team in diagnosing the problem.
c)
Diagnose the issue as part of your leadership role.
d)
Accept some variance as inevitable.
14.
What is the advantage of using risk severity instead of expected monetary value (EMV) to rank risks?
a)
Risk severity helps us focus on the relative value of the risks.
b)
Risk severity is more accurate than EMV
c)
EMV is less realistic than risk severity.
d)
EMV can't be ranked on a simple scale (low, medium, high).
15.
What is one cause of technical debt?
a)
Trying to keep all the code perfectly neat and standardized
b)
Refactoring that hasn't been done on a regular basis
c)
Building a stripped-down minimal viable product
d)
Pair programming stress and burnout
16.
What is the agile approach to problem solving?
a)
Fix the problem after it arises, at the last responsible moment.
b)
To keep velocity consistent, only fix problems that are posing impediments to progress.
c)
When a problem arises, either fix it on the spot or add it to the backlog.
d)
Capture impediments, problems, and lessons learned daily in the stand-up meetings.
17.
As a team member, if you encounter a tricky problem during a development iteration, agile recommends that you:
a)
Stop what you're doing until you figure out a solution, using your individual expertise and ingenuity.
b)
Tell the ScrumMaster about the problem and let them decide what to do about it, since it's their job to remove impediments to progress.
c)
Just keep moving ahead so your velocity isn't disrupted, since most problems eventually take care of themselves.
d)
Quickly bring the problem to your team members and ask for their help in solving it, since many heads are better than one.
18.
Stories and features are prioritized in the risk-adjusted backlog based on their:
a)
Risk impact or risk probability
b)
Risk mitigation impact or user impact
c)
Expected monetary value or business value
d)
Cost-benefit ratio or customer value
19.
When a problem arises, what steps are needed?
a)
Remove the bad work and redo it; then look for other problems that might be related to that issue.
b)
Revise the plan since we have fallen behind.
c)
Diagnose the problem, decide what to do about it, and fix the problem (remove the bad work and redo it).
d)
Decide what to do and add the new work to the backlog.
20.
What is the least likely reason why changes found later in the project are more costly to fix?
a)
More rework might be needed to fix the problem.
b)
More stakeholders might be affected by the problem.
c)
More code might have to be refactored.
d)
More features might have to be supported.
100 %
![REVISION 4 : TOPIC 9 [ACCOUNTING FOR NON-CURRENT ASSETS]](https://cf.quizizz.com/image/image-loader.svg)
