You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the Daily Scrum, the Developers should be actively managing their work that is in progress. They should be discussing what they need to do next to be most effective at reaching the Sprint Goal.
32
+
The Daily Scrum is an essential event in the Scrum framework. It offers the
33
+
Developers an opportunity to reflect on their progress, and plan for the next 24
34
+
hours. But it's essential to approach it with the right mindset and intent.
There is no key way to do this, however, it is important to understand and look at the age of each of the work items that are currently in progress.
38
+
The primary objective of the Daily Scrum is not merely to go through a checklist
39
+
of questions. Instead, it's to actively manage ongoing work and strategize on
40
+
how best to achieve the Sprint Goal. This meeting is a platform for Developers
41
+
to discuss their work, challenges, and any impediments they might be facing. By
42
+
doing so, they can effectively strategize on their next steps and ensure that
43
+
they are on the right track.
24
44
25
-
[[_TOC_]]
45
+
### Beyond the Three Questions
26
46
27
-
#Overview of Flow for Daily Scrum
47
+
While the three standard questions—What did I do yesterday? What will I do
48
+
today? Are there any impediments in my way?—provide a structure, they shouldn't
49
+
become a monotonous routine. Developers should not feel compelled to answer
50
+
these questions robotically or feel the unnecessary pressure for everyone to
51
+
speak. The focus should be on meaningful conversation and collaboration.
28
52
29
-
This workshop leverages a simple flow and consists of the following:
53
+
### Beyond the Three Questions
30
54
31
-
The Developers review their progress towards the Sprint Goal. They should actively manage the work that is in progress and maintain transparency of the present as reflected in the Sprint Backlog.
55
+
Rather than discussing every item, the team should concentrate on elements in
56
+
the Sprint Backlog that require intervention or are at risk. By honing in on
57
+
these areas, the team can proactively address potential challenges and ensure
58
+
they remain on course.
32
59
33
-
_Although Scrum Masters can certainly facilitate the Daily Scrum, it should be the Developers that own this event and facilitate it.;_
60
+
### Emergent Practices
34
61
35
-
##Suggested Flow Steps
62
+
It's crucial to understand that there's no one-size-fits-all approach to the
63
+
Daily Scrum. What works for one team might not necessarily work for another.
64
+
Practices should emerge based on the team's unique needs, challenges, and
65
+
dynamics. Over time, as the team evolves and matures, so will their practices.
36
66
37
-
###Part 1: Review the Work in Process [~5 mins]
67
+
###Asking more interesting questions
38
68
39
-
The Developers should review the work that is currently underway and identify any problems, issues, or missing information that is required to get to the Sprint Goal.
69
+
The Daily Scrum is not just a routine check-in. It's an opportunity for the team
70
+
to come together, collaborate, and strategise. By focusing on the right areas
71
+
and fostering open communication, teams can remain aligned with the Sprint Goal
72
+
and continue delivering value. Remember, the method in which the team conducts
73
+
the Daily Scrum can vary, and what's presented here is just one of many ways!
-**Work Item Aging Graph** - A very effective way to review the work that is in progress is to use a Work Item Aging graph and to pay particular attention to the oldest items.
By actively managing the age of items the Developers can see clearly which items need the most focus, what is blocked, and how long they have been running.
46
-
-**Review the Boards** - Another key visualization is of the work currently in progress using a Board that shows the progress of the Value.
###Part 2: Create Actionable Plan for 24h [~10 min]
80
+
This recipe leverages a simple flow and consists of the following:
50
81
51
-
The outcome of the Daily Scrum should be an increase in the transparency of the work underway and this should be reflected in the Sprint Backlog. What is the plan for the next 24h and does the Sprint Backlog still represent the most important work to get to the Sprint Goal.
82
+
The Developers review their progress towards the Sprint Goal. They should
83
+
actively manage the work that is in progress and maintain transparency of the
84
+
present as reflected in the Sprint Backlog.
52
85
53
-
####Facilitation Options
86
+
*The Developers should own this event and facilitate it, although Scrum Masters
87
+
may certainly facilitate as requested or as needed.*
54
88
55
-
- Create a Plan [10 min]
89
+
### Why recipe?
56
90
57
-
# Some Common Anti-patterns
91
+
You follow a recipe a few times to build muscle memory and understand the
92
+
intended outcomes. Once learned one can tweak or change the recipe to adapt the
0 commit comments