Please login or join to subscribe to this thread
How much effort is involved for any one microservice? If it is more than can be accomplished by the team within a sprint, you'd need to consider whether the microservice can be laterally sliced so that value can be delivered (from your stakeholders' perspective) within a sprint. If so, then define your product backlog based on a prioritized list of the microservices and then a breakdown of the near term (1-2 sprints worth) of lateral "slices" of the highest priority microservices.
You are not talking about Agile. You are talking in using a framework based on Agile which is not the same. It could sound trivial but believe me it could make the difference mainly in the type of initiatives you are talking about. I worked in those from long time ago including it before they were called "microservices". Key on microservices is the architectural design which will impact everything you do related to define "the way" (call it project) to create it. So, architecture is the key. Regarding the framework and the tool to support the framework you can use what best fit, It has the least importance. Today I am using Azure DevOps plus Scrum to create it. Last point: remember Scrum is a framework you have to fill it up which best fit for your situation. There is no line inside the Scrum Guide about you have to use story points, user stories, kanban board, etc.
Agree with Kiron
To add on to Kiron's reply...
If your project in Jira is just comprised of the 20-30 microservices you mentioned then there is no need for other configurations beyond creating the Scrum Board with the product backlog and managing the sprints like any other project.
But...If there are other issues in the project along with the microservices then, depending on how you want to run the project, us the label field to specify the microservices or place all the microservices issues under a single "Microservices" epic. you can then filter on the microservices (either the label or the epic) to create a separate Scrum board just for them. The rest of th eproject's issues can be either Scrum or Kanban, whichever is best for the team, and you can create a "Scrum of Scrums" board that includes everything.
There is more info on how to do this in the Atlassian Community.
Thanks so much for your contribution. I will check with my team to filter by epic.
Please login or join to reply