Companies need a sustainable model for leading continuous change - yet most leadership teams are too busy running the business to effectively lead change. Many transformation efforts fail due to false starts, organizational resistance, and a lack of effective governance. We will explore a strategic change project management model that has repeatedly resulted in successful ongoing change initiatives. The model draws on Agile and Lean principles and techniques to lead change initiatives in a way that is simple, provides focus and transparency, and builds trust.
Using agile and lean to lead business transformation agile 2010
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
Hinweis der Redaktion
IntroductionSituationInitial AssessmentIntroducing Kanban to the development organizationApproach to Achieving the Business ObjectiveIntroducing Kanban at the strategy execution levelCeremonies for the Strategy Execution KanbanResults of our effortApplication of Boyd’s O-O-D-A
merchandising offering went back in-house due to customer margin pressure and conflict of interest concerns; Remodeling and Construction were significantly down due to lack of investment by customers; leaving resets as the core business
Everything needed to be fixed. Within the timeframe we couldn’t fix the entire system – we need to focus on just the areas that we could change to achieve the strategy.
NPD has since moved to an online board – not visible on our board anymore.Switched payment for Defects from hours committed to hours moved to Done-DoneCore system WIP is limited from the strategy board – that’s nextBy the time the developers delivered anything – the business had moved on. Either solving it with a spreadsheet or deciding it wasn’t actually that important to fix. The problems would then reemerge later – repeating the same crisis over and over.
Everything needed to be fixed. Within the timeframe we couldn’t fix the entire system – we need to focus on just the areas that we could change to achieve the strategy.
Notice the result of the A3 shows three key standards to get work done.Outcome – Deliverables in the context of the problem & prioritized (isn’t this what we want from the business?)Sequence – what order do they need to be doneTiming – When will it be done (can be assigned at the last responsible moment)Owner - Coordination
Notice the result of the A3 shows three key standards to get work done.Outcome – Deliverables in the context of the problem & prioritized (isn’t this what we want from the business?)Sequence – what order do they need to be doneTiming – When will it be done (can be assigned at the last responsible moment)Owner - Coordination
Notice the result of the A3 shows three key standards to get work done.Outcome – Deliverables in the context of the problem & prioritized (isn’t this what we want from the business?)Sequence – what order do they need to be doneTiming – When will it be done (can be assigned at the last responsible moment)Owner - Coordination
Notice the result of the A3 shows three key standards to get work done.Outcome – Deliverables in the context of the problem & prioritized (isn’t this what we want from the business?)Sequence – what order do they need to be doneTiming – When will it be done (can be assigned at the last responsible moment)Owner - Coordination
Notice the result of the A3 shows three key standards to get work done.Outcome – Deliverables in the context of the problem & prioritized (isn’t this what we want from the business?)Sequence – what order do they need to be doneTiming – When will it be done (can be assigned at the last responsible moment)Owner - Coordination
Notice the result of the A3 shows three key standards to get work done.Outcome – Deliverables in the context of the problem & prioritized (isn’t this what we want from the business?)Sequence – what order do they need to be doneTiming – When will it be done (can be assigned at the last responsible moment)Owner - Coordination
Notice the result of the A3 shows three key standards to get work done.Outcome – Deliverables in the context of the problem & prioritized (isn’t this what we want from the business?)Sequence – what order do they need to be doneTiming – When will it be done (can be assigned at the last responsible moment)Owner - Coordination
Today, the line managers are more interested because they need to move their card to execution – defects often still linger in acceptance.
Development and deployment was iterative. Basics in place at kick off. Continued to refine and deploy enhancements in flight. Despite lack solid engineering practices. Aggressively followed up daily on use of the system.The engagement has been extended and the contingency will be paid
OODAMilitary strategist Colonel John Boyd described the OODA loop for fighter pilots. It has since been applied to define the Marine Corps Doctrine in Maneuver warfare. Chet Richards applies it business strategy in Certain To Win. The primary concept is to expend the least resource to accomplish the next objective and to operate at a decision cycle faster than your competition can achieve. This allows you to go farther and faster than your competition.Unfortunately, it can not as simple as “observe, then orient, then decide, then act.” In fact such a sequential model would be very ponderous and would not well describe how successful competitors operate.The key to quickness turns out to be the two “implicit guidance and control” arrows at the top. In other words, most of the time people and groups do not employ the explicit, sequential O-to-O-to-D-to-A mechanism. Most of the time, they simply observe, orient, and act. There is data coming out to support this (see Gary Klein’s book, Sources of Power.)The question, of course, is, “What action?” A thinking opponent doesn’t provide us with a laundry list of his tactics so we can work out responses in advance. The mechanism which handles this uncertainty and makes the loop function in a real world situation is “Orientation.”As we suck in information via the “Observe” gateway, it may happen that we notice mismatches between our orientation and what we’re observing in the real world. If we don’t spot these mismatches and correct our orientation, the actions that flow from it may not be as effective as we intend. This can open up opportunities for our opponents. Boyd’s concept of strategy places heavy emphasis on attacking the other side’s orientation to open up just these kinds of opportunities, and he suggests many ways to do this.Note that “OODA” speed is quite different from the speed of our actions. Doing something dumb or irrelevant, but doing it at high speed, may not provide much of a competitive advantage.The “Decision/hypothesis” block is the learning part of the loop, where we experiment and in the process add new actions to the Implicit Guidance and Control link. You can also think of it as programming orientation for future intuitive actions.