Agreed, without vision, those at the team level that may be looking up would likely be confused hence why set a sprint goal from the bottom? However the problem I’ve seen over the years in addition to those visionaries that don’t have one or can’t set a goal, is that the team is working on so many things such as one team mate supporting app x, another app y, three others on production support, so spread out working in their own box you’d seriously question why they are even a Scrum Team. So how do write that one goal these inside the box players can rally around and serve as the compass for the Daily Scrum? It’s a tough one for sure and I’m pretty close to giving up on it.
There's also a anti-pattern where you do the planning, and THEN set the goals. and when you do that, the goals are nothing more than a summary of the sprint items, and this isnt really what a "goal" should be! So at least set your goals at the *start* of planning
👍🏻 Like it! 💫
Agreed, without vision, those at the team level that may be looking up would likely be confused hence why set a sprint goal from the bottom? However the problem I’ve seen over the years in addition to those visionaries that don’t have one or can’t set a goal, is that the team is working on so many things such as one team mate supporting app x, another app y, three others on production support, so spread out working in their own box you’d seriously question why they are even a Scrum Team. So how do write that one goal these inside the box players can rally around and serve as the compass for the Daily Scrum? It’s a tough one for sure and I’m pretty close to giving up on it.
There's also a anti-pattern where you do the planning, and THEN set the goals. and when you do that, the goals are nothing more than a summary of the sprint items, and this isnt really what a "goal" should be!
So at least set your goals at the *start* of planning