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:

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