1 / 19

Lean or Agile - When to Use What? David Binnerts Shell Global Solutions

Lean or Agile - When to Use What? David Binnerts Shell Global Solutions. Conversation around. Process Management Lean, Pull Planning, Agile When to use what. Hands up, if you have ever used . Lean Pull Planning Agile. Continuous Improvement . Lessons from Business Process Redesign.

demily
Download Presentation

Lean or Agile - When to Use What? David Binnerts Shell Global Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lean or Agile - When to Use What?David BinnertsShell Global Solutions

  2. Conversation around • Process Management • Lean, Pull Planning, Agile • When to use what

  3. Hands up, if you have ever used • Lean • Pull Planning • Agile

  4. Continuous Improvement

  5. Lessons from Business Process Redesign • All work is process work • A process may be implicit, or explicit • Explicit processes allow us to: • Repeat the work consistently over time • Teach it to others • Measure the results of it • Improve it

  6. Explicit processes for improvement • Lean • Pull Planning • Agile

  7. Lean • Make use of Standard Operating Procedures (SOPs) • These provide a standard for the process • In order to identify a gap between goal and performance • A root cause analysis (5x Why) helps to identify waste • So teams can eliminate it • PDCA

  8. Pull Planning • Make work explicit and reduce lead time and waste in projects: • Buffers of non value adding waiting times • Waiting • Handovers • Inventory

  9. Pull Planning (cont) • Sometimes leads to an increase of: • Overprocessing (on planning time) • Overproduction (of documentation) • Rework (as schedules had to be adjusted, promises were still not kept, trades would not understand requirements and schedules from others, projects were not delivered as promised). • Talent (as team members were constantly chasing eachother)

  10. Agile Values • Individuals and interactions over processes and tools • Delivering a good end product over documentation • Collaboration over contract negotiation • Embracing change over sticking to the plan • And provides simple frameworks for delivering the work

  11. So, when would you use what?

  12. Stagegated vs. Agile

  13. Assess • Select • Define • Execute • Operate What’s each stage like?

  14. In Shell:

  15. Scrum Framework

  16. What’s each stage like?

  17. Pull Planning

More Related