The Case for Standardising Ways of Working in Software Delivery Teams

What Are Ways of Working?

Before diving into standardisation, let’s define “ways of working.” In the context of software development or digital product development, ways of working refers to the methods, practices, and processes teams use to collaborate, communicate, and execute tasks. It encompasses frameworks, communication protocols, workflows, tools, and decision-making approaches that guide day-to-day work.

For instance, some teams rely on Agile methodologies, utilising Scrum or Kanban frameworks, while others may adopt a hybrid approach. It also includes coding standards, quality assurance processes, deployment strategies, and even how feedback loops are managed.

Software and Digital Product Development

In software delivery, teams work across a spectrum of tasks that range from building new features to supporting legacy systems or innovating entirely new products. Each team’s role and function shape its way of working. Let’s take a look at common team types found in software development:

• Feature Teams: These teams focus on delivering end-user functionality. Their primary job is building new features or improving existing ones, working closely with product managers and designers.
• Support Teams: These teams manage, troubleshoot, and support existing systems, ensuring that operations run smoothly and addressing issues as they arise. Their way of working is often reactive but requires efficient knowledge sharing and cross-functional collaboration.
• Platform Teams: These teams focus on maintaining infrastructure, optimising system performance, and enabling feature teams by ensuring they have the technical foundations to deliver effectively.
• Product Teams: Focused on delivering value around a specific product line, these teams engage in iterative delivery, often maintaining close alignment with stakeholders and clients to continuously rank tasks based on business needs.

Each team has unique needs, but how they work has a direct impact on speed, efficiency, and business outcomes.

The Why

Now that we understand the diversity of team structures, let’s talk about standardising ways of working. Why would an organization want to invest in this? Here are the key reasons:

• Efficiency Gains: When teams follow standardised processes, there’s less time spent reinventing the wheel. Everyone understands the workflows, and hand-offs between teams become smoother. This means reduced lead times and increased throughput.
• Predictability and Quality: Standardisation promotes consistent outcomes. Whether it’s how code is reviewed or how deployments are handled, having a set process reduces the risk of errors and ensures that quality is built into every step of the development lifecycle.
• Scalability: As organisations grow, standardised ways of working ensure that scaling doesn’t mean chaos. New teams can be onboarded quickly because the processes are already in place, documented, and proven.
• Cost Control and Resource Efficiency: Standardising reduces unnecessary experimentation with methods and tools. Teams can avoid duplicate work, reducing operational costs while maximising the use of resources such as time and talent.

Return on Investment (ROI)

From a business perspective, standardising ways of working can deliver tangible ROI. Here’s what you can expect:

• Increased Delivery Speed: Streamlined workflows and clear processes enable teams to deliver features and products faster, which directly translates into quicker time-to-market for products, giving you a competitive edge.
• Enhanced Collaboration: When everyone follows a consistent framework, cross-team collaboration improves. There’s less friction when different teams (feature, support, platform) need to interact.
• Risk Mitigation: Standardisation minimises the chances of critical errors, missed steps, or misaligned priorities, which could lead to costly project delays or failures. It’s an investment in long-term stability.
• Improved Team Satisfaction: A clear, well-understood way of working reduces ambiguity and frustration. When team members know what to expect and how to perform, they feel more confident and empowered.

What Are the Downsides?

While there are clear benefits, standardizing ways of working isn’t without its challenges. Here are some potential downsides to consider:

• Inflexibility: Over-standardising can stifle creativity and limit the flexibility needed to adapt to changing circumstances. Some teams require unique approaches, especially when dealing with innovative or exploratory work.
• Initial Investment: Implementing standardised processes requires time, effort, and sometimes a cultural shift. Teams that are used to autonomy might resist the perceived rigidity, and training efforts might slow down initial progress.
• Loss of Autonomy: If not carefully balanced, standardisation can reduce a team’s sense of ownership and decision-making power, which could demotivate some members and lead to lower engagement.
• One Size Doesn’t Fit All: Different teams have different needs. While standardisation can streamline operations, enforcing a uniform approach may lead to inefficiencies in cases where teams need specific solutions tailored to their unique challenges.

A Strategic Investment in Efficiency

Standardising ways of working in software delivery is not a decision to take lightly. However, when done right, the return on investment can be substantial. By improving efficiency, reducing errors, and fostering better collaboration, organisations can expect to see more predictable outcomes and higher-quality products. The key is striking a balance between structure and flexibility, allowing teams to innovate while reaping the benefits of a consistent, optimised approach.

As with any investment, it’s important to periodically reassess whether the standardisation approach is still delivering value or needs adjusting based on changing circumstances or team dynamics.

Recommended Books

“Accelerate: The Science of Lean Software and DevOps” by Nicole Forsgren, Jez Humble, and Gene Kim

This book is excellent for understanding how to improve software delivery performance through proven practices and processes. It’s grounded in research and provides a data-driven approach to efficiency, standardization, and team performance.

“Team Topologies: Organizing Business and Technology Teams for Fast Flow” by Matthew Skelton and Manuel Pais

A great resource for understanding how to structure teams for optimal collaboration and flow. The book outlines different team types (e.g., feature teams, platform teams) and gives practical guidance on how to align ways of working with team structures.

“The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win” by Gene Kim, Kevin Behr, and George Spafford

Written as a novel.