@AgilePT 2016 - HyP: A journey to greater efficiency

Agenda
HyP – A journey to greater efficiency
Story
Paterns
Results
Self-Organization
Testimony
Conclusions

Who am I?
Hi, I’m Bruno (Cacho) Teixeira
Agile Coach @Farfetch
Scrum Master @Farfetch
Community
Co-Founder @Xekin
Co-Founder @ScrumPortugal
Twitter: @bruno_cacho
Linkedin: linkedin.com/in/brunocacho
Site: www.xekin.org
www.scrumportugal.org

Unicorn is Born
Story

Young Unicorn Hunger for Growth
Story

Wisdom
Story
“We need to haunt the
house of history and
listen anew to the
ancestors' wisdom”
Maya Angelou

Search for Ancestors’
Story

ScrumPLoP® - Scrum Pattern Community
Story
Jeff Sutherland Co-Creator of Scrum @Scrum, Inc
A Pattern Language for Hyperproductivity

Initiative Support
Story

Mission
Story
Transform Farfetch’s Frontend into the first
Portuguese “Hyper Productive” Cluster of
Software Engineers.

Reading Sessions
Story

Simulation Sessions
Story

Start
Story

First HyP Daily
Story

Collective Emoticon
Story

Structure
Patterns
Get Ready
Stable Teams
Yesterday’s
Weather
Get Finished
Swarming
Interrupt Pattern
Daily Clean Code
Emergency
Procedure
Get
Hiperproductive
Scrumming the
Scrum
Happiness Metric
Teams That Finish
Early, Accelerate
Faster

Stable Team
Patterns [Get Ready]

Stable Team
Keep teams stable and avoid shuffling people between teams.
Stable teams tend to get to know their capacity, which makes it
possible for the business have some predictability.
“Being flexible in shifting people NEED to change to being flexible
with work.”

Yesterday's Weather

Yesterday's Weather
In most cases, the number of Estimation Points completed in the last
Sprint is the most reliable predictor of how many Estimation Points
will be completed in the next Sprint.
“Running Average Velocity Using running average of at least THREE
Sprints to calculate the velocity of next Sprint”

Swarming: One-Piece Continuous Flow
Patterns [Get Finished]

Swarming: One-Piece Continuous Flow
Focuses maximum team effort on one item in the Sprint Backlog to get it
done as soon as possible.
Whoever takes this item is Captain of the team. Everyone must help the
Captain if they can and no one can interrupt the Captain.
“Multitasking makes you stupid as well as slow. Gives the illusion that
things are going faster, but this increases defects.”

Illegitimus Non Interruptus

Illegitimus Non Interruptus
Allot time for interruptions and do not allow the time to be exceeded.
“In almost all cases, it is desirable to have the Scrum Team “eat their
own dog food.” If they produce a defect that gets into the field they
need to fix it as soon as possible.”

Daily Clean Code

Daily Clean Code
“... bugs turn into features at midnight ...”
Fix all bugs in less than a day. Aim to have a completely clean base
of code at the end of every day.
“The consistent quality of the code is probably the major contributor
to the improvement in velocity.”

Emergency Procedure

Emergency Procedure
When high on the burndown try a technique used routinely by pilots.
When bad things happen, execute the emergency procedure
designed specifically for the problem.
“Do not delay execution while trying to figure out what is wrong or
what to do.”

Scrumming the Scrum
Patterns [Get HyPerproductive]

Scrumming the Scrum
Identify the single most important impediment in the Sprint Retrospective
and remove it before the end of the next sprint.
To remove the top priority impediment, put it in the sprint backlog as a
user story with acceptance tests that will determine when it is done.
“This pattern assures continuously increasing velocity or sustainable
high-level velocity”

Happiness Metric

Happiness Metric
Find out what one improvement will increase the happiness of the team
the most, and implement that improvement in the next sprint.
Happiness is one of the best metrics because it is a predictive indicator.
“They can see how it will impact them personally, so they are more likely
to work harder to accomplish the improvement.”

Teams that Finish Early Accelerate Faster

Teams that Finish Early Accelerate Faster
Teams often take too much work into a sprint and cannot finish it.
Failure prevents the team from improving.
Therefore, take less work into a sprint. Maximize your probability of
success by using the pattern Yesterday’s Weather.
“Managers pressure teams because they lack basic understanding of
lean practices.”

Efficiency KPIs
Quantity as Software delivered [Pts] => #Points delivered on team’s DoD
Quality as defects detected [Def] => #Bugs Live
Time to Market as Cycle Time [Ttm] => #Hours spent to DoD
Results
[Team A]
43% Increase in avg points DoD deliver
12% Decrease in avg Bugs Live
59% Decrease in avg DoD Cycle Time
[Team B]
168% Increase in avg points DoD deliver
26% Decrease in avg Bugs Live
62% Decrease in avg DoD Cycle Time

Emergent Boards
Self-Organization
1 2
3
4

Emergent Boards
Self-Organization
1
2
3

Mob Programming
Self-Organization

Learning Dojos
Self-Organization

Different Ways of Work
Self-Organization

