Scaled Agile Framework of smoker…

Сентябрь 4, 2022

Главная
ОБЖ
Scaled Agile Framework of smoker…

Содержание

2. Who? 8 years NGSSM experience Certified SAFe consultant, practicing Agile \ Scrum and Kanban over 5
3. What is Scaled Agile Framework?
4. Agile is a framework Agile is always equal Scrum Agile is not about mindset but about
5. Bus effect Because customer is asking for it Because counterparts using it It’s modern and fancy
6. SAFe is a pie, it’s easy! Do not ever hire SPC’s Do not even try to
7. People does not matter! Do not train them Do not ever pay attention to feedback Do
8. Scream instead of Scrum Hold the team and support illusion of control Heightened project transparency (you
9. Contracts Fix as much as possible (scope, money, etc.) Don’t think about details in SOW, Agile
10. SAFe NOT on both sides Customer DO NOT need understanding of what we as supplier are
11. Mini-waterfalls Waterfall perfectly fit’s into Scrum \ Kanban \ Lean frameworks Act as you normally did
12. Force teams Never ask teams what the best way to implement product, all is predetermined on
13. Jokes a side SAFe isn’t perfect and have problems with feedback on certain levels Scrum teams
16. Скачать презентацию

Слайд 2

$Who? 8 years NGSSM experience Certified SAFe consultant, practicing Agile \$

Who?
8 years NGSSM experience
Certified SAFe consultant, practicing Agile \ Scrum and

Kanban over 5 years.
Project Manager
Scrum Master

Слайд 3

What is Scaled Agile Framework?

Слайд 4

Agile 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

Слайд 5

Bus 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

Слайд 6

SAFe 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..

Слайд 7

People 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

Слайд 8

Scream 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

Слайд 9

Contracts
Fix as much as possible (scope, money, etc.)
Don’t think about details

in SOW, Agile provide values

Слайд 10

SAFe 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

Слайд 11

$Mini-waterfalls Waterfall perfectly fit’s into Scrum \ Kanban \ Lean frameworks$

Mini-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

Слайд 12

Force 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

Слайд 13

Jokes 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

Слайд 14