Hola!

#agileIIMN

About me
Agile & Technical Coach
Consultant & trainer
Lego Serious Play
@josecgil

Its not about...

Practices or tools
Boards, post-it, standups, games...

What?

Its about
principles...

 and Values

PRODUCT?

Computing

Manufacturing

Most common
methods

Kanban
Make work visible
Limit WIP
Measure flow
Explicit rules
Feedback loops
Evolve experimentally

Lets go back
to the example

Org Context
300 people
Catalog sales to web
Rebranding
Labour Force Adjustment (ERE)

The project
Web redesign & rebuild
A company challenge
Not only Marketing & Tech

Background
Previous mobile web
made using Scrum
It may seems the same
but it was not a
company effort

The project begins

Agile Inception
40 people
10 exercices
1 full day
Outside the company

Product Box

Not List

How Long? How Much?

Results
Know whats in/out: web,
brand, process change...
Shared vision
Too many people

The team
3 Full Stack Devs
1 Frontend Dev/UX
1 QA/UX
2 Part-time Designers
1 Product Owner

Time & Space

Dedicated space for the team
Product Owner co-located
100% of time devoted to
project

Team Organization
Kanban:
Business, Design & Front End
Scrum:
Development & Acceptance Test
2 weeks Sprints

Business
UX

Design

Front End

Development

Acceptance Test

Everything is good
High quality of deliverables
Better business organization
High team morale
Customer satisfaction

Why?

Command & Control

exercise of authority [...] by a
properly designated [individual] over
assigned [resources] in the
accomplishment of a [common goal]
As defined by
North Atlantic Treaty Organization (NATO)

Industrial

Knowledge

Cmd & Ctrl

Self Org

One brain

Many brains

Slow decision chain

Fast decision chain

No idea

Know how

Demotivated

Motivated

Self organizing team

Pulling work
Solving conflicts internally
Improving process by themselves
Suggesting solutions
Delivering value

Is for every team?

Requires maturity
Skills / Knowledge
Motivation / Ambition

Quality at the
source
Root cause
Testing

Pair working

Mob working

Demo
Every 2 weeks we
show and deliver a
product that
works and is
better than before.

Retrospective
Transparency
Continuous improvement

Informal meetings
As soon as a problem
arises
Anyware
Fast decision or
Last responsible moment

No problems
then?

ERE
Every 5 weeks 1 off
Pair / Mob Working
Visual management
Self organization

Training
Not everyone in the
team knew well
Scrum / Kanban.
Internal Training

More cowbell
Management wants
speed / more people
Maximizing the amount
of work not done
Release early, release
often

Wisdom of the elders

Adding manpower
to a late software
project makes it
later
Frederick P. Brooks

Wisdom of the elders

Nine women cant
make a baby in one
month
Frederick P. Brooks

Delivery date
Continuous delivery
Prioritize
Create options
Visualize the work
Contrast with

To conclude

Agile has practices...

...but is about
Principles & Values

Your team is
your product

Thanks!

Questions?

@josecgil
josecgil@smokingbrains.com