Pedro Martins
The belief in the value of scrum patterns controled one’s
natural scepticism about HyperProductivity, but seeing
the way the work flowed right on the first sprint
removed any doubt I could have.
The PO got predictability.
The QA got a regular work pace.
The Devs worked closer together.
And the team got happier.
Testimony
Product Owner

Hugo Galvão
If I have to pick one single word to describe this journey
the word would be amazing.
It was mind-blowing to see the change in the team’s
mindset to swarm in each story and the combined efforts
to grab a task from the beginning to the end in order to
deliver business value in record time improving on every
sprint the amount of work done.
Testimony
Product Owner

Rui Felgueiras
It's been amazing to see the (r)evolution since HyP was
first presented by Bruno.
It brought us another vision from agile and the solution
to multiple problems that we had.
All teams seem to work really well collaborating with
each other in many more ways.
Testimony
Lead Developer

João Madureira
The thing I liked the most about HyP was applying the
Swarming pattern. By having the whole team involved in
solving each problem we can benefit from everyone‘s
strengths.
Testimony
Lead Developer

Andreia Melo
I felt more connected to the team because the work was
really shared and the feeling of being only a part of a
pipeline disappeared.
Suddenly I was not the team bottleneck anymore
because the user stories were not stacked for testing.
It is really confortable to work on a smooth environment
and see the stories coming out faster.
Testimony
Software Tester

Sónia Liquito
Quality Assurance Tester was my role back then, but I wasn’t able
to do my work with quality, mostly because all user stories arrived
for testing late in sprint and all at the same time.
HyP Effect:
• No more bottlenecks in Testing Phase.
• More engagement of all members in all the phases of
development.
• More productive dailies, because every team members already
knows what each one of us did in the day before.
• More independent as a team.
Testimony
Software Tester

Wilson Alberto
I believe the most important part of HyP is the
collaboration it enforces.
Members of different areas of development can
collaborate and learn easily by sharing knowledge and
stepping out of their comfort zones.
Testimony
UI Developer

Vitor Subtil
Love the swarmming concept.
It allowed us to share business knowledge, produce
better code and strength team spirit.
It also helps keeping a stable team. We respect and
care for each others.
Testimony
Developer

Alberto Gomes
For me HyP is mainly about 2 concepts:
• Swarming: Through Swarming we have more interaction and
better knowledge share.
• Captain: Captain Concept is important because prevents work
to be interrupted. This is essential to keep focus.
A final note on Dailies, finally I understand the Daily Meeting
purpose.
HyP journey allowed me to witness a mindset transformation from
reporting to self-organization. HyP made our dailies to be focused
on team organization and efficiency.
Testimony
Developer

Mário Barbosa
HyP has been an innovative experience, which provides
a new way of looking at software development.
It’s main advantages are:
• Opportunity to create bonds with your peers
• Knowledge sharing and team evolution
• Continuous code reviewing and improvement
• Enables a faster and more precise sharing of ideas
and goal achievement
Testimony
Developer

João Pinto
HyP is all about collaboration and Team work.
My team started acting as one, united on the same goal:
deliver more, faster and better software
We achive this by improving the quality of our dailly
meeting, reducing its duration, promoting dojos and pair
programming.
Testimony
Developer

João Santos
As HyP was being introduced in the team at the same
time I was starting my role as a developer in Farfetch,
the Swarming concept was extra important for me and
it allowed me to gain vital knowledge from my peers
about the applications on which I would be working on.
Working closely with my colleagues, also increased my
adaptation to the team / company on a personal level.
Testimony
Developer

Great Team Experience
Stable Teams and Swarming are key Patterns in order to be sucessfull
LifeCycle Evolution enhables Continuous Deploy implementation
Team’s working habits, mindset and culture are ready to CI and CD
Conclusions

Relations and Synergies will, ultimately,
be reflected on code quality.
Conclusions

Scrum Pattern Community - http://www.scrumplop.org/
Stable Teams - https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/stable-teams
Yesterday's Weather - https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/estimation-points/yesterday-s-weather
Swarming: One-Piece Continuous Flow - https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/swarming--one-piece-continuous-flow
Daily Clean Code - https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/daily-clean-code
Emergency Procedure - https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/emergency-procedure
Scrumming the Scrum - https://sites.google.com/a/scrumplop.org/published-patterns/retrospective-pattern-language/scrumming-the-scrum
Happiness Metric - https://sites.google.com/a/scrumplop.org/published-patterns/retrospective-pattern-language/happiness-metric
Teams that Finish Early Accelerate Faster - https://sites.google.com/a/scrumplop.org/published-patterns/retrospective-pattern-language/teams-that-finish-early-accelerate-faster
https://www.scruminc.com/new-scrum-the-book/
https://www.scruminc.com/scrum-metrics/
References

@AgilePT 2016 - HyP: A journey to greater efficiency

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (13)

Ähnlich wie @AgilePT 2016 - HyP: A journey to greater efficiency

Ähnlich wie @AgilePT 2016 - HyP: A journey to greater efficiency (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

@AgilePT 2016 - HyP: A journey to greater efficiency

Hinweis der Redaktion