Planning, scaling and flowing within your agile organization

© Torak, Inc. www.torak.com
Planning, Scaling and
Flowing within your Agile
Organization

About Dimitri Ponomareff
Dimitri Ponomareff (www.linkedin.com/in/dimka5) is a Coach. Whether it's a sports team, software
products or entire organizations, Dimitri has that ability to relate and energize people. He is consistently
recognized as a very passionate and successful change agent, with an overwhelming capacity to motivate
and mobilize teams on their path to continuous improvements. He is a master facilitator, as well as a
captivating speaker with consistent, positive feedback regarding his ability to engage an audience.
As a certified Coach, Project Manager and Facilitator of "The 7 Habits of Highly Effective People",
Dimitri brings a full spectrum of knowledge in his delivery of methodologies. Through teaching by
example, he is able to build teams of people who understand where to focus their work to generate the
most value.
He has coached and provided tailor-made services and training for a multitude of organizations. The
short list includes, American Express, Charles Schwab, Bank of America, Morgan Stanley,
Choice Hotels International, JDA Software, LifeLock, First Solar, Mayo Clinic and Phoenix
Children's Hospital. Dimitri enjoys his work, and does everything to ensure he shares his knowledge
with others who seek it.

Organizational agility...
is the ability of an organization to effectively sense and
adapt in complex, rapidly changing conditions so that it
can thrive as an organization.
Plan to achieve your goals
Scale to increase your productivity
Flow to gain the most efficiencies

It’s all about communication
People who want IT must
communicate with people who can
build IT.

The Third Wave of Agile
http://www.solutionsiq.com/the-third-wave-of-agile/

Plan
● The 5 levels of planning
● Planning traceability
● Let’s play Plinko!

The 5 levels of Planning in Agile

Planning Traceability
Vision
Roadmap
R1 R2 R3 Rn
Release 1
SP1
Iteration 1
ST1 STnST3ST2
Iteration n
ST1 STnST3ST2
Story 1
T1 TnT3T2
Story n
T1 TnT3T2
SPnSP3SP2
Release n
SP1 SPnSP3SP2

Let’s play Plinko...

Scale
● Scrum of Scrums
● Scrum at Scale
● Large Scale Scrum (LeSS)
● Disciplined Agile Delivery (DAD)
● Scaled Agile Framework (SAFe)

Scaling Scrum
“Scaling Scrum means getting rid of stuff
because everything in Scrum is just in time, just
enough,…and because any extra weight slows
you down and increases cost. ”
– Jeff Sutherland
Sutherland, Jeff. “Scaling Scrum – What People Are Not Talking About!”
http://www.scruminc.com/scaling-Scrum-what-people-are-not/

Scrum of Scrums
Each Scrum team identifies one person who attends the Scrum of Scrums
meeting to coordinate the work of multiple Scrum teams.

Scrum at Scale framework
● It’s a minimal extension of the core Scrum framework
● Modularity is the key, by allowing context-driven
solutions and processes
○ Modularity allows versatility
○ Scrum is modular
○ Deploying incrementally is easier
○ Modularity supports a pattern library

Modular Framework for Scrum at Scale

Large Scale Scrum (LeSS)

Large Scale Scrum (LeSS)
LeSS is a scaled up version of one-team Scrum, and it maintains many of the
practices and ideas of one-team Scrum.
https://less.works

Disciplined Agile Delivery (DAD) framework
DAD is goal driven and relies on hybrid Agile.
DAD provides guidance for adoption of an Agile framework.
Scaling factors
● Team size 2 < > 1000
● Geographic distribution co-located < > global
● Organizational distribution single division < > outsourcing
● Compliance none < > life critical
● Domain Complexity straightforward < > very complex
● Technical Complexity straightforward < > very complex
http://www.disciplinedagiledelivery.com/

Disciplined Agile 2.0

