System Optimization by attacking Lean Waste
Most large scale organizations are designed on the overarching theme of local efficiency and local optimization. Local optimization focus can be seen at all levels and areas in such organizations right from hiring, approach to funding new initiatives, the way people are promoted to higher ranks, etc. Effects of such behavior is visible through organizational silos, hand-offs of partly finished work products among groups of SMEs, single function roles (such as Analyst, QA, etc.), everyone being busy, and communication barriers and distance from real user/customer challenges.
In this workshop, we'll focus on the Software Product Development area of the organizations, identify local optimization, expose the underlying lean wastes and list approaches to optimize the whole system and improve organizational agility.
Kamlesh Ravlani will help attendees see the prevailing local optimization by dissecting planning, analysis and design, and programming areas and will facilitate activities where the participants expose the underlying lean wastes.
Equipped with the knowledge of prevailing lean wastes and resulting local optimization, attendees will learn couple of approaches based on Systems Thinking that solely focus on customer value and remove lean wastes resulting in System Optimization. Attendees will also learn that System optimization also triggers and necessitates re-designing the organization to move away from local optimization in the benefit of the whole system optimization and allowing the organization to be more responsive and agile.
PS: As a reference, Kamlesh Ravlani will bring additional reference material and books for attendees to become aware and later refer to - if interested to learn further on this topic.
Outline/structure of the Session
- Agenda and Intro - 2 min
- Large Scale Organizational Design (and Local Optimization) - 10 min
- Lean Wastes - 6 min
- Cognitive Biases and Thinking Mistakes - 4 min
- 1st Dissection: Planning - 10 min
- Table activity to expose underlying Lean Wastes in planning - 4 min
- 2nd Dissection: Analysis and Design - 10 min
- Table activity to expose underlying Lean Wastes in analysis and design - 4 min
- 3rd Dissection: Programming - 10 min
- Table activity to expose underlying Lean Wastes in programming - 4 min
- Systems Thinking - 6 min
- Organizational redesign and System Optimization - 10 min
- Q&A - 10 min
PS: I'll be presenting this topic at at-least two venues including one International conference.before Agile India 2016
PSS: It's a complex subject and hands-on activity adds a tremendous value to the learning. Squeezing this session to a shorter 45 min talk doesn't seem a practically sound idea to me.
- Understand the Lean Wastes
- Identify Lean Wastes underlying the Large Scale Organizational Design
- Understand Cognitive Biases
- Identify Local Optimization in various organizational design areas
- Understand System Thinking
- Lean Organizational Design approach to Optimizing Whole System
Leaders, VPs, Directors, Agile Coaches, Change Agents, Product Owners, ScrumMasters
schedule Submitted 2 years ago
People who liked this proposal, also liked:
Richard Sheridan - Build a Workplace People Love – Just add JoyRichard SheridanCEOMenlo Innovations
schedule 2 years agoSold Out!
The CIO invited me into his office and closed the door. Before he took me for a tour of his operation, he had a few stories to share. Important stories. Last year’s project was a disaster. Late, lots of quality issues, in short, a failure in every dimension. His boss, the CEO, had just presented him with a very personal ultimatum: deliver the next project by April 4th, "or else".
"Or else what," I asked?
His team was burned out and scared. They were a hard-working and dedicated group, but fear and demoralization had set in and he didn't know what to do next. That’s why he wanted to talk to me, he had heard things about my company, things that seemed too good to be true, but he had to hear them firsthand. He wanted hope, inspiration, and a practical way to get there.
I told him about my own journey from joy to fear to disillusionment back to joy. It was simple, but, of course, simple isn’t easy. I wasn’t sure he and his organization were ready; "manufactured fear" is a powerful drug.
In this talk, I will share with you what I shared with him. I will explore what an intentionally joyful culture must choose as its focus. I will discuss what joy looks like, feels like, how it is organized. Along the way, you will be confronted by paradoxical approaches of how workplace noise increases productivity, how two people at one computer outperforms hero-based organizations 10-to-1, how rigor and discipline emanate from a shared-belief system, how transparency conquers fear, how all of the disciplines you study including agile, lean, and six sigma when done well are really about building human relationships at the intersections of business and technology, between project management and software development, between development and design and how quality can be a natural result of a team built on trust. This is not a theoretical talk, but rather a talk built from well over a decade of experience of leading a team focused on “the business value of joy”. There will be lots of room for discussion with the audience. The audience will begin to understand why thousands of people make the journey to Ann Arbor, Michigan every year to see The Menlo Software Factory firsthand, and why so many more are reading about it in Joy, Inc. – How We Built A Workplace People Love.
Ram Srinivasan - More with LeSS (Large Scale Scrum)Ram SrinivasanAgile Coach and Certified Scrum TrainerIndependent Consultant
schedule 2 years agoSold Out!
How do you effectively do Scrum when you need multiple teams to work on the same product? What kind of patterns and structures should we create to support empiricism and self-organization at scale? And how do you get started?
This session explores these questions by uncovering the rules, principles and guidelines behind Large Scale Scrum (LeSS). Ram Srinivasan also discusses the two LeSS frameworks and provides guidelines on which one may be more appropriate for you. You will learn how the role of management changes in a LeSS organization. Ram also will share his success and failure stories and will provide guidances on what will make your LeSS adoption more successful
Virender Kumar - Are Test Coverage Measurements Unnecessary in TDDVirender KumarSoftware ConsultantConsultant
schedule 2 years agoSold Out!
TDD is based on the premise that automated test is written before we write actual code. In such a scenario, we should be getting very high test coverage by default. I will discuss whether test coverage metrics have any significance in TDD paradigm using a sample program.
I will present an application developed using TDD from scratch. Using this application I will try to answer following questions:
- Do we get very high test coverage by default.
- Do test coverage measurements bring in any value in TDD
- Which coverage metrics might be useful