Optimizing DSUs for Scrum Teams Following Scaled Agile Framework(SAFe)

I hear a lot about what the team should do in Daily Stand-Up (DSU) and the so-called best practices around it. I have been to scrum for quite some time before I adopted the Scaled Agile Framework(SAFe). In this article, I would like to talk about the DSU and how the development team can use the DSUs for their success with Iteration execution following SAFe

The DSUs are an integral part of the scrum events for teams the following scrum while executing their iterations in SAFe. Some kanban team practices DSU too but for this article, I will focus on the teams the following scrum as part of their iteration planning. Let's look at the intent behind DSUs.

1. Enabling face to face communication (Virtual for distributed teams) on a daily basis
2. Forecasting any risk/impediments that might derail the Team`s iteration goal
3. Forecasting any risk/impediments that might derail the Team`s Pi Planning commitment
4. Promoting everyday collaboration, transparency, and planning

While working with SAFe teams I encountered various development teams practicing DSUs in many unproductive ways. While some teams were practicing the unproductive DSUs because they were naïve with their agile transformation journey, many teams were practicing those unproductive DSUs because of their organizational structure. The unproductive or less productive (Modest way of saying :)) DSUs will exhibit the below characteristics.

1. Team members using the DSU as status reporting. Teams who are in their early stage of SAFe transformation journey usually exhibit this behavior
2. Team members limit themselves to the most misunderstood 3 lines- (1. What I completed/did yesterday 2. What am planning to do today. 3. Any impediments) without understanding the real intent/meanings behind them
3. SM and PO asking team members name and their status
4. Team members are just interested in their status and not utilizing the rest of the DSU time
5. Team members indulging in deep 1to 1 technical discussion exceeding the 15 minutes time window
6. Irregular DSUs and Irregular Team members

Now the question is who can help and how? Before you say of course Scrum Master as teams are not matured enough so they have such DSUs, I would then say how? The Scrum master alone can not turn these DSUs to productive DSUs. The Teams needs to understand Why part of the issue and work with Scrum Master.

I would share my experiments as SM while stuck with such DSUs.

1. Set ground rules for DOs and Don'ts of DSU
2. Organize interactive workshop/s on the DSUs and let the team members brainstorm or design an agile game simulating around DSU
3. Use DSU as an event designed for every 24-hour planning cycle
4. Run the DSU in front of the Jira board and PI planning board. I have used the Jira board for showing up the Iteration backlog and the Iobeya board for PI plan/objectives. This helps the team to focus and be involved as a team
5. Request team members for Facilitating DSUs and SM observing the team dynamics
6. Coach team members on bringing transparency in DSU and raising an early alarm for helping hand
7. Coach team members to have parking lot discussion wherever there is a 1x1 discussion need or a technical deep dive with few members required. Just hint that during DSU.
8. For silent DSUs find the reasons and deal with them. I have so far found reasons like team members with introverted personalities, environmental issues ( danger of rejection/insecurity), Low team morale, organizational culture (Answer only when manager ask questions), Organizational structure around SAFe ( Line manager doing PO/SM roles). I have dealt with each of these reasons by applying various strategies
9. Have an option to adjust Iteration Plan and PI plan based on the DSU… Bottom-up approach

I was successful in turning the DSUs into productive ones and of course teams helped in this journey. I tried to share my experience here, let me know how your DSUs are? What did you do to make your DSUs fit for the purpose? I would love to hear them.