Don’t fight but work together<\/strong><\/strong><\/h3>\n\nIn the Netherlands, that wind is just part of it. But instead of fighting wind gusts solo, it’s much easier to work together in a group. So I cycle the same lap of the dike with my friends. This time it won’t be a tussle, but nimble reactions to each other. We adjust positions. Keep each other out of the wind. Divide the heaviest work with short head turns. Does the wind turn? Then we adjust our routine again with lightning speed. Soon we find a wonderful rhythm even in that headwind, we maintain perfect speed. The euphoria is back! <\/p>\n\n
The 3 practical tips<\/strong><\/strong><\/h3>\n\nYou will recognize this: even in (Scrum) teams it often blows. Some teams always seem to have the wind at their backs, flying successfully through their work. But in your team: rock-hard wind against. Why is that? And more importantly; what can you do about it? <\/p>\n\n
\n- Set your direction and don’t blow with all the winds<\/li>\n\n\n\n
- Accept the wind force and organize according to it<\/li>\n\n\n\n
- Break the wind by really doing it together<\/li>\n<\/ul>\n\n
![\"Agile](\"https:\/\/scrumacademy.nl\/wp-content\/uploads\/2023\/08\/Scrum-Academy-camp2023-banner-600x150-150dpi-Stije-1-1024x256.png\")
<\/figure>\n\nDetermine your direction<\/strong><\/strong><\/h3>\n\nIn your Agile or Scrum Team, you (I hope) pursue the same goal together. A goal to which everyone contributes, from his or her expertise. You have set a very clear dot on the horizon together. Long term, in other words. Think of it as the finish line of your bike ride. But to get there, you need short-term actions to get closer to that goal. What turn do you take, who will lead, what gear? In summary, your Product Vision should be clear and with your Sprint goal you are getting closer and closer in concrete terms. <\/p>\n\n
Accept the wind force<\/strong><\/strong><\/strong><\/h3>\n\nYou have set the direction. Good job. But then suddenly there is an unexpected gust of wind, force ten. As a cycling team and as a Scrum team, you don’t want to be blown over even then. This is where the Daily Scrum is valuable. During the Daily you quickly adapt to the latest insights. What has come our way that we are suffering or benefiting from? Where do we need to adjust our direction or not? And in the Retrospective you then look back and dwell on it a bit longer. Then to accelerate again, of course. If these are new terms for you, then the Agile Kickstart for teams <\/a>might be for you. <\/p>\n\nBreak the wind<\/strong><\/strong><\/strong><\/h3>\n\nAs I said, Agile and Scrum require teamwork. The saying “alone you go faster, but together you get further” really doesn’t apply here. I like to change it to: Together you go faster and further. Alone you fight the wind. Together you find the wind at your back. Yet it is not always easy to work together in a sincere way. Why is that? I’ll give you a few examples. <\/p>\n\n![\"Agile](\"https:\/\/scrumacademy.nl\/wp-content\/uploads\/2022\/09\/Agile-Leaderschapstrainingen-1024x256.jpeg\")
<\/figure>\n\nAlternating Product Owners<\/strong><\/strong><\/strong><\/h3>\n\nI often see the lack of clear direction created by too many changes in the Product Owner role. Some teams even lack the Product Owner completely. Lack of leadership also results in blowing with all the winds. As a team, you don’t even immediately experience this as a headwind; perhaps it even feels like freedom for a while. But over time, motivation sinks, islands form and noise appears on the line. You may even feel frustration, as customers and stakeholders become less and less satisfied. The team’s right to exist thus becomes unclear. <\/p>\n\n
So you see that reflected in the team<\/strong><\/strong><\/strong><\/h3>\n\nHow do you see the above reflected concretely in your team? The team has become a group of individuals. Colleagues prefer to avoid cooperation. Everyone focuses on individual tasks and prefers to have them handed to them on a silver platter. Even in meetings, there is little enthusiasm; colleagues are frustrated about everything, but no longer see what they can do to change it. Before one project is finished, they jump on to the next. All in all, the team becomes nonchalant and erratic. <\/p>\n\n
Time to do something about that<\/strong><\/strong><\/strong><\/strong><\/h3>\n\nNow how to turn that headwind into tailwind? We’ve already talked about it: set direction, accept the wind force and break the wind. First, that means setting direction with long-term goals for the team. Work out with each other when you will be successful and how you will measure that. Then, with an “inspect and adapt” mindset, you can move forward with your customers and stakeholders. Once the basics(check Agile and Scrum Essentials<\/a>) are in place, you can start building as a team and getting better and better. And this I promise you: that progression feels like wind at your back. Want to talk to me personally<\/a> about this? Contact me<\/a>. <\/p>\n\n
You will recognize this: even in (Scrum) teams it often blows. Some teams always seem to have the wind at their backs, flying successfully through their work. But in your team: rock-hard wind against. Why is that? And more importantly; what can you do about it? <\/p>\n\n
- \n
- Set your direction and don’t blow with all the winds<\/li>\n\n\n\n
- Accept the wind force and organize according to it<\/li>\n\n\n\n
- Break the wind by really doing it together<\/li>\n<\/ul>\n\n<\/figure>\n\n
Determine your direction<\/strong><\/strong><\/h3>\n\n
In your Agile or Scrum Team, you (I hope) pursue the same goal together. A goal to which everyone contributes, from his or her expertise. You have set a very clear dot on the horizon together. Long term, in other words. Think of it as the finish line of your bike ride. But to get there, you need short-term actions to get closer to that goal. What turn do you take, who will lead, what gear? In summary, your Product Vision should be clear and with your Sprint goal you are getting closer and closer in concrete terms. <\/p>\n\n
Accept the wind force<\/strong><\/strong><\/strong><\/h3>\n\n
You have set the direction. Good job. But then suddenly there is an unexpected gust of wind, force ten. As a cycling team and as a Scrum team, you don’t want to be blown over even then. This is where the Daily Scrum is valuable. During the Daily you quickly adapt to the latest insights. What has come our way that we are suffering or benefiting from? Where do we need to adjust our direction or not? And in the Retrospective you then look back and dwell on it a bit longer. Then to accelerate again, of course. If these are new terms for you, then the Agile Kickstart for teams <\/a>might be for you. <\/p>\n\n
Break the wind<\/strong><\/strong><\/strong><\/h3>\n\n
As I said, Agile and Scrum require teamwork. The saying “alone you go faster, but together you get further” really doesn’t apply here. I like to change it to: Together you go faster and further. Alone you fight the wind. Together you find the wind at your back. Yet it is not always easy to work together in a sincere way. Why is that? I’ll give you a few examples. <\/p>\n\n
<\/figure>\n\nAlternating Product Owners<\/strong><\/strong><\/strong><\/h3>\n\n
I often see the lack of clear direction created by too many changes in the Product Owner role. Some teams even lack the Product Owner completely. Lack of leadership also results in blowing with all the winds. As a team, you don’t even immediately experience this as a headwind; perhaps it even feels like freedom for a while. But over time, motivation sinks, islands form and noise appears on the line. You may even feel frustration, as customers and stakeholders become less and less satisfied. The team’s right to exist thus becomes unclear. <\/p>\n\n
So you see that reflected in the team<\/strong><\/strong><\/strong><\/h3>\n\n
How do you see the above reflected concretely in your team? The team has become a group of individuals. Colleagues prefer to avoid cooperation. Everyone focuses on individual tasks and prefers to have them handed to them on a silver platter. Even in meetings, there is little enthusiasm; colleagues are frustrated about everything, but no longer see what they can do to change it. Before one project is finished, they jump on to the next. All in all, the team becomes nonchalant and erratic. <\/p>\n\n
Time to do something about that<\/strong><\/strong><\/strong><\/strong><\/h3>\n\n
Now how to turn that headwind into tailwind? We’ve already talked about it: set direction, accept the wind force and break the wind. First, that means setting direction with long-term goals for the team. Work out with each other when you will be successful and how you will measure that. Then, with an “inspect and adapt” mindset, you can move forward with your customers and stakeholders. Once the basics(check Agile and Scrum Essentials<\/a>) are in place, you can start building as a team and getting better and better. And this I promise you: that progression feels like wind at your back. Want to talk to me personally<\/a> about this? Contact me<\/a>. <\/p>\n\n