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:

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