There are two key reasons a Scrum Master may run a futurespective. The first is to kick start a new project, and the second is to restart an existing one.
A futurespective gives a team a chance to create and grow the connections that are important for team health. They are an opportunity to team build: the perfect time to explore your team’s motivations and fears, and share how members have worked well in the past. This presents a Scrum Master with –
- valuable insight into how they can best support their team, and
- the chance to start important conversations such as dealing with unpredictability.
Additionally, they help the team build a vision and purpose. It’s no surprise then that futurespectives are a wonderful way to align newly formed teams or check the calibration of established ones.
When it comes to the project, a futurespective is a brilliant planning mechanism. They can be used to identify things such as –
- areas of concern or perceived risks
- resources and tools needed
- gaps in the team.
This means shaping solutions to address such hurdles can start sooner than later.
A futurespective can also be used to set the tone for a project. This is why Scrum Masters can also us the futurespective to –
Importantly, futurespectives ensure that at the start of the project, all team members are on the same page.
Futurespectives are also a great way to restart a stalled or stuck project. They can help reenergize an unmotivated team, shake up the repetition of retrospectives, and help a team revisit their goals.