Lean Software Delivery

Get lean and mean without being stretched too thing

Lead Consultant & Tech Evangelist

Eric is Lead Consultant at Urbancode where I help customers get the most out of their build, deploy and release processes.

Today he works with customers and industry leaders to figure out this DevOps thing.

Eric Minickeminick@us.ibm.com@EricMinick

Why Lean? Need to do more

Agile: Faster pace of builds & releases More complex architectures Distributed, even global teams

Adding more people unlikely Only solution is to increase efficiency

Lean Software By analogy, inspiration and even direct mapping from

Lean Manufacturing

More focused on principles than practices 7 Lean Principles Complements and underpins Agile and DevOps

Provides a low-risk approach to increasing efficiency

Lean increases efficiency by removing waste

7 Wastes: of Manufacturing

InventoryExtra ProcessingOverproductionTransportationWaitingMotionDefects

7 Wastes: of Software

Partially Done WorkExtra ProcessesExtra FeaturesTask SwitchingWaitingMotionDefects

Wastes: 1 Partially Done Work

Waste: Work you get no value from Risk: Untestable.

Can’t verify you’re on the right track

Commons.wikimedia.org

Wastes: 2 Extra Process

Wastes: Paperwork that nobody really reads is “theater” at best, a complete waste at worst.

What happens if we skip or delay this process? Is any value to the customer lost?

Image: http://upload.wikimedia.org/wikipedia/commons/d/d9/Paperwork_-_by_Tom_Ventura.jpg

Wastes: 3 Extra Features

Waste: All planning, development and testing time was useless. No value was delivered.

Worse: Extra complexity was introduced

Image: http://commons.wikimedia.org/wiki/File:IPhone_3G.png

Wastes: 4 Task Switching

Waste: “Reloading” the information for various concurrent process is expensive when switching between them.

Another useless meeting… now where was I on this?

Wastes: 5 Waiting

Waste: When the project is not moving forward, value is not being delivered.

Waiting tends to generate more task switching as well.

Wastes: 6 Motion

Each hand-off represents a risk due to incomplete knowledge.

Can my developer quickly understand a feature, or does she need to ask someone; who asks someone; who asks someone?

Wastes: 7 Defects

Severity of Defect * Time undetected

In Short

Build the right thing

Deliver it promptly

In Short

Deliver it promptly

Execute Efficiently

In Short

Deliver it promptly

Execute Efficiently

Agile focuses here

DevOps focuses here

In Short

Deliver it promptly

Execute Efficiently

Agile focuses here

DevOps focuses here

DevOps also helps with feedback

Build the right thing: Strategy by situation When requirements are well understood

Document them well

When big picture is understood but details are shaky Tight customer collaboration Rapidly deliver to QA and user acceptance for validation

When big picture of the app is shaky Use ‘Lean Startup’ approach of Minimum Viable Product

• Get something in front of customers quickly and measure

Should I support ‘Log-in with Facebook’?

Pro: Lower sign-up barrier to entry. More customers!Con: My company is B2B. Maybe Facebook is too personal

1) Acknowledge uncertainty

2) Establish a Thesis

10% of People who would otherwise ‘bounce’ will attempt to sign up w/ Facebook

3) Test it cheaply. Then decide

10% of People who would otherwise ‘bounce’ will attempt to sign up w/ Facebook

Add button that doesn’t work for X% of visitors. Measure attempted use.

Something went wrong. Try again.

Experimentation may depend on delivery

Deliver it promptly

Execute Efficiently

Agile focuses here

DevOps focuses here

DevOps also helps with feedback

Visualize waste with lean techniques

Spaghetti Diagramming shows motion, such as handoffs and the flow of artifacts

between people

Value Stream Mapping shows the temporal division between work being done

(value being added) and waiting (waste)

image credits: http://commons.wikimedia.org/wiki/File:Diagram_spaghetti_kilka_produktow.PNGhttp://www.michaelnygard.com/blog/2008/02/outrunning_your_headlights.html

Example: Sign-off Process

1. PM emails Dev Manager2. Dev Manager emails PM3. PM emails QA Manager4. QA Manager emails PM5. PM emails Operations6. Operations emails PM

Spaghetti diagrams show flow of work

Value stream map shows delays

---3030303030

111111

Waiting Working

1. PM Dev2. PM Dev3. PM QA4. PM QA5. PM Ops6. PM Ops

Value stream map after process change

------30---3030

1---1---11

Waiting Working

1. PM Dev2. ----------3. Dev QA4. ----------5. QA Ops6. Ops PM

Lean Software Takeaways

Inspired by Lean Manufacturing

Strong emphasis on removing “waste”

The 7 Wastes of Lean Software Development

Tools for Visualizing Waste

A Lean view of build & deployment

Common Practice: “Dan the Deployer”

1. Pam emails Dan to deploy to the Development environment

2. Dan the Deployer reads the email 3. Dan moves the build artifacts to the Development

environment4. Dan runs the deployment scripts5. Deployment script runs while Dan monitors

progress via the console6. Dan emails Pam to let her know the deployment is

complete7. Pam reads the email

Dan’s Diagram

1. Pam emails2. Dan reads3. Moves artifacts4. Launches script5. Deploy runs6. Dan emails7. Pam reads

