Scaled Agile Framework of smoker…. Bad advices how to 100% fail SAFe

Содержание

1. Scaled Agile Framework of smoker…. Bad advices how to 100% fail SAFe
2. Who?8 years NGSSM experienceCertified SAFe consultant, practicing
3. What is Scaled Agile Framework?
4. Agile is a frameworkAgile is always equal
5. Bus effectBecause customer is asking for itBecause
6. SAFe is a pie, it’s easy!Do not
7. People does not matter!Do not train themDo
8. Scream instead of ScrumHold the team and
9. ContractsFix as much as possible (scope, money, etc.)Don’t think about details in SOW, Agile provide values
10. SAFe NOT on both sidesCustomer DO NOT
11. Mini-waterfallsWaterfall perfectly fit’s into Scrum \ Kanban
12. Force teamsNever ask teams what the best
13. Jokes a sideSAFe isn’t perfect and have
14. Слайд 14
15. Fin
16. Скачать презентанцию

Who?8 years NGSSM experienceCertified SAFe consultant, practicing Agile \ Scrum and Kanban over 5 years. Project ManagerScrum Master

Главная
Разное
Scaled Agile Framework of smoker…. Bad advices how to 100% fail SAFe

Слайды и текст этой презентации

Слайд 1Scaled Agile Framework of smoker….
Bad advices how to 100% fail

SAFe implementation

Слайд 2Who?
8 years NGSSM experience

Certified SAFe consultant, practicing Agile \ Scrum

and Kanban over 5 years.
Project Manager
Scrum Master

$Who?8 years NGSSM experienceCertified SAFe consultant, practicing Agile \ Scrum and Kanban over 5 years. Project ManagerScrum$

Слайд 3What is Scaled Agile Framework?

Слайд 4Agile is a framework
Agile is always equal Scrum
Agile is not

about mindset but about stupid values that nobody can measure

and understand \ share
Agile is buzzword that help sell contracts, nothing more

Agile is a frameworkAgile is always equal ScrumAgile is not about mindset but about stupid values that

Слайд 5Bus effect
Because customer is asking for it
Because counterparts using it
It’s

modern and fancy
If we will not start using, we

are all gonna die
I feel the pain, SAFe will fix it

Bus effectBecause customer is asking for itBecause counterparts using itIt’s modern and fancy If we will not

Слайд 6SAFe is a pie, it’s easy!
Do not ever hire SPC’s

Do not even try to be trained how to read

or use it
Always implement all layers (even if you do recognize that is useless)
Remove unnecessary roles or artifacts \ practices
Synchronization is unnecessary
After you would tired about Agile idea go to ‘V-type model’ (SAFe is adaptive to any sort of changes)
Forget about XP just do..

SAFe is a pie, it’s easy!Do not ever hire SPC’s Do not even try to be trained

Слайд 7People does not matter!
Do not train them
Do not ever pay

attention to feedback
Do net let them decide how product will

look like (act top to down as much as possible)
Do not care about motivation
Scrum Masters are useless
Program Increment do not require any context or details necessary for teams

People does not matter!Do not train themDo not ever pay attention to feedbackDo net let them decide

Слайд 8Scream instead of Scrum
Hold the team and support illusion of

control
Heightened project transparency (you will not do that)
Stability losses for

quick win
Grant managers not teams to speed up their career grow
More KPI’s to teams
Do ceremonies even if you don’t understand what is it for
Change Sprint and PI length when it’s needed

Scream instead of ScrumHold the team and support illusion of controlHeightened project transparency (you will not do

Слайд 9Contracts
Fix as much as possible (scope, money, etc.)
Don’t think about

details in SOW, Agile provide values

Слайд 10SAFe NOT on both sides

Customer DO NOT need understanding of

what we as supplier are doing
Never align about meanings and

values
Comfortable roles always on supplier side

SAFe NOT on both sidesCustomer DO NOT need understanding of what we as supplier are doingNever align

Слайд 11Mini-waterfalls

Waterfall perfectly fit’s into Scrum \ Kanban \ Lean frameworks

Act as you normally did before (don’t use XP or

try to implement new work order)
More management to management god

$Mini-waterfallsWaterfall perfectly fit’s into Scrum \ Kanban \ Lean frameworks Act as you normally did before (don’t$

Слайд 12Force teams

Never ask teams what the best way to implement

product, all is predetermined on mgmt. level.
Always do a formal

PI planning's, never ask for feedback, it’s not necessary.
Team should be represented on ALL PI planning's without exception, because it’s stated.
IP sprint is expensive and useless
SAFe is enough flexible to change priorities each sprint

Force teamsNever ask teams what the best way to implement product, all is predetermined on mgmt. level.Always

Слайд 13Jokes a side
SAFe isn’t perfect and have problems with feedback

on certain levels
Scrum teams mindset as well as RTE

require mature skills
SAFe hardly implementing in short term perspective
It’s mislead to copy top2down company structure
Distinguishing to levels is require a lot of synchronization
It is expensive!
In supplier case it’s not the best model to use
Attrition rate increase team delivery uncertainty and risks
Multiple vendors in train hardly to plan and synchronization and testing might be problematic.
Testing in ART hard to synchronize