Scaled Agile Framework (SAFe)
SAFe is an online, freely revealed knowledge base of proven success
patterns for implementing Lean-Agile software and systems development at
enterprise scale.
SAFe Principles
1. Take an economic view
2. Apply systems thinking
3. Assume variability; preserve options
4. Build incrementally with fast, integrated learning cycles
5. Base milestones on objective evaluation of working systems
6. Visualize and limit the WIP, reduce batch sizes, and manage queue lengths
7. Apply cadence, synchronize with cross domain planning
8. Unlock the intrinsic motivation of knowledge workers
9. Decentralize decision-making
http://scaledagileframework.com/

SAFe Evolution (v1 to v4)
1 2
3 4

Scaled Agile Framework (SAFe)

Flow
● Flow in psychology
● Flow in the workplace
● Lean Thinking
● Kanban
Practical flows...
● Why, What & How
● Plan, Do, Check, Act (PDCA)
● Feature Driven Development (FDD)
● Product, Epics & Stories

Flow in psychology
Flow is the mental state of operation in which a person
performing an activity is fully immersed in a feeling of
energized focus, full involvement, and enjoyment in the
process of the activity.
being in the zone

Flow in the workplace
Flow has been used in the software world as being "wired in", “hack mode”, or
simply “The Zone”.
The 3 conditions to achieve Flow by Mihály Csíkszentmihályi’s
1. Goals are clear
2. Feedback is immediate
3. A balance between opportunity and capacity
Group Flow or group cohesion can be achieved through
● Creative spatial arrangements
● Playground design
● Parallel, organized working
● Target group focus
● Advancement of existing one with prototyping
● Increase in efficiency through visualization
● Using differences among participants as an
opportunity, rather than an obstacle

Lean thinking
Coined by James P. Womack and Daniel T. Jones, it describes how to organize
human activities to deliver more benefits to society and value to individuals
while eliminating waste, by focusing on these concepts:
● Value
● Value streams
● Flow
● Pull
● Perfection

Toyota Production System (TPS)
http://www.toyota-global.com/company/vision_philosophy/toyota_production_system/

Kanban
4 Principles
1. Start with what you do now
2. Agree to pursue incremental,
evolutionary change
3. Respect the current process,
roles, responsibilities and titles
4. Encourage acts of leadership at
all levels
5 Properties
1. Visualize the workflow
2. Limit work-in-progress (WIP)
3. Measure and Manage the flow
4. Make process policies explicit
5. Improve collaboratively using
models and empirical evidence

Cumulative Flow Diagram
A great way to read the
data behind a Kanban
board is to use a
cumulative flow diagram.
● Backlog size
● Lead time
● Cycle time
● Work in progress
● Work remaining
http://wall-skills.com/2013/cumulative-flow-diagram/

Why, What & How
●WHY are we doing this?
Voice of the stakeholder (Stakeholders)
●WHAT needs to be done?
Voice of the user (Product Owner, Subject Matter Expert)
●HOW do we build it?
Voice of the developer (Scrum Team)

PDCA - Plan, Do, Check, Act
ACT
PLAN DO
PDCA
Cycle
CHECK
Continuous Improvements

Feature Driven Development (FDD)
www.torak.com

Product, Epics & Stories
Story Story Story
Story Story Story
Story Story Story
Story Story Story
Story Story Story
Story Story Story
Product
Epics
Stories
www.torak.com

Agile Coaching, Staffing and Training.
Learn more at www.torak.com
Learn more at www.AgileTestingFramework.com

Thank You

This presentation was inspired by the work of many people and we have done our very best to
attribute all authors of texts and images, and recognize any copyrights. If you think that
anything in this presentation should be changed, added or removed, please contact us.
http://creativecommons.org/licenses/by-nc-nd/3.0/
www.torak.com

Planning, scaling and flowing within your agile organization

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (7)

Similaire à Planning, scaling and flowing within your agile organization

Similaire à Planning, scaling and flowing within your agile organization (20)

Dernier

Dernier (20)

Planning, scaling and flowing within your agile organization