Raising a flag early when any blocker is found is one of the tips to help the team to get things done smoothly without delays.
- Developer/Testing/Designer. etc ( owner of the task) faced a problem with the task example ( code problem, found missing requirement, dependency problem, task estimation changed due to unplanned bugs found or clean code or anything, etc )
- Developer tries to solve it until he/she misses the deadline
- No environment to show that he/she is blocked and asking for help not only the standup
- Build the habit of flagging the task early as you are facing a problem that may impact the delivery.
- Facilitate to him/her the space/channel/environment/ tools where he/she can find support and good communication with others
- Always remind the team by raising the flag early and putting it in the team ground rules.
- Teach them how they can raise a flag in the tool so it can be trackable and obvious on the team board so anyone in the team can jump to help.
- Raise a flag to the product owner or product manager that we have a problem in this specific Task/Story so he can prioritize the delivery or communicate to the business team or stakeholder with the updates.
- Delays in the Task/Story delivery that lead to sprint delays
- Other bugs may raise due to he/she forgetting to say that this task may impact other feature codes.
- No environment to show the flag let the team forget about the delay and no follow-up to support or facilitate.
- Always Remind the team in the standup and ask if they have any blockers
- Always remind the team in the standup to Flag his/her task in the used tool ( ex: jira) so any one of the team can jump to help, and have a good history to inspect and adapt.
- We can Run a small simple script using the Jira automation rule, so it can send a scheduled reminder for the team by the flagged tasks/stories, so we can all follow up on them.
Here we use slack as a communication tool and Jira for Tasks/Stories
