what_are_the_changes_in_culture_that_need_to_happen_with_agile
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
what_are_the_changes_in_culture_that_need_to_happen_with_agile [2017/04/25 06:06] – hpsamios | what_are_the_changes_in_culture_that_need_to_happen_with_agile [2020/06/02 14:21] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== What Are The Changes in Culture That Need To Happen with Agile? ====== | ====== What Are The Changes in Culture That Need To Happen with Agile? ====== | ||
+ | |||
+ | <WRAP todo> | ||
The " | The " | ||
Line 11: | Line 13: | ||
^ Traditional Organization ^ Agile Organization ^ Role ^ Comments ^ | ^ Traditional Organization ^ Agile Organization ^ Role ^ Comments ^ | ||
| "Local optimization" | | "Local optimization" | ||
- | | Manage looking backward | Manage looking forward | Management | Traditional approach of managing by the numbers, focusing on “make the month” targets | + | | Manage looking backward | Manage looking forward | Management | Traditional approach of managing by the numbers, focusing on “make the month” targets, and working to determine what went wrong (and in the worst case finding someone to blame). This is essentially |
| Resource efficiency | Flow efficiency | Management | The focus with agile is on delivering business value as a smooth flow. This may mean that the best thing for people to do is not to be busy the whole time. Traditional management focuses on " | | Resource efficiency | Flow efficiency | Management | The focus with agile is on delivering business value as a smooth flow. This may mean that the best thing for people to do is not to be busy the whole time. Traditional management focuses on " | ||
| Large annual bets based on plan | Multiple small actively managed bets based on reality | Management | Traditional approaches to implementing an organization plan is to do a yearly plan, and then determine if we meet the plan. The agile approach assumes we have plans, but they are smaller, more regularly reviewed so we can more easily adapted based on the changing business situation. See [[why_should_we_start_without_doing_a_complete_analysis|Why Should We Start Without Doing a Complete Analysis? | | Large annual bets based on plan | Multiple small actively managed bets based on reality | Management | Traditional approaches to implementing an organization plan is to do a yearly plan, and then determine if we meet the plan. The agile approach assumes we have plans, but they are smaller, more regularly reviewed so we can more easily adapted based on the changing business situation. See [[why_should_we_start_without_doing_a_complete_analysis|Why Should We Start Without Doing a Complete Analysis? | ||
Line 63: | Line 65: | ||
| Status is assess through document (phase-gate) review | Status is assessed by seeing working code at cadence boundaries | PM | | | | 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 | | | | 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' | ||
</ | </ | ||
</ | </ | ||
Line 75: | Line 78: | ||
{{tag> | {{tag> | ||
- | |||
- | |||
- | ~~LINKBACK~~ | ||
- | ~~DISCUSSION~~ |
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/what_are_the_changes_in_culture_that_need_to_happen_with_agile.txt · Last modified: 2023/08/14 11:45 by hans