Differences

This shows you the differences between two versions of the page.

--- what_are_the_changes_in_culture_that_need_to_happen_with_agile [2017/03/19 16:31] – hpsamios
+++ what_are_the_changes_in_culture_that_need_to_happen_with_agile [2018/12/03 19:33] – Added todo hpsamios
@@ Line 1: / Line 1: @@
 ====== What Are The Changes in Culture That Need To Happen with Agile? ======
-Note: this discussion is closely related to [[what_are_the_changes_in_management_approach_that_need_to_happen_with_agile|What Are The Changes in Management Approach That Need To Happen with Agile?]]
+<WRAP todo>Work in progress</WRAP>
-The "inability to change the organization culture" is listed by most people as the biggest obstacle to implementing a Scrum / Agile approach. Here is a more detailed list of some of the culture changes that need to be made for an organization to become more agile in it approach:
+The "inability to change the organization culture" is listed by most people as the biggest obstacle to implementing a Agile approach.
+Some wit once said "if you think agile is simple, just try it". The basics of Agile are pretty simple (a focus on people and collaboration, continuous improvement through feedback, iterative and incremental delivery of value, etc). The problem is that while this is pretty simple, the result in your complex organization, when adopted is far from simplistic. What you see is the effect of "network effects" - small changes that ripple through your entire system and impact "everything" from governance, management, finance, budgeting, HR, architecture, and so on.
+Someone once asked me "what kinds of changes are we talking about?" The chart below captures some of the changes we see. Of course, "your mileage may vary". You will find that some these are bigger deals in your environment, while others just make sense and you will have no problem implementing thinking in your organization.
 <searchtable>
@@ Line 61: / Line 65: @@
 | Status is assess through document (phase-gate) review | Status is assessed by seeing working code at cadence boundaries | PM | |
 | Release date determined by wishful thinking | Release dates are fixed - manage scope expectations | PM | |
+| Meetings / events / reports happen at convenience of manager | Meetings / events / reports happen at convenience of team / train | Manager | This is part of servant leadership. Idea is to ensure that management doesn't slow the team / train down. |
 </sortable>
 </searchtable>
@@ Line 69: / Line 74: @@
   * [[https://findingmarblesdotcom.files.wordpress.com/2011/12/agile_mindset.jpg|Excellent graphic describing some of the transitions from the perspective of traditional project management viewpoint]]
   * FYI: I expect to edit this list as I figure out better ways of saying things and identify other changes that are required. And I expect to focus this list and edit it to make it more concise as it is pretty lengthy at the moment.
+  * This discussion is closely related to [[what_are_the_changes_in_management_approach_that_need_to_happen_with_agile|What Are The Changes in Management Approach That Need To Happen with Agile?]]
-Note: page is getting big so need to refactor. Perhaps based on "things that are general" vs "things that a coach would need to change"?
 {{tag>Consultant Tools CultureChange Organization FAQ PresentationIdea ToDo}}
-~~LINKBACK~~
-~~DISCUSSION~~