問題一覧
1
Immediately after the conclusion of the previous Sprint.
2
Managers are not required at the Daily Scrum.
3
Scrum is based on empiricism and lean thinking., Scrum is a framework for developing and sustaining complex products., Each component of Scrum serves a specific purpose and is essential to Scrum's success and your usage of Scrum to develop complex products.
4
How much of the functionality of the product is being used., Direct customer feedback., How quickly or easily the product can be absorbed and used by its customers.
5
The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.
6
The competencies and skills needed to deliver an Increment in a Sprint.
7
At the end of each Sprint.
8
False
9
15 minutes.
10
False
11
Tools and techniques.
12
The Developers.
13
4 hours for a one-month Sprint.
14
They will improve their Definition of Done to include more stringent criteria.
15
Turn Product Backlog items into a valuable, useful Increment.
16
False
17
The Product Backlog is continually kept up to date with the most recent insights.
18
No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.
19
All of the above.
20
As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.
21
The benefit of Developers figuring out a solution for themselves., The ability of the Scrum Teams to produce integrated Increments.
22
When the Sprint Goal becomes obsolete.
23
There is no such thing as Sprint 0.
24
The Sprint length is unchanged and the Scrum Team continuously learns and adapts.
25
Sprint Backlog.
26
Allow the Developers to self-manage and determine for themselves what to do.
27
The Developers.
28
Value of Product Backlog items., Dependencies between Product Backlog items., Dependencies to other products.
29
The Developers after clarifying requirements with the Product Owner.
30
True
31
To inspect the product Increment with the stakeholders and collect feedback on next steps.
32
Collaborate with the Product Owner to determine what is possible and acceptable.
33
At the end of every Sprint.
34
False
35
Coach the team on why the Daily Scrum is important as an opportunity to update the plan., Learn why the Developers want this and work with them to improve the outcome of the Daily Scrum.
36
Yes, they all belong on the Product Backlog. The Product Backlog is supposed to be the "single source of truth" for all the work for the product.
37
False
38
The Scrum Team during the current Sprint, if they have been unable during preceding Sprints to define Product Backlog items with enough precision to begin work., The Scrum Team on an ongoing basis, defining Product Backlog items into smaller more precise items that are ready for selection.
39
Existing teams propose how they would like to go about organizing into the new structure., Bring all the people together and let them organize into Scrum Teams.
40
Any of the above (or others) which are a decomposition of the selected Product Backlog items.
41
True. Outcomes are affected by their participation and availability.
42
All Sprints must be one month or less.
43
The Developers are more focused with a common yet specific goal.
44
Each Scrum Team is accountable for developing functionality from beginning to end.
45
By facilitating Scrum Team decisions., By removing impediments that hinder the Scrum Team.
46
True
47
When the Product Owner is actively working on items on the Sprint Backlog; however, they participate as a Developer.
48
Do not include the item in the Increment this Sprint., Put it on the Product Backlog for the Product Owner to decide what to do with it.
49
Scrum Master., Product Owner., Developers.
50
The Scrum Team may add the items to the Sprint Backlog for the next Sprint.
51
When multiple Scrum Teams are working together on a product, they must mutually define and comply with the same Definition of Done.
52
False
53
Remove items from the Product Backlog that have not been addressed in a long time., Only fully describe Product Backlog items when it seems likely they will be implemented.
54
False
55
False
56
The Product Owner.
57
Illustrate that as a project forecast lengthens, it is increasingly less certain.
58
The Developers.
59
It is allowed to grow and change as more is learned about the product and its customers.
60
The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint.
61
Immediately after the first Sprint.
62
It is the Developers plan for the Sprint.
63
True
64
Bring all the people together and let them organize into Scrum Teams., Existing teams propose how they would like to go about organizing into the new structure.
65
All answers apply.
66
Identification of impediments that may prevent the Developers from achieving the Sprint Goal., A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal.
67
Collaborating with stakeholders, users, and customers., Working with the Scrum Team on Product Backlog refinement.
68
During Sprint Planning.
69
Remove or change selected Product Backlog items., The Developers ensure that the Scrum Team is aware, start the Sprint, and monitor progress.
70
When the item meets the Definition of Done.
71
The value of the Product Backlog items., Dependencies between Product Backlog items., Their relevance to achieving the Product Goal.
72
True
73
Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access., Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint.
74
8 hours for a one-month Sprint.
75
The Product Backlog is ordered., The Product Backlog is available to all stakeholders.
問題一覧
1
Immediately after the conclusion of the previous Sprint.
2
Managers are not required at the Daily Scrum.
3
Scrum is based on empiricism and lean thinking., Scrum is a framework for developing and sustaining complex products., Each component of Scrum serves a specific purpose and is essential to Scrum's success and your usage of Scrum to develop complex products.
4
How much of the functionality of the product is being used., Direct customer feedback., How quickly or easily the product can be absorbed and used by its customers.
5
The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.
6
The competencies and skills needed to deliver an Increment in a Sprint.
7
At the end of each Sprint.
8
False
9
15 minutes.
10
False
11
Tools and techniques.
12
The Developers.
13
4 hours for a one-month Sprint.
14
They will improve their Definition of Done to include more stringent criteria.
15
Turn Product Backlog items into a valuable, useful Increment.
16
False
17
The Product Backlog is continually kept up to date with the most recent insights.
18
No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.
19
All of the above.
20
As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.
21
The benefit of Developers figuring out a solution for themselves., The ability of the Scrum Teams to produce integrated Increments.
22
When the Sprint Goal becomes obsolete.
23
There is no such thing as Sprint 0.
24
The Sprint length is unchanged and the Scrum Team continuously learns and adapts.
25
Sprint Backlog.
26
Allow the Developers to self-manage and determine for themselves what to do.
27
The Developers.
28
Value of Product Backlog items., Dependencies between Product Backlog items., Dependencies to other products.
29
The Developers after clarifying requirements with the Product Owner.
30
True
31
To inspect the product Increment with the stakeholders and collect feedback on next steps.
32
Collaborate with the Product Owner to determine what is possible and acceptable.
33
At the end of every Sprint.
34
False
35
Coach the team on why the Daily Scrum is important as an opportunity to update the plan., Learn why the Developers want this and work with them to improve the outcome of the Daily Scrum.
36
Yes, they all belong on the Product Backlog. The Product Backlog is supposed to be the "single source of truth" for all the work for the product.
37
False
38
The Scrum Team during the current Sprint, if they have been unable during preceding Sprints to define Product Backlog items with enough precision to begin work., The Scrum Team on an ongoing basis, defining Product Backlog items into smaller more precise items that are ready for selection.
39
Existing teams propose how they would like to go about organizing into the new structure., Bring all the people together and let them organize into Scrum Teams.
40
Any of the above (or others) which are a decomposition of the selected Product Backlog items.
41
True. Outcomes are affected by their participation and availability.
42
All Sprints must be one month or less.
43
The Developers are more focused with a common yet specific goal.
44
Each Scrum Team is accountable for developing functionality from beginning to end.
45
By facilitating Scrum Team decisions., By removing impediments that hinder the Scrum Team.
46
True
47
When the Product Owner is actively working on items on the Sprint Backlog; however, they participate as a Developer.
48
Do not include the item in the Increment this Sprint., Put it on the Product Backlog for the Product Owner to decide what to do with it.
49
Scrum Master., Product Owner., Developers.
50
The Scrum Team may add the items to the Sprint Backlog for the next Sprint.
51
When multiple Scrum Teams are working together on a product, they must mutually define and comply with the same Definition of Done.
52
False
53
Remove items from the Product Backlog that have not been addressed in a long time., Only fully describe Product Backlog items when it seems likely they will be implemented.
54
False
55
False
56
The Product Owner.
57
Illustrate that as a project forecast lengthens, it is increasingly less certain.
58
The Developers.
59
It is allowed to grow and change as more is learned about the product and its customers.
60
The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint.
61
Immediately after the first Sprint.
62
It is the Developers plan for the Sprint.
63
True
64
Bring all the people together and let them organize into Scrum Teams., Existing teams propose how they would like to go about organizing into the new structure.
65
All answers apply.
66
Identification of impediments that may prevent the Developers from achieving the Sprint Goal., A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal.
67
Collaborating with stakeholders, users, and customers., Working with the Scrum Team on Product Backlog refinement.
68
During Sprint Planning.
69
Remove or change selected Product Backlog items., The Developers ensure that the Scrum Team is aware, start the Sprint, and monitor progress.
70
When the item meets the Definition of Done.
71
The value of the Product Backlog items., Dependencies between Product Backlog items., Their relevance to achieving the Product Goal.
72
True
73
Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access., Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint.
74
8 hours for a one-month Sprint.
75
The Product Backlog is ordered., The Product Backlog is available to all stakeholders.