Visual board stand-up

The daily stand-up is when the team, product managers, managers and other groups meet to learn the story and share findings. This is best accomplished on front of the visual board.

Aspects of a good stand-up, apart from number of people attending can be summarized as follows.

Coloring of various project areas, for example risks, defects, urgent tasks, delays, class of service and others can help in knowing what happening and to take appropriate actions. It reminds everyone on the previous areas and therefore coloring helps the team to focus on mitigating their impact. For example, once I see red dot on a  card I know it should  implement certain policies to facilitate flow of value.

Keep the visual board manual allows face-to-face communication among team members and other related stakeholders. The manual board doesn’t require tool evaluation, purchase, training of staffs, and others. For me a big benefit is avoiding shifting the staff mind-set from being tool driven to more process oriented. Any tool has its own philosophies and ideas that should be grasped in order to use it. This takes time and can distract team from implementing Lean/ Kanban methods.

Should be less than 15 minutes covering mainly the situation of various cards and examining the flow. Having coloring system in place helps to notice the various areas which require actions and follow-up.

Should avoid problem solving as the meeting can highlight many concerns which can be followed-up after the meeting.

Attendees should no feel as if they are being interrogated. Instead they should focus on having flow of value and accordingly contribute.

Questioning of our understanding is a key benefit from my view when visualizing the flow during the stand-up. For example, the complain in one project was that we didn’t have enough developers to address the backlog. After visualizing the Value Stream and doing stand-ups for a month or so we found that the problem turned to become we don’t have enough work to give to the developers. Many of the cards represent requirements which needed more elaboration by the product owner and should not really be part of the team current activities.

Having people identity on their cards promotes ownership and should not be associated with personal attribution. Team members would report issues related to their work and once there is delay they can accept other work. The flow is enabled by avoiding having them waiting, meanwhile we pro-actively escalate to resolve the issue.

Facilitate apart from seniority from who is attending the stand-up. This originates collaborative problem solving among the cross functional team members with minimal level of escalation.

Invite other groups to attend the stand-up although they are not part of the project.  I asked our quality director to attend, his feedback was that he learned about the team which improved collaboration  and increased the alignment with the organization.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s