Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Scrum
How to manage micro services project in Agile
Hi All,

I would like to request an idea for how to manage the microservices project in Agile (Scrum) - JIRA. It may includes 20-30 microservices in the whole project. I would really appreciate if you guys may suggest on this.

Regards,
Kyaw
Sort By:
Kyaw -

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.

Kiron
...
3 replies by Jim Lile, Kyaw Wanna, and Scott Theus
Feb 02, 2020 9:23 PM
Kyaw Wanna
...
Thanks so much and appreciated for your reply. This is well explained.
Feb 03, 2020 12:29 PM
Scott Theus
...
Kyaw,

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.

-Scott
Feb 13, 2020 12:48 PM
Jim Lile
...
some micro services (MS) are large, some are small. As they MS grow to contain to many rules and logic they can be broken up and refactored. They key to MS development is to connect and "stand up" the MS in a sprint and as immediate as you can. Hence. Connect the UI, to the BS, to the DS, to the DB. slice the functionality to do the base work and grow into functionality that can be demo'd. Typically demo's will show working code and you'll have to explain what isn't work "yet" and what is coming next. MS is my preference. Also when planning, ensure team call out what services they will be working on so that you understand dependencies. BREAK these dependencies the best you can and consume the work and/or people. when 2 devs need to work on the same MS in the same sprint, find ways for them to Pair and work together and deploy what is need for both parties, if/when appropriate break them into versions.
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.
...
1 reply by Kyaw Wanna
Feb 02, 2020 9:23 PM
Kyaw Wanna
...
Thanks for sharing.
Agree with Kiron
...
1 reply by Kyaw Wanna
Feb 02, 2020 9:24 PM
Kyaw Wanna
...
Thanks for your reply.
Jan 28, 2020 1:29 AM
Replying to Kiron Bondale
...
Kyaw -

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.

Kiron
Thanks so much and appreciated for your reply. This is well explained.
Jan 28, 2020 5:02 AM
Replying to Sergio Luis Conte
...
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.
Thanks for sharing.
Jan 28, 2020 8:17 AM
Replying to Abolfazl Yousefi Darestani
...
Agree with Kiron
Thanks for your reply.
Jan 28, 2020 1:29 AM
Replying to Kiron Bondale
...
Kyaw -

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.

Kiron
Kyaw,

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.

-Scott
...
1 reply by Kyaw Wanna
Feb 03, 2020 10:40 PM
Kyaw Wanna
...
Hi Scott,

Thanks so much for your contribution. I will check with my team to filter by epic.
Feb 03, 2020 12:29 PM
Replying to Scott Theus
...
Kyaw,

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.

-Scott
Hi Scott,

Thanks so much for your contribution. I will check with my team to filter by epic.
Jan 28, 2020 1:29 AM
Replying to Kiron Bondale
...
Kyaw -

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.

Kiron
some micro services (MS) are large, some are small. As they MS grow to contain to many rules and logic they can be broken up and refactored. They key to MS development is to connect and "stand up" the MS in a sprint and as immediate as you can. Hence. Connect the UI, to the BS, to the DS, to the DB. slice the functionality to do the base work and grow into functionality that can be demo'd. Typically demo's will show working code and you'll have to explain what isn't work "yet" and what is coming next. MS is my preference. Also when planning, ensure team call out what services they will be working on so that you understand dependencies. BREAK these dependencies the best you can and consume the work and/or people. when 2 devs need to work on the same MS in the same sprint, find ways for them to Pair and work together and deploy what is need for both parties, if/when appropriate break them into versions.

Please login or join to reply

Content ID:
ADVERTISEMENTS

I watched the Indy 500, and I was thinking that if they left earlier they wouldn't have to go so fast.

- Steven Wright

ADVERTISEMENT

Sponsors