I am asked more often: How can we work as a service team with agile principles?
Is Scrum right for us? How can we keep space free for day-to-day business in sprints, but still work on fixed goals? Or should we rather work according to Kanban?
Probably there is no single right answer, it always depends on organization, team and customer. But I would be interested in your experiences in this context. Have you experienced similar situations? Do you work in a similar environment?
I am looking forward to your answers.
Thanks @Harald Seyr
Hello @Kai Becker .
It’s important to distinguish between agile principles and Scrum. So, let’s go for the agile principles first:
Now, you have Scrum, with roles, events and artifacts. Every IT Service Focused Team will also have improvements or Kaizen initiatives. You can use Scrum (and a scrum/Kanban software project), to handle these improvements.
CHECKOPS could also be considered a “retrospective”. You could have a Product Owner who sets the vision/roadmap for your service team. You could have a Scrum Master who helps the teams stay focused on their improvements initiatives, remove impediments, while keeping the customers happy. You can do sprint reviews to “demo” new service initiatives implemented (new dashboards, new monitoring, new processes, new self-service tools, new knowledge base articles, etc.)
You can also have Dailys, getting a quick overview of highest priority issues, and if there is any impediment that must be addressed.
Hi @Ivan Ferreira ,
thank you for bringing back the principles. It is always good to remember the basics and not to take the second step before the first.
I will definitely take another look at the topic of CheckOps and also recommend it to our internal service teams. Thanks for the tip!
Hi @Kai Becker ,
I am coaching an IT team, that has about 50% of their work planned and 50% unplanned for various service requests that are created daily.
The team is working hand in hand with a Business operations team, that generates many of the system changes that are needed, and work together with the different business teams to unravel their needs from the system.
The IT team, with the Business operations team (their team leader acting as Product owner), practice scrum, work in sprints, plan their sprints based on what they know upfront, while making sure to have enough slack to be able to address the incoming day-to-day requests.
When a new request comes in, which cannot be handled as "support" and needs to be planned and prioritized, then it enters the backlog and waits for the next sprint to be planned.
All in all, this is currently working for us. We are always looking at the slack needed, at the ability of the team to plan and execute their plan, and make adjustments on the way we work.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.