Skip to main content

Mastering the Recession with Lean, Agile and Scrum

Around the world, companies are challenged by the financial crisis. Companies face declining revenue and fixed costs. Lean, Agile and Scrum help your company at all levels to focus on doing the right things, like creating value for your customer and eliminating wasted cost and effort, to get you company back to profitability. Lean, Agile and Scrum help you focus on getting the right Vision, Values and Execution to meet challenging times. Now is the time to start the discussion with your top management.

Your CEO wants your company to survive and even prosper during the recession (and we'd all be happier if there were no recession or if we could turn it around quickly). Together with Sales and Marketing, the CEO is trying to figure out whether and how much sales will dry up in 2009. He is under pressure to cut costs. If he does nothing, the company will be stuck with the fixed costs, but not have the revenue to pay for it.

Cut Wastes, not Costs

Lean is an adaptation of the principles of lean manufacturing to software development. Pioneered by Tom & Mary Poppendieck, Lean explains (particularly to management) why agile works.
Lean thinking helps management and staff focus on the right problems at the right time:
  • Create Value for your customers. Dieter Zetsche, CEO of Daimler sums it up: 'The best cure for the crisis are convincing and innovative products' 
  • Eliminate waste. Anything with does not provide value for your customers is wasted effort which should be reduced to the minimum.
  • Improving to Time to Market is a powerful cost reduction tool. If you can bring out a product in half the time, then you have half the development costs, half the carrying costs and you see a return on investment in half the time. (If in doubt, ask your CFO what that means).
  • Multitasking is an expensive form of waste because it increases time to market. Would you overload the database server at the center of your enterprise services? Of course not! The long response times would drag everything to a halt. The same is true of management and project teams. So deliver as quickly as possible by focusing on doing few things well.
Concentrate your efforts. Get new products and services "out the door", one after the other. Get your corporate response times to a minimum.

Create a productive climate

Agile values ensure effective information flow. Openness, Honesty, Courage and Trust ensure that everything which must be said can get said. If your staff fears for their job, or fears the consequences of telling the truth, they will be less willing to raise difficult issues. If your staff do not trust each other to do a good job, then people will devote energy to proving themselves or shielding themselves from blame. All these activities detract from your company's mission to create value for its customers.

Adopt agile value to create an environment where
  • Staff at all levels trust each other to do good job. 
  • Everyone can tell the truth, the whole truth, even in difficult situations.
  • All Stakeholders in a project have access to complete and correct information about the state of your projects.

Create great products and services

Agile is also a set of practices. For instance, Incremental Delivery means products are ready quickly for the customer (80/20 rule) and ROI can start quicker.

User Centered Design provides the basis for creating great products and services. Get inside your users heads. Understand what they want better than they do. Create a product which meets their needs, even the ones they didn't know they had.

Create those innovative and convincing products, which give your customers products and services that they just have to buy.

Strive for perfect execution

Scrum organizes work based around simple principles to produce concrete results predictably and with ever improving productivity. In a company organized around Scrum, everyone knows what they have to do:
  • Top management provides Vision, Focus and Flow.
  • Middle Management eliminates impediments and drives productivity upwards.
  • Self organizing, interdisciplinary Scrum Teams solve problems and deliver solutions.
Vision is about knowing where the company -- and each project -- is going. Focus is ensuring that people really act to accomplish the defined goals (without distraction). Flow is having a continuous supply of work, not too much and not too little, so that the company can consistently and predictably deliver new value to its customers.

Scrum rituals ensure everything which must be said does get said. Continuous Improvement means your productivity will be at least 30% better by the end of the year than it is today.

The way out of the recession

For each company, the way out of the recession means getting customers to buy your products and services. So follow Dieter Zetsche's advice and give them something wonderful to buy.

Get you top management interested in the problem and the solution. Tell them you want to their support for a pilot project, which will 1) create an innovative new product this quarter (which your customers will just have to buy next quarter), and 2) show how Lean, Agile and Scrum lay the foundation for a highly competitive enterprise.

You will need 1) management support and involvement, 2) an interdisciplinary team of 7 to 10 top people from your around company -- all the experts needed to make a new product and 3) probably some coaching and training to make it all work effectively.

Then go create something wonderful!

--
Originally published on my blog at AgileSoftwareDevelopment.com.

Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…