5 things after Scrum (flies)
Scrum (stand-up meeting, rus .: letuchka) - a daily meeting for the project team.
(the translation is passed through the prism of my perception, although I disagree with something)
The first is “difficulties”. Anything that causes difficulty, interference, and prevents progress toward the goal should be studied and excluded after the volatility. Agile uses the "theory of restrictions" described by Eli Goldratt, in which the manager must remove any obstacles in the way of the team. The manager must make a TO-DO list of tasks after each fly.
The second is “deviation from the plan”. If you have planned 2 days for the task, and the 4th day has already gone and there is no end in sight, it’s worth starting to understand. If the fly is short today, then you can immediately try to understand why? Ask a question - what are the difficulties? But the best alternative would be to discuss right after the fly. You need to understand: is it a bad assessment, or a vicious problem, or a sign from above that you need help and is it worth connecting someone else? A single case is not a problem, it is isolated. The art of the master to see the dynamics, the frequency of the problem serves as a sign of the search for the underlying problem. Also, if the entire planned iteration miraculously ended in one day. Try to change the goals of the iteration, and maybe include testing, acceptance tests and focus on the delivery of the project a month earlier.
The third is “emotions.”Notice what has been said and has not been. Was anyone angry or upset. Was there a tension that would be nice to understand. Or maybe someone was below the water and below the grass? All these are tips to say a word after the flies. These are also difficulties for progress, as well as any obvious things (see paragraph 1). Sometimes you don’t even have to decide anything, the main thing is to listen, and the solution itself may come (and this sometimes allows the daredevils to write more code ... bugug!)
Fourth - “questions”. Perhaps you did not completely drive into questions and problems during the fly. If clarifying questions have brought more confusion than clarification, it’s the right way to talk after the fly (before when I was a developer, I quickly managed to get into all these technical problems, now I became a program manager and I need to chew on shelves; besides, I received a PMP certificate and I can show that now for me everything needs to be chewed m-e-d-e-n-o). We cannot fix what we do not understand. Many things in development grow out of technical problems, but when escalation and elimination is required (and this is my job) I must be in the know to find the best solution.
The fifth is “recognition.”Work ultimately turns into boring weeks, months, or projects. Look for ways to express recognition for the work done, significant events or the completion of the next step. We must support the motivation of people so that we all have enough strength to deal with difficulties. The best way to celebrate everyone’s progress and contribution. It can be just sincere thanks for what people did for the project, or maybe a nice lunch, and all sorts of trinkets. This should be the difference between a kamikaze team and just a good team.
Today it’s the 5 most, tomorrow they may be different.
Original: LeadingAnswers
(the translation is passed through the prism of my perception, although I disagree with something)
The first is “difficulties”. Anything that causes difficulty, interference, and prevents progress toward the goal should be studied and excluded after the volatility. Agile uses the "theory of restrictions" described by Eli Goldratt, in which the manager must remove any obstacles in the way of the team. The manager must make a TO-DO list of tasks after each fly.
The second is “deviation from the plan”. If you have planned 2 days for the task, and the 4th day has already gone and there is no end in sight, it’s worth starting to understand. If the fly is short today, then you can immediately try to understand why? Ask a question - what are the difficulties? But the best alternative would be to discuss right after the fly. You need to understand: is it a bad assessment, or a vicious problem, or a sign from above that you need help and is it worth connecting someone else? A single case is not a problem, it is isolated. The art of the master to see the dynamics, the frequency of the problem serves as a sign of the search for the underlying problem. Also, if the entire planned iteration miraculously ended in one day. Try to change the goals of the iteration, and maybe include testing, acceptance tests and focus on the delivery of the project a month earlier.
The third is “emotions.”Notice what has been said and has not been. Was anyone angry or upset. Was there a tension that would be nice to understand. Or maybe someone was below the water and below the grass? All these are tips to say a word after the flies. These are also difficulties for progress, as well as any obvious things (see paragraph 1). Sometimes you don’t even have to decide anything, the main thing is to listen, and the solution itself may come (and this sometimes allows the daredevils to write more code ... bugug!)
Fourth - “questions”. Perhaps you did not completely drive into questions and problems during the fly. If clarifying questions have brought more confusion than clarification, it’s the right way to talk after the fly (before when I was a developer, I quickly managed to get into all these technical problems, now I became a program manager and I need to chew on shelves; besides, I received a PMP certificate and I can show that now for me everything needs to be chewed m-e-d-e-n-o). We cannot fix what we do not understand. Many things in development grow out of technical problems, but when escalation and elimination is required (and this is my job) I must be in the know to find the best solution.
The fifth is “recognition.”Work ultimately turns into boring weeks, months, or projects. Look for ways to express recognition for the work done, significant events or the completion of the next step. We must support the motivation of people so that we all have enough strength to deal with difficulties. The best way to celebrate everyone’s progress and contribution. It can be just sincere thanks for what people did for the project, or maybe a nice lunch, and all sorts of trinkets. This should be the difference between a kamikaze team and just a good team.
Today it’s the 5 most, tomorrow they may be different.
Original: LeadingAnswers