Skip to main content

New tool for the team in middle of the program

Last post 02:03 pm September 26, 2018 by Olivier Ledru
3 replies
01:05 pm September 24, 2018

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.


12:27 pm September 25, 2018

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?


11:25 am September 26, 2018

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. 


02:03 pm September 26, 2018

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


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.