Sujith SalianProject Manager | LTI MindtreeNavi Mumbai, Mh, India
How can we implement an Agile way of working for projects where team work on resolving incidents. We usually get incidents for Bug fixes, user access , report access etc. Our client has started to adopt Agile in a big way across the organization and wants it implemented in our project too. Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Lean and Agile are different things. With that said, in this type of projects or environments using a Lean based approach works well. For example, Kanban system (not the board only). By using Kanban system you will be able to optimize the flow and to get a time to market according to client expectations, just in case you measure time to market.
...
2 replies by Sujith Salian and pamela bidear
Jan 17, 2024 5:44 AM
Sujith Salian
...
Thanks Sergio Luis Conte. We have been using the Kanban Board for managing the flow of incidents and it has worked well till date. However, it seems that for our model of delivery, agile might not be the right fit . Your opinion please
Jan 18, 2024 8:07 PM
pamela bidear
...
Hello Sujith
Great question, yes we can, and the agile approach to use for ongoing bugs while the project is ongoing as well or finished will be Kanban because it will be a continuous workflow and incidents will be addressed as they come in.
Saving Changes...
Sujith SalianProject Manager | LTI MindtreeNavi Mumbai, Mh, India
Jan 17, 2024 5:35 AM
Replying to Sergio Luis Conte
...
Lean and Agile are different things. With that said, in this type of projects or environments using a Lean based approach works well. For example, Kanban system (not the board only). By using Kanban system you will be able to optimize the flow and to get a time to market according to client expectations, just in case you measure time to market.
Thanks Sergio Luis Conte. We have been using the Kanban Board for managing the flow of incidents and it has worked well till date. However, it seems that for our model of delivery, agile might not be the right fit . Your opinion please
...
1 reply by Sergio Luis Conte
Jan 17, 2024 5:49 AM
Sergio Luis Conte
...
Just to comment: is not about to use Kanban Board only. It is about to use the whole Kanban System. For example, defining WIP limits, measure flow, change the way of working to a pull system instead of push, etc. I am writting this without knowing about your process.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Jan 17, 2024 5:44 AM
Replying to Sujith Salian
...
Thanks Sergio Luis Conte. We have been using the Kanban Board for managing the flow of incidents and it has worked well till date. However, it seems that for our model of delivery, agile might not be the right fit . Your opinion please
Just to comment: is not about to use Kanban Board only. It is about to use the whole Kanban System. For example, defining WIP limits, measure flow, change the way of working to a pull system instead of push, etc. I am writting this without knowing about your process. Saving Changes...
Service requests are a good fit for a Kanban-based delivery approach, but as Sergio has indicated, you do need to adopt the overall philosophy of the Kanban system such as limiting work in progress, empowering front line workers and so on.
Do you have a large backlog of service requests? Are they handled FIFO or do they get prioritized? Hopefully those making the decision understand that ServiceDesk is part of the PRODUCT lifecycle more than is is part of a project, and aren't just "going agile" because it's supposed to make everything better.
That said, I agree with Sergio and Kiron that Kanban CAN work well in your situation. Does your ticketing system have a Kanban board feature? Can your team establish and work within WIP (work in Progress) limits?
What are the client's expectations? Are they working in Sprints? Do they expect you to, as well? Will this affect any SLAs you may have for fixing issues? Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Sujith, I do completely agree with my fellow colleagues with regards to the Kanban. You also might want to take a look at your Value Stream and see where you can do some improvements to boost efficiency. Saving Changes...
pamela bidearField Cordinator| Ayo-West African FoodsMd, United States
Jan 17, 2024 5:35 AM
Replying to Sergio Luis Conte
...
Lean and Agile are different things. With that said, in this type of projects or environments using a Lean based approach works well. For example, Kanban system (not the board only). By using Kanban system you will be able to optimize the flow and to get a time to market according to client expectations, just in case you measure time to market.
Hello Sujith
Great question, yes we can, and the agile approach to use for ongoing bugs while the project is ongoing as well or finished will be Kanban because it will be a continuous workflow and incidents will be addressed as they come in. Saving Changes...
"This planet has - or rather had - a problem, which was this: most of the people living on it were unhappy for pretty much of the time. Many solutions were suggested for this problem, but most of these were largely concerned with the movements of small green pieces of paper, which is odd because on the whole it wasn't the small green pieces of paper that were unhappy."
Community Champion
