Transform Enterprise Finance Functions based on Lean-Agile budgeting Models
We find that as enterprises drive business agility using lean agile methods, it faces friction and quickly hits against wall of rigid traditional budgeting methods and project based cost accounting.
Traditional cost accounting believes in long horizon planning, it values plan accuracy with frequent variance analysis against original estimates rather than accept uncertainty, respond quickly to market trends. We notice frequent delays on re-approvals of changing budgets; a big WASTE. How can we transform finance functions to enable lean agile software and systems development?
We can address this conflict with new Lean-Agile budgeting models that cater to the need of both the worlds: allowing empowered lean agile development programs for rapid decision making that are responsive to market, align with professional accountable management of dollar spends.
Traditional cost center based investment planning is based on deliverables, but the content of such deliverables are changing rapidly that require flexible resourcing across projects.
We all agree that agile portfolios need to execute and deliver value within an approved operating budget which is an outcome of strategic planning process at enterprise level. This paper describes the nuts and bolts around how to establish, administer and govern agile portfolio budgets.
Outline/structure of the Session
Outline/Structure of the Session
Highlight key areas that agile software development and traditional cost accounting do not match [ 15 mins – 7 slides]
Understand the mechanics of lean agile budgeting and forecasting, administration and fiscal governance with dynamic budgeting [15 mins – 6 slides]
How to setup a working model between finance functions and lean agile delivery teams that promotes agility over accuracy and trust over controls [10 mins – 4 slides]
How to handle CapEx and OpEx elements of budget in an lean agile development context [10 mins – 4 slides]
Roles and responsibilities for leaner financial planning, content planning and capacity planning for dynamic resourcing needs [ 15 – 5 slides]
Q & A [10 mins]
The goal of the talk is to highlight and gain awareness around current challenges and conflicts apparent between budget planning office following traditional rigid deliverables based cost accounting practices vs lean agile program teams that welcome uncertainty and constantly re-prioritize the deliverable contents to maximize customer value
My primary goal is to trigger the thought within the PPM community and financial budget planners within an enterprise, where there is big mismatch between how budget cycles are estimated, approved and allocated based on long time horizons, where focus is more on planning accuracy and variance analysis rather than quick response and increasing value to customers in constantly changing market landscape
It will contain some slides with case study based examples
It will be an interactive talk, welcoming questions around real life situations faced by attendees in their current roles
- Plan roughly for longer time horizon initiatives, and more accurately for short time period which leads to higher throughput, higher morale and less budget surprise
- Abandon cost center or deliverable based approach to budget approvals and controls
- Assess and question the traditional accounting practices, propose changes to finance planning functions to become a true enabler of agile and lean development
- Need for visibility of deliverables and promote culture of transparency
Program Portfolio Management Leaders, Business Unit Heads, PMO, Budget Planners, and Budget Approvers
schedule Submitted 1 year ago
People who liked this proposal, also liked:
The Agile Ecosystem - Changing the way we think about Organizing to Deliver ValuethomasjeffreyPresidentAgile By Design
schedule 1 year agoSold Out!
A key leadership responsibility in today’s enterprises is understanding how to create organizational structure that promotes agility. Most organizations think about their organizations as a hierarchy, with departments dedicated to specialist functions like marketing, finance, or IT. This hierarchy based model can make it very challenging for knowledge workers to collaborate with each other to the extent necessary to deliver value. Especially when you consider today’s environment of constant change
With agile becoming increasingly popular, the concept of creating structure based on cross functional self organizing teams is becoming increasingly popular. There are obvious advantages to this approach such as breaking down functional silos, moving employees closer to the customer, and motivating a diverse collection of specialist towards a common goal. Organizations often face challenges when moving from a hierarchical model to one based on agile teams, and they have encountered a number of very serious challenges.
Organizational designers often struggle with creating a model that is economically feasible,. The model does not always seem to lend itself to managing scarce expertise. A different type of siloing can occur, where discrete business functions or customer experience teams have very little integration with each other, this can cause crosscutting concerns to the organization to become forgotten, and create an overall loss of organizational cohesion. Team coordination and communication becomes a concern as agile deployment scales to larger and larger efforts.
Over the last several years I have paid attention to how others are deploying agile at scale, as well as catalog my own experiences in helping customers with changing their team structure to improve agility. The results are a set of patterns that describe different ways teams can be designed to provide effective services their customers, and collaborate with each other.
During this session I want to provide participants with a chance to use a set of defined team service and team linking patterns to design an agile ecosystem; a system of self-organizing, interdependent teams, a system that constantly evolve to organize around value. This session promises to be a hands on, in depth session where attendees will be able to develop a real world example of team organizational structure designed to improve agility in their context. I'll walk attendees through the steps necessary for designers to identify the teams and interactions required to deliver value as well as the the support structures required to enable those teams.
Participants will build a real agile team ecosystem that covers the following steps:
- describing the services, clients, and capabilities of your teams, and organize them into higher order missions
- Applying one or more team delivery patterns
- Applying one or more team linking patterns
During this session I will facilitate ecosystem design through the use of an agile ecosystem design toolkit. I will use the toolkit to describe the details of each pattern, including when to use them and some of the benefits and trade-offs required.
Agile Trekking: Why does it look I am walking backwards, how do I improve, sustain and trek forward?Pranay ChandaAgile Transformation LeaderCognizant Technology Solutions
schedule 1 year agoSold Out!
Leaders often find themselves in this situation after few plus years in an agile transformation journey. At the start of the trek everyone in the enterprise were super excited, adopted new practices, shared learnings, worked as cohesive unit, and delivered predictable and continuous value to customers.
Trekking through the years, we find consultants leave and with it the expertise. You start to notice dysfunctions, lethargy, lack of motivation and biggest problem diminishing value delivery to customers. What is going on? As trek leader why do I feel we are walking backwards reliving the past all over again? How do we stop it and resume trekking in the right transformation path?
How to stem the backward spiral, with organic sustainable strategies and governance mechanisms that have been applied successfully at large enterprises. The talk introduces the learning organization model with transformation office, coaching nucleus, community of practice and knowledge nerve center all working under the stewardship of change leadership team.