Budgeting in a Lean Agile world

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Budgeting. 

Not many statements cause as much dread in business or IT leaders as “It’s time to review your budget for next year”.  Budgets within any enterprise, but especially in the larger ones, are complex and difficult.  In our studies and work with Lean Agile Budgeting (LAB) we have learned that the average company spends about 30% of its yearly budget simply to manage its budget.  (Many CFO and financial people feel that this number may actually be higher).  Why is this?  Why do we put so much emphasis on something that is almost always (if we are honest) wrong?

The yearly budget cycle typically looks like this:

We spend so much time creating a budget, usually in the June-August time frame (for fiscal and calendar year sync companies).  And yet invariably when we start to implement on these budgets they turn out to be wrong.  This leads to endless change management, budget reviews, and many slapped wrists for being wrong. 

The problem is that we have based our budget cycles on predicting the future, and we as humans are terrible at predicting the future.  Our crystal ball is broken, and never really worked well in the first place.  When we base a yearly budget cycle on predicting we throw away the advantage that we all have; the ability to adjust based on new information.

Forecasting is a common practice in traditional budgeting, however, the term Forecast should not be used as a predictive tool, but as a learning tool.  We create forecasts to do ‘what-if scenarios, to learn about opportunities, and to better prepare for unknown outcomes.
When it comes to creating budgets the key is to create a forecast that allows us to learn and plan based on what we know today but also anticipates pivots and adjustments as we gain more knowledge during the actual implementation.  The key is to create a disciplined approach that allows for fast, non-disruptive adjustments.  This is the heart and soul of Lean-Agile Budgeting (LAB).

But how can this be done in today’s traditional, detail-oriented, regulated, and controlled budgeting approach?  With incremental changes.  I have worked with several companies that have begun this journey, and the key that has emerged is to treat your current budgeting process as a tangled ball of yarn.

To be successful you cannot just cut the ball of yarn in half, instead, you have to start pulling on one string at a time.  This allows you to learn in relative safety how to progress towards a budgeting process based on Lean and Agile principles and practices.  Implementing practices such as Weighted Shortest Job First (WSJF) for prioritization or Participatory Budgeting to gain more information on how to distribute the budget will begin to untangle that ball of yarn.

Imagine being able to streamline your budgeting process using Lean and Agile principles and practices to reduce this budget managing cost.  What better outcomes could you create for your customers and stakeholders?  What more important things could your finance group spend their time on to help the company thrive?

Subscribe for Email Updates:

Categories:

Tags:

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