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:

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