New tool for the team in middle of the program
We have several program iterations(PI) in the year, and each PI is divided into 5 sprints. In one of the PIs the management decided to introduce a new tool in the last sprint. The Product Owner and Scrum master were informed of this only 2 days before the last sprint was to start. The tool was launched earlier too but since it was not mature, the teams ended up wasting time spent trying to use the tool. We are told that successful implementation of the tool will lead to less errors and issues with the delivered software, but the last two times the team has dipped its hands into it has lead to nothing but disaster(in terms of loosing valuable dev days with the existing tools). How does should a PO or SM deal with the is situation? We are open to tools and processes that will improve our software, but its difficult to plan for the plan and re-plan with these new management decisions.
The Scrum Guide says:
"The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t."
...
"The Scrum Master serves the organization in several ways, including:
- Leading and coaching the organization in its Scrum adoption"
From your reading of the Scrum Guide, do you think it was appropriate for management to make the tooling decision you describe, and do you see a possible coaching opportunity?
Hello Abhi,
It is scrum master's responsibility to make management understand that introducing new tool in the middle of the sprint would decrease the productivity of the dev team. Lets say if management wants to make any changes in the development team or their way of working that should be planned well otherwise it will endanger the sprint goal.
Your scrum master can arrange some technical sessions (1-2) in on going sprint and if team feels comfortable with the tool then they can start using in upcoming sprint. This way team will be familiar with the tool and productivity won't decrease.
Reading about PI, I'm afraid Abhi is in a SAFe world, in with the Scrum Master and PO roles are not the one of the Scrum Guide