Dynamic Squad Model

The Dynamic Squad model, a software development model, is the modern way of organizing software development teams focusing on a specific set of goal(s).

A squad is a small group of people focusing on a particular goal or purpose. The size and lifespan of each squad will be different and will be based on the goal; hence, it's referred to as dynamic. 

Structure

Each Dynamic Squad consists of at least four roles : 

Developer(s) are dedicated to one squad at a given time, whereas Squad Lead, Product Lead, and Project Managers can be involved in multiple Dynamic Squads depending on the needs in a particular organization.

Life Cycle of Squad

The life cycle of Squad consists of the following three phases.

Create

• Senior Leadership appoints Squad Lead, Product Leads for Squad
• Squad Lead & Product Lead deep dives into the goal(s) and identify resources needed and appropriate team members from the available resource pool
• Squad is formed

Function

• The squad starts detailed analyses of requirements associated with goal(s) and defines high-level solutions. 
• The project manager outlines the overall delivery strategy and plan
• Squad now started putting the plan into motion using Agile methodology. Kanban is more suitable with this model, but depending on the nature of the work, Squad can decide and use Kanban or Scrum agile methodology. 
• For proper execution highly recommend the following ceremonies: 

Dissolve

• The squad enters into this phase once goals are achieved, and deliverables are pushed to production. 
• The squad does a retrospective to identify what went well and what didn't go as per the plan and identifies potential improvements for upcoming squads. 
• The squad gets dissolved, and members are released back to the resource pool so that they can be part of upcoming squads.

Pros of the Model

• Focus on goals results in focus on delivering value
• Developer(s) are focused on one or more related goal(s), which reduces context switching and improves productivity, and also time to market is less
• The agility of the model allows quick adaptation to changes in scope, priorities, or business demands.
• The dynamic nature of this model allows leaders to do dynamic resource allocation as compared to strong team boundaries.
• Developer(s) get the opportunity to work on different things in a systematic order instead of multiple projects simultaneously, which boosts their morale.
• Squad members take ownership of their tasks, leading to higher accountability and commitment.

Cons of the Model

• It's a cultural shift; hence, implementation from the traditional hierarchical model to this model could be challenging.
• Scaling this model with for large organization with a matrix structure needs an open mindset, continuous learning, and adaptation for successful implementation.

Case Study

I used this model for a group of 35+ developers. The group was responsible for Client Customization and integration development. For a while, operating in a scrum team-based model resulted in different challenges, as listed below.

• Developers need to switch context more often while simultaneously working on multiple client-specific projects, which is painful, less productive and takes a longer time to market. 
• Difficult to maintain the team's backlog
• Due to strong team boundaries, it is hard to move resources between scrum teams based on need. 

To improve team efficiency and for a shorter time to market, there is a need for the group to operate in an innovative model that allows dynamic resource allocation. Developers have to focus on one thing at a given time. Started adapting the dynamic squad model. 

At a given point, there were 5-6 Squads, as shown below, with specific goals:

After adoption, observed the following advantages

• Time to market improved by 50%, i.e., before, it used to take six weeks to deliver, whereas in the Dynamic Squad model team was able to deliver a similar type of work in about three weeks.
• The team happiness survey indicated that individual member’s happiness has increased by 25% since day-to-day operations became more structured and organized.

Overall, leadership observed the success of the group after adopting the Dynamic Squad Model.

Other examples where this model can be used are in Startups and big companies focusing on next-generation product development in a fast-paced start-up-like environment. Also, the latest emerging technologies complement this model.