Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Using Scrum for Improving Operations

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

I’m encountering more and more people that are trying to solve different kinds of problems with Scrum:

  • People designing Consumer Goods
  • Accounting professionals focused on Revenue Accounting
  • Marketers of many kinds
  • Healthcare professionals.

I’ve been having some interesting discussions with them that I thought I might share.

One of the key questions I start a conversation about Scrum with is Why – Why do we need Scrum? What problems are we looking to solve with it?

Next, we typically explore Where/When – Where would it make sense to use Scrum? When would it or wouldn’t it?

One thing to remember is that Scrum was designed to help people solve complex problems, not all sorts of problems. What does this mean exactly?

Let’s look at a couple of examples of Complicated processes that might not need Scrum/Agile

Accounting teams run several sorts of processes – like Closing (the month, quarter, year), Reporting, Accounts Payable, and Accounts Receivable.

Healthcare professionals treat patients. Whether it is in an emergency room, an orthopedics clinic, or a covid19 testing provider.

Should we use Scrum for Operational Processes?

These might be complicated processes but they aren’t typically complex. Lots of steps, and lots of work they need to be careful and diligent about, but it’s not something they need Agile for on an ongoing basis.

Hopefully, these operational processes are stable and predictable. If they’re not, we have some work to do. We need to get rid of variability and surprises.

We can use Scrum for Improving operational processes

Where Scrum IS often useful in the process of continuously improving these operational processes. We know how to run the current process predictably. But once we decide to improve it, this might be a problem we have more uncertainty about – what does better look like? What will work? How do we go about implementing it?

What we find in many contexts is that people call these improvements “Projects” and it is one of the areas they struggle with. Beyond the classic challenges of complex work, we see many cases of teams working on improvement projects that are based on people who also work in the operation. (for example an A/R professional working on a project to improve A/R or a physician participating in a project to implement electronic medical records software). These teams working on improvement “projects” struggle to focus. As we all know, Allocating capacity to improvement is hard. And switching contexts between the day-to-day operation and improvement work is hard as well.

Scrum helps these teams optimize the value they create through their improvement work.

Their “Product” is an improved operation that achieves better outcomes for their stakeholders while making life easier for themselves and their peers.

We want the entire company to be Agile

We’re hearing that more and more aren’t we?

As you can imagine based on the above, I’m of the opinion that we need to be careful and apply the right tool in the right context. Agile approaches make sense in many contexts and most companies would indeed benefit from applying them beyond software development/technology/IT.

Identifying the different “Operational” flows in the organization and the various “Development/Improvement” activities that work to improve them is a great way to drive a discussion with a company or a leader that is exploring Agile/Scrum all over the company.

In Summary – Scrum for Improving Operations, not necessarily Scrum for Operations

This distinction between the ongoing “Operations” where we don’t necessarily need Scrum or Agile and “Development” or “Improvement” work that aims to improve “Operations” helps people outside of software/technology/IT relate and buy into Scrum or other Agile approaches.

PS You might find it interesting to read about “Operational Value Streams” and “Development Value Streams” in SAFe, which are similar concepts to what I’m describing here.

Subscribe for Email Updates:

Categories:

Tags:

Lean Risk Management
Amdocs
Covid19
Agile Assembly Architecture
Agile in the Enterprise
Nexus and Kanban
Agile for Embedded Systems
Operational Value Stream
ScrumMaster Tales
Advanced Roadmaps
ATDD
Agile Project Management
Spotify
Kanban Kickstart Example
Continuous Integration
Lean Startup
SPC
ATDD vs. BDD
Scrum Values
Tools
User stories
AI Artificial Intelligence
Tips
Scrum Master
POPM
Certification
speed @ scale
Scrum and XP
Risk-aware Product Development
Managing Risk on Agile Projects
Kanban
Legacy Code
Software Development Estimation
chatgpt
Agile and DevOps Journey
Perfection Game
Risk Management on Agile Projects
Accelerate Value Delivery At Scale
Agile Release Management
System Team
Engineering Practices
Agile Development
Continuous Planning
Atlaassian
Kanban Game
Jira Plans
Jira
Professional Scrum Product Owner
LPM
Elastic Leadership
speed at scale
Continuous Improvement
Kaizen Workshop
Lean Software Development
Limiting Work in Progress
Release Train Engineer
GanttBan
Atlassian
Video
Rapid RTC
Agile Risk Management
Implementation of Lean and Agile
Agile Contracts Best Practices
Team Flow
Process Improvement
Lean Agile Organization
EOS®
Agile Exercises
Lean Agile
Agility
Continuous Deployment
Agile Outsourcing
What Is Kanban
Entrepreneurial Operating System®
LAB
Agile Program
Product Management
RTE
Releases Using Lean
NIT
Scrum
Presentation
Development Value Streams
Sprint Iteration
Systems Thinking
Lean-Agile Software Development
Agile Delivery
Professional Scrum Master
Agile Project
DevOps
ARTs
Jira admin
Continuous Delivery
Agile Marketing
lean agile change management
Introduction to ATDD
Acceptance Test-Driven Development
Introduction to Test Driven Development
Quality Assurance
AgileSparks
Lean Agile Management
Scrum.org
Coaching Agile Teams
The Kanban Method
Pomodoro Technique
Agile Testing Practices
Nexus Integration Team
Agile Product Ownership
Agile Release Planning
Agile Israel Events
AI
Agile Games
Agile Games and Exercises
Code
Reading List
PI Objectives
Self-organization
Agile
Frameworks
Nexus
Implementing SAFe
RTE Role
Test Driven Development
Built-In Quality
SA
Agile Community
A Kanban System for Software Engineering
SAFe Release Planning
TDD
Agile Product Development
System Integration Environments
Business Agility
Scrum Master Role
Lean Budgeting
BDD
WIP
Manage Budget Creation
Keith Sawyer
Scaled Agile Framework
Iterative Incremental Development
Managing Projects
PI Planning
Planning
Enterprise DevOps
Nexus vs SAFe
predictability
Agile Israel
Product Ownership
Principles of Lean-Agile Leadership
Software Development
Large Scale Scrum
Scrum With Kanban
IT Operations
Sprint Planning
SAFe DevOps
Agile Techniques
Professional Scrum with Kanban
Risk Management in Kanban
Sprint Retrospectives
Lean Agile Basics
Scrum Guide
Certified SAFe
Program Increment
Kanban Basics
Daily Scrum
Portfolio for Jira
Agile Basics
Effective Agile Retrospectives
Lean and Agile Principles and Practices
QA
Change Management
Kanban 101
Applying Agile Methodology
Slides
SAFe
agileisrael
Story Slicing
Hybrid Work
Scrum Primer
Games and Exercises
Legacy Enterprise
Agile India
Lean and Agile Techniques
The Agile Coach
Webinar
ROI
Jira Cloud
Kaizen
Agile Mindset
An Appreciative Retrospective
ALM Tools
LeSS
Achieve Business Agility
Artificial Intelligence
Lean-Agile Budgeting
RSA
System Archetypes
Value Streams
Nexus and SAFe
Lean Agile Leadership
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart