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 revisionLast revisionBoth sides next revision | ||
what_are_the_changes_in_culture_that_need_to_happen_with_agile [2018/12/03 19:33] – Added todo hpsamios | what_are_the_changes_in_culture_that_need_to_happen_with_agile [2020/06/10 12:53] – ↷ Links adapted because of a move operation hans | ||
---|---|---|---|
Line 13: | 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? | ||
- | | " | + | | " |
| Efficiency | Effectiveness | Management | According to Peter Drucker " | | Efficiency | Effectiveness | Management | According to Peter Drucker " | ||
- | | " | + | | " |
| " | | " | ||
| "Iron triangle is scope, cost and schedule" | | "Iron triangle is scope, cost and schedule" | ||
| Solution focus - "Bring me solutions, not problems" | | Solution focus - "Bring me solutions, not problems" | ||
- | | "Do it right first time" | "Fail fast" | Management | Why fail fast? Would you prefer to find out that we went in the wrong direction at the end of the project, or close to the beginning? Traditional approaches mean you only find out at the end of the project that there is a problem. See [[blog:how_can_we_understand_the_real_value_of_fast_feedback_and_deciding_late|How Can We Understand the Real Value of Fast Feedback and Deciding Late?]] | | + | | "Do it right first time" | "Fail fast" | Management | Why fail fast? Would you prefer to find out that we went in the wrong direction at the end of the project, or close to the beginning? Traditional approaches mean you only find out at the end of the project that there is a problem. See [[how_can_we_understand_the_real_value_of_fast_feedback_and_deciding_late|How Can We Understand the Real Value of Fast Feedback and Deciding Late?]] | |
| "Best practices" | | "Best practices" | ||
| "Phase gate reporting" | | "Phase gate reporting" | ||
- | | "Bring project back on plan" | "Plan will evolve based on what we know" | Management | Lets face it, plan was put together when we knew the least about the project we were undertaking so it is safe to assume the plan is flawed. See also [[blog:how_can_we_understand_the_real_value_of_fast_feedback_and_deciding_late|How Can We Understand the Real Value of Fast Feedback and Deciding Late?]] and [[blog:why_doesn_t_traditional_project_management_work_for_software_projects|Why Doesn' | + | | "Bring project back on plan" | "Plan will evolve based on what we know" | Management | Lets face it, plan was put together when we knew the least about the project we were undertaking so it is safe to assume the plan is flawed. See also [[how_can_we_understand_the_real_value_of_fast_feedback_and_deciding_late|How Can We Understand the Real Value of Fast Feedback and Deciding Late?]] and [[why_doesn_t_traditional_project_management_work_for_software_projects|Why Doesn' |
| "Test quality into the product" | | "Test quality into the product" | ||
| "Get 'r done" | " | | "Get 'r done" | " | ||
| " | | " | ||
| " | | " | ||
- | | "Make decisions early" | "Make decisions at last responsible moment" | + | | "Make decisions early" | "Make decisions at last responsible moment" |
| " | | " | ||
| " | | " | ||
Line 40: | Line 40: | ||
| "Late learning" | | "Late learning" | ||
| " | | " | ||
- | | " | + | | " |
| " | | " | ||
| "Cost focus" | "Value focus" | Management | Traditional model is based on cost accounting with little discussion of the value we get as a result of this. Agile changes model to focus on value delivery, where value, as in " | | "Cost focus" | "Value focus" | Management | Traditional model is based on cost accounting with little discussion of the value we get as a result of this. Agile changes model to focus on value delivery, where value, as in " |
/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