---???0?1

Waiting Working

Delays from Dan

What if Pam could click a button?

http://commons.wikimedia.org/wiki/File:Big_Green_Button.png

1. Pam triggers2. ----------3. Move artifacts4. ---------- 5. Deploy runs6. System emails7. Pam reads

------0---001

1---1---1001

Waiting Working

Self-service deployment removes delays

Deployment automation story

Offshore testing team needed to request deploys to test environments Due to timezones, average turn-around was 20 hours Giving the offshore team direct access to servers was not

an option

Secure, automated deployments allow self-service Turn around drops to under one hour

Win: 15% more testing gets done. Defects found faster, cheaper to fix, and product ships quicker.

Bug fix & verify cycle

1. Pam commits a feature2. Feature is built by Bob3. Build with new feature is deployed by Dan4. Tom the Tester tests new feature and reports a bug5. Pam fixes the bug6. Bug fix is built7. Build with fix is deployed8. Tom verifies the bug fix

Manual fix & verify spaghetti

Bug fix & verify value stream

7203600240

2880720

3600240

12060151560

Waiting Working

12000 300

1. Feature build2. Build deployed3. Bug reported4. Pam fixes 5. Fix built6. Fix deployed7. Tom verifies

Adding automation

1. Automated builds (CI); that invokes:2. Automated deployments; that invokes:3. Automated regression tests

12060151560

7203600240

2880720

3600240

Waiting Working

12000 300

Impact of continuous delivery

7203600240

2880720

3600240

12060151560

Waiting Working

12000 300

Impact of automated testing

Waiting Working

12000 300

7203600240

2880720

3600240

12060151560

Impact of automated reporting

Bug fix & verify with Enterprise CD

Bug fix & verify value stream with ECD

151530151515

Waiting Working

1500 225

CD impact on bug fix & verify cycle

Partially Done WorkExtra Processes: no bug “hot potato”; Tom tests onceExtra FeaturesTask Switching: Pam quickly notified of defectWaiting: no waiting for builds or deploymentsMotion: fewer handoffs; no bug report adminstriviaDefects: more time testing, can find additional defects

The impact of automated building & testing

90% rise in LOC output/programmerwhen performing builds at least daily

36% reduction in defect ratewhen integration/regression testing at each code check-in

“Trade-offs between Productivity and Quality in Selecting Software Development Practices”, IEEE Software, Sept-Oct 2003

Think at the system level

Image credit: http://52weeksofux.com/post/694598769/the-local-maximum

Urbancode.com/resources

Continuous Delivery Maturity ModelDeployment Automation BasicsValue of Deployment Automation

Blogs.urbancode.com

Twitter.com/UrbanCode

Facebook.com/IBMUrbanCodeProducts

SlideShare.net/Urbancode

Further Resources

Yes, UrbanCode has tools that help

IBM UrbanCode Deploy Application Release Automation

IBM UrbanCode Release- Release management and release weekend v execution

IBM UrbanCode Build Build automation on an enterprise scale

Q&Aeminick@us.ibm.com

Slideshare.net/Urbancode@EricMinick

Linked-in group:“Automating Deployment and Release”

Lean Software Delivery

Technology

Transcript of Lean Software Delivery

The Lean Project Delivery System: An Update - Lean Construction

Applying Lean to Software - Lean & Kanban 2009

Introduction to Lean Software Delivery - gotocon.comgotocon.com/dl/goto-zurich-2013/slides/ScottAmbler_IntroductionTo...Introduction to Lean Software Delivery Principles and Practices

“Achieving LEAN Project Delivery through … Lean Project Delivery...Agenda: Achieving LEAN Project Delivery through Modularization Modular is a Lean Construction Technique Using

Lean Application Delivery

Lean Software Developmen - Chalmers · Agile Development Processes 2 Lean Manufacturing Lean Product Development Lean Software Development Lean Software Developmen

Lean it and lean software factory

Agile & Lean for Project Delivery

Lean Software & Kanban Prof. Plattner, Dr. Uflacker ... · Lean Software & Kanban — Software Engineering II — WS 2016/17 Lean Software & Kanban Enterprise Platform and Integration

Lean Software Development

Lean software

UHS Lean Project Delivery Guide - Lean Construction Institute

Your Software: Faster. Stronger. Better....extends Agile and Lean principles to encompass the entire software delivery lifecycle. It involves numerous techniques, multiple roles within

Linbeck Lean Project Delivery

LEAN SOFTWARE DEVELOPMENT James Manning. Outline Lean History of Lean Lean Manufacturing Lean Software Development Where to start.

Lean Agile CMMI · development ! A Lean and Agile software development organization ! Operational Excellence is in our DNA " Culture of quality, predictable delivery, continuous

lean construction and integrated project delivery

Lean Software Developmentkena/classes/5828/s12/presentation... · Lean Software Development is an Agile practice that is based on the principles of Lean Manufacturing Lean Software

Software Process Improvement through the Lean Measurement ... · Software Process Improvement through the Lean ... Lean software development propagates two important ... Process Improvement

Lean Project Delivery - NASA · Lean Project Delivery Gregory A. Howell, P.E. Executive Director Center for Innovation in Project and Production Management ©Lean Construction Institute,