if_we_doing_agile_at_scale_we_must_adopt_safe_anti-pattern
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| if_we_doing_agile_at_scale_we_must_adopt_safe_anti-pattern [2020/06/01 09:22] – Renamed to be more useful hpsamios | if_we_doing_agile_at_scale_we_must_adopt_safe_anti-pattern [2021/12/10 06:31] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== If We Doing Agile at Scale We Must Adopt SAFe (Anti-pattern) ====== | + | ====== If We Are Doing Agile at Scale We Must Adopt SAFe (Anti-pattern) ====== |
| + | |||
| + | Or "The answer is SAFe; now what was the question?" | ||
| + | Or "We Need to Go SAFe Now!" | ||
| ====== Consumer ====== | ====== Consumer ====== | ||
| Line 19: | Line 22: | ||
| ====== Impact ====== | ====== Impact ====== | ||
| - | Let’s be clear, there is nothing wrong with SAFe. SAFe captures good values, principles, and practices, that are the gathered up the results of a number real world experiences. And we are using the framework in many situations. | + | Let’s be clear, there is nothing wrong with SAFe. SAFe captures good values, principles, and practices, that are the gathered up the results of a number real world experiences. And I've used the framework in many situations. |
| The problem is that like all frameworks, it is a tool, and sometimes tools are used in the wrong context, and even if the context is applicable, the tools can be misapplied which do not produce the expected result or worse result in outcomes that you’ll regret in the future. | The problem is that like all frameworks, it is a tool, and sometimes tools are used in the wrong context, and even if the context is applicable, the tools can be misapplied which do not produce the expected result or worse result in outcomes that you’ll regret in the future. | ||
| Line 47: | Line 50: | ||
| * Pure operations group wanting to go SAFe. There were two problems here. Firstly the group represented about 3 teams which really meant the SAFe bureaucracy was overkill. The second problem was that a lot of the work was incident management and so difficult to plan to a cadence. Organization went more DIY approach, growing into the structure they needed, and reporting good results (especially around work visibility). | * Pure operations group wanting to go SAFe. There were two problems here. Firstly the group represented about 3 teams which really meant the SAFe bureaucracy was overkill. The second problem was that a lot of the work was incident management and so difficult to plan to a cadence. Organization went more DIY approach, growing into the structure they needed, and reporting good results (especially around work visibility). | ||
| - | # Want To Know More? | + | ====== |
| - | * [[blog:why_should_we_work_harder_to_eliminate_the_effect_of_dependencies|Why Should We Work Harder to Eliminate the Effect of Dependencies? | + | |
| + | | ||
| * [[what_is_the_benefit_of_having_a_cadence_of_meetings_etc|Why Do We Establish a Cadence of Events?]] | * [[what_is_the_benefit_of_having_a_cadence_of_meetings_etc|Why Do We Establish a Cadence of Events?]] | ||
| + | |||
| {{tag> | {{tag> | ||
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/if_we_doing_agile_at_scale_we_must_adopt_safe_anti-pattern.1591028560.txt.gz · Last modified: 2020/06/02 14:31 (external edit)