Where can we track the "ops" side of devops?
Hi everyone!
My PO asked if I could look around for best practices on how to gain insight in the ops side of the devops. We are working in Scrum and have a board that contains the user stories and bugs.
But we also have 2 team-members who are not developping but working on the support tickets, manuals, FAQ's, those kind of things.
I suppose we can give the creating of manuals, FAQ's and other planned work a story that gets pokered. But is that in accordance with the scrum way of working?
Should we give the ops side of our work another board so we can use it in a more kanban approach?
What you describe is not DevOps. DevOps is a cultural shift along with some practices that move operational considerations "left". In the same way, a principle of Agile Software Development is that business people and developers work together every day, DevOps is about operations specialists being more involved across the software development life cycle.
There are different ways to achieve DevOps. Sometimes it means embedding operations specialists onto development teams. Other times, it may be matrixing operations specialists to the development organization to support ongoing efforts as needed. It could also be having highly cross-functional people who handle operations alongside development.
If your team members are all on the Scrum Team, then what you're doing doesn't align with Scrum. Having two sub-teams is not per Scrum. You want a single, unified, cross-functional Development Team. That doesn't mean that people can't have specializations, but if I would consider a specific type of work that must be done by a particular group of individuals to be having sub-teams. This is even more true if you are not taking action to make the whole team cross-functional.
My PO asked if I could look around for best practices on how to gain insight in the ops side of the devops. We are working in Scrum and have a board that contains the user stories and bugs.
But we also have 2 team-members who are not developping but working on the support tickets, manuals, FAQ's, those kind of things.
That's not the ops side of anything. It's the work left over when deliverables aren't fully usable and of release quality.
Check out my blog on Scrum and DevOps. Hopefully it can give you some inspiration.