How to Manage Agile Teams With Microservices

DZone 's Guide to

How to Manage Agile Teams With Microservices

A how-to for utilizing all things microservices.

· Microservices Zone ·
Free Resource

We’re getting closer to the 2019 finish line, but there’s still time to jump on the microservices train to accelerate your team’s delivery. We’ve written about microservices in the past, including discussing best practices for microservices implementation and GitLab’s integrated vision for microservices, but I’m here to share something a little different: How you can use microservices to manage your team.

But first, a recap: Microservices is a collection of independently deployable services that advance a goal, with each application managing a specific function really well.

“The term ‘Microservice Architecture’ has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services.” – Martin Fowler

GitLab Microservices for Agile Team Management

Using GitLab Projects and Groups, teams can organize their work to increase visibility and collaboration. GitLab supports Agile teams by providing Milestones (or sprints), Issues (or user stories), Weights (or points and estimation), and other common Agile artifacts.

Here are a few ways to use groups and projects:

Organizing Your Team by System

One of the more traditional ways to divide work, organizing by system separates teams by component and subsystem. For example, the teams that handle mobile iOS, mobile Android, and websites have different projects, each with their own code repo and issue tracker. This type of structure works well with operations-driven organizations, but it’s not a modern approach, so we recommend one of the following structures instead.

Organizing Your Team by Product Area

Dividing work by-product is a best practice that drives business value. Using GitLab Groups, you can create Codeand Teams. Within Code, separate projects represent various components (e.g. mobile iOS and user accounts), with individual code repositories and sets of merge requests. Once you’ve created your projects (and code repos), you can build another group forTeams, which includes full-stack product teams (i.e., engineers, PMs, designers), enabling parallel milestones and Agile boards. The benefit of organizing work by product area is that there’s a separation between code repos and work so that every piece of code in your organization is open to contributions from all teams.

Organizing Your Team With a Hybrid Approach

This approach combines both product and system organization structures and is well suited for organizations that have cross-platform teams. For example, a mobile team has dedicated iOS and Android engineers rather than full teams for both platforms. In this model, the Code group will have individual projects according to a component, but Teams is consolidated so that there are only a website and mobile team.

Watch this demo and check out its corresponding example application to see groups and projects in action. 

Does your team use microservices for Agile development? We’d love to hear your thoughts.

microservice ,agile ,organization ,tutorial

Published at DZone with permission of Suri Patel , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}