Scrum tools for projects having repetitive tasks

Last post 07:47 pm September 13, 2018
by Bidyut Bikash Das
3 replies
Author
Messages
12:02 pm September 9, 2018

We are going to adopt scrum for a team which is performing the below activities as part of a project.Could anyone suggests some free scrum tools which can help us
in implementing the scrum framework.

Is it advisable to use scrum in projects like the below one ?

1. Build KPIs reflecting system performance.
2. Monitor Productionized KPIs.
3. Analyze and report trends and take corrective action.
4. Implement process improvements which can enhance system performance.

Thanks.

12:12 am September 10, 2018

Hey Bidyut!

I was in a similar pickle some time ago - where management wanted to implement Scrum, but since the project falls in an operational/continuous improvements area, we took a decision to go ahead with Lean/Kanban approach.

Scrum can be implemented - not that it is not possible - but the fundamental question is: is it really necessary, and will it help the team deliver better and faster?

Looking forward to hearing on your approach and experience.

Cheers!

Adwait Vaidya.

04:48 am September 10, 2018

Could anyone suggests some free scrum tools which can help us
in implementing the scrum framework.

The Scrum Guide. I’d recommend putting a clear focus on that to begin with.

Is it advisable to use scrum in projects like the below one ?

1. Build KPIs reflecting system performance.
2. Monitor Productionized KPIs.
3. Analyze and report trends and take corrective action.
4. Implement process improvements which can enhance system performance.

A project is a temporary endeavor. Perhaps the activities you have cited are more likely to be ongoing ones, and represent certain tools and techniques for implementing Scrum which a team may use.

07:47 pm September 13, 2018

Thanks Adwait & Ian for your inputs. 

Apartfrom my above mentioned tasks we do need to deliver new functional & technical KPIs after every two weeks. The various dimensions of these KPIs are not known when we start building them and normally evolves after multiple discussions and feedback from the customer. Hence we have started to follow the below approach..

1. We have got the permission to use JIRA tool which is already there at the enterprise level.

2. We have considered the KPI requirements as our backlog items.Depending upon the priority we will deliver 2/3 KPIs per sprint(2 weeks duration)

3. We are keeping one generalized backlog item as "Repetitive Task" which will contain all required activities under its sub-task. We know that this isn't the right approach, but to keep things simple at the beginning we will follow this approach for first few sprints. This generalized item will be present in all sprints with item name as "RT_sprint#"

4. Add other development tasks and adhoc activities as low priority backlog items.

 

Thank you.