Agile GameChangers@marekkirejczyk

DISCLAIMERThose are my personal opinions, different coaches and trainers opinions might differ.

4 LEVELS

1. Process !

2. Technical practises

3. Product (focus on value)

4. SCALE: Alignment & Communication

LEVEL 1Process

PROCESSKANBAN

KANBAN

• Who is doing what?

• What are the priorities?

• When will it be done?

• “I thought something else need to be done”

• We don’t have time to fix bugs

“It’s better to ask for forgiveness then for

permission”

WANT TO LEARN MORE?• Yes we Kanban

• Get Kanban with GetKanban

Tomasz Łasica Mateusz Srebrny

SCRUM

SCRUM

• Continuous improvement

• Better communication to stakeholders

WANT TO LEARN MORE?S c r u m P r i m e r Introduction to Scrum

Michał Prządka

SCRUM PATTERNS

SCRUM Patternswww.scrumplop.org

JEFF sutherland

SCRUM SHOCK

THERAPY

Scrum shock therapy JEFF sutherland

• Everyone is trained in Scrum

• One week sprints

• All ceremonies together up to 4 hours

• Stop when team delivers 3 commitments in a row

• … blah blah blah

• Discipline!

• (it is not as bad as it sounds)

Release cycle

“Nothing improves a team morale more than a

release to production”

LEVEL 2Technical PRACTICES

Implementing• Training is good, change agent is much better

• Code DOJO is a good start

• There is no better way then pair programming

• Code Review is good (later)

• Technical debt will take consistent effort over time to get rid of

WANT TO LEARN MORE?e X t r e m e Programming (XP) for beginners

Jakub Nabrdalik

LEVEL 3Project vs.product teams

AIM!

project team WORKING SOFTWARE

PRODUCT team VALUE!

PROJECT team WORKING SOFTWARE

DID A GOOD JOBPROJECT TEAM:!!• NO BUGS !

• DELIVERED FAST !

• WHAT PRODUCT OWNER WANTED

PRODUCT TEAM:!!• MONEY! … or !

• Validated learning !

• GROWTH • CONVERSIONS • FREE TRIALS • REVENUE

TEAM MEMBERSPROJECT TEAM!

!• DEVELOPERS • TESTERS • DESIGNERS !!!!

PRODUCT TEAM:!!ALSO:!• MARKETING • SALES • OTHER…?

!

PROCESSPROJECT TEAM!!

• SCRUM • KANBAN • EXTREME

PROGRAMMING

PRODUCT TEAM

• LEAN STARTUP • EVO

!!!!

MEASURE OF PROGRESSFUNNELBURN DOWN CHART

WANT TO LEARN MORE?The Lean Startup in a corporate practice – validate or die

Agata Czopek

WANT TO LEARN MORE?Lean Startup for Agile Product Management

Ángel Medinilla

LEVEL 4Scale

Scale PROCESS• You can scale Scrum with LeSS

• Kanban Scale it selfs nicely

WANT TO LEARN MORE?Scaling Scrum with LeSS

Marek Kirejczyk

WANT TO LEARN MORE?War stories about S c a l e d A g i l e Framework

Tomek Pająk

Alignment

V2MOM• VISION - What is overall vision

• VALUES - What are our values

• METHODS - What specific methods will I use

• OBSTACLES - What may stop me?

• MEASUREMENTS - How will we know if we achieved a goal? (or in what %?)

V2mom - NOTES

• CEO starts, then everybody negotiate his V2MOM

• Usually done once a quoter

• I like to stop on team level (by Karol Traczykowski)

WANT TO LEARN MORE?5 reasons to use V2MOMs a t you r company

Karol Traczykowski

Summary

4 levels of (my) agile implementation

1. SPEED 1: Process

2. SPEED 2: Technical practises

3. BUSINESS FOCUS: Product teams

4. SCALE: Alignment & Communication

4 levels waste1. SPEED 1: We estimate bad, communicate bad, we

have unfinished features

2. SPEED 2: We have bugs, we deliver slower then we could

3. BUSINESS FOCUS: We build what our customers don’t want to pay for

4. SCALE: We lose all above, because of our scale

4 levels of EMPOWERMENT

1. SPEED 1: Team create it’s own process (improve)

2. SPEED 2: Team aims for Technical excellence (Software craftsmanship)

3. BUSINESS FOCUS: Team improves business

4. SCALE: Teams can still do all of above while growing

4 levels of lazy jobs1. Scrum Master has little to do

2. Team Leader has little to do

3. PO has little to do

4. CEO has little to do