Back to Forum

Unplanned Task

Last post 03:10 pm May 17, 2016 by Pedro Golino
3 replies
Pedro Golino
02:37 pm May 16, 2016

Hello everyone,

My team is adopting SCRUM for Production Maintenance in a company that has no culture of agile.

Our process was adapted and we are in a continuous evolution process because of this adaptation.

We are having a problem on every sprint with new unplanned tasks.

How to deal with this?
How to measure this new tasks?
Does the sprint have to be replanned?
How to score the new tasks at the end of sprint?

Thanks

Ranjith Kumar Kilari
02:49 pm May 16, 2016

What were the motivations behind using Scrum for production maintenance? Did the team consider Kanban which may be more suitable to manage production requests?

Regards

Pedro Golino
03:24 pm May 16, 2016

The motivations were: Agility and visibility.
The Kanban was adapted according to our process.

Pedro Golino
03:10 pm May 17, 2016

Dears,
I notice that cases of Scrum at Production Maintenance are not usual.

Do you have sugestions?

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.