THE GROUP DIDN’T DEVOTE TO THE SCHEDULE

Note: please go to the Part 1 short article here to get the context.

Very first thing initially, let’s double-check are all employee familiar with the schedule? And are all employee have accepted the schedule?.

If the response is no, you understand what you should do, right?

1. Make an agreement
2. Make the agreement specific (i obtain Kanban practices here, make policies specific)

If the response is yes, it’s time to make a routine reflection.

1. What makes it hard to follow the agreement/schedule

Please keep in mind that you need to put your compassion above whatever when performing the session. Do not put any judgment on your staff member. Make the session safe for them to highlight their problems.

I think the method you resolve it needs to be customized based upon the case shared by the group. On the other hand, I hope these misconceptions of everyday scrum didn’t come to the response:

The schedule is prematurely (early morning), so I can’t overtake the schedule.

Response: Nobody stated that our everyday scrum needs to be performed in the early morning. Even the Scrum guide does not state so. Despite the fact that there’s some advantage if we do it in the morning, that does not suggest we need to. Daily scrum will just benefit if everybody can add to the issue resolution and understand the changed shipment method.

I dislike to stand just for the conference.

Response: Nobody stated that our everyday scrum needs to be performed in a stand-up position. Even the Scrum guide does not state so. You can do it in sit-down, while having a push-up, sit-up, or in any body position that makes you comfy.

The occasion does not make any sense since we constantly sync each time.

Response: Wow, it would be even much better! Our company believe a few of us do not have that high-end. It might be since some employee are not operating at the very same area as the others, the kind of work has a substantial danger from context changing, and so on. The everyday scrum is simply how the Scrum structure assists us develop the practice. Once it’s developed, we will feel it as the method of working, not a conference. It ends up being the requirement rather of the events.

I have a lot of conferences currently, just 15 minutes, and I need to sign up with offline? It does not make any sense.

Response: Daily scrum does not require offline involvement rather of active involvement. It suggests we can do asynchronous interaction (such as chat or email) or concurrent interaction (such as call) to share the issue, talk about the analytical, and do action products generation.

Please describe my Part 1 short article to learn the vital things to be shared throughout the everyday scrum.

This is completion of Part 2. Do not hesitate to put any remarks or feedback concerning this short article. See you in Part 3!