Download - Agile Learning - Agile2013

AGILE LEARNING

Don McGreal

@donmcgreal

linkedin.com/in/donmcgreal

AGILE LEARNING improvingenterprises.com

!


CHAPTERS

1

2

3

ENVIRONMENT

PROBLEM WITH PRINCIPLES

RETENTION

CHAPTER 1

ENVIRONMENT


INTRODUCTIONS

Expectations(be selfish)

Name

RoleRelevant

Experience

Three Questions


THE DETRACTORS

The Terrorist

Use their power for good instead of evil.

Give them a reason to be there

The Prisoner


THE FRIENDLIES

Give them a reason for being there.Make it fun.

Use him when necessary.

The Tourist The Buddy


THE MONOPOLIZERS

The Glory Hound

Reference them.Team up with them.

Connect one-on-one.Coach.

The Eeyore


SCRUM AGENDA


QUESTION BACKLOG

What is the

difference between

Scrum and Agile?How long should a Sprint be?

How do I keep my Daily Scrum to

under 15 minutes?

How do I break

down Epics?

How do I get my manager to buy-in to

agile?

What do I do when I

have a total a$$ on

the team?

CONSULTING

MENTORING

COACHING


MAINTAIN A SAFE ENVIRONMENT

Say their name

Acknowledge their experience

Remember their contributions

No hand-raising

Never say ‘no’

Give them ownership

CHAPTER 2

PROBLEM WITH PRINCIPLES

Draw%a%picture%of%‘trust’.

It%is%very%hard%to%communicate%Values%and%Principles%without%practice,%shared%experience,%

and%context.


WHAT ARE THESE?Individuals%and%interactions%over%processes%and%tools

Working%software%over%comprehensive%documentation

Customer%collaboration%over%contract%negotiation

Responding%to%change%over%following%a%plan%

Games%and%Simulations%provide%a%fun%and%effective%way%to%communicate%

values%and%principles.

Play%==%Flow


LEARNING VECTORS

EmotionalRecall or create

an emotional experience

ImpressionalMemory games.‘Every Good Boy Deserves Fudge.’

PhysicalDoing.

Muscle Memory,

Learning Working


PLAY

★ Form%Pairs.%One%is%a%Product%Owner,%the%other%a%Developer.

★ Developers%face%away%from%the%slide.

★ Product%Owners%describe%the%product%without%saying%the%taboo%words.

★ Developer%draws%the%product.

What%Were%They%Thinking?


PLAY

★tea

★pot

★short

★stout

★coffee

★water

★heat

Do%not%use%these%words:


PLAY

★motorcycle

★bike

★camper

★recreationalvehicle%(rv)

★chopper

★harley

Do%not%use%these%words:


DEBRIEF★ In%software,%we%are%rarely%creating%something%that%already%exists,%so…★ it%is%difficult%to%describe.%Customers%may%not%have%a%

current%vocabulary.★ we%are%forced%to%communicate%in%imperatives%and%

metaphors%and%much%is%lost%in%translation.

★ Verbal%communication%is%easier%than%written

★ Using%iterative%development%along%with%feedback%loops%allow%the%customer%to%hone%in%on%what%is%really%needed


ValuesValues

Individuals and Interactions

Processes and Tools

Working Software

Comprehensive Documentation

Customer Collaboration

Contract Negotiation

Responding to Change

Following a Plan


CHAPTER 3

RETENTION


CONE OF LEARNING(Edgar Dale)

After 2 Weeks, we tend to remember...

Receiving/Participating

Doing

Verbal Receiving

Visual Receiving


CREATING CONTENT(Step 1/5)



Challenge Them“The things we have to learn before we do them, we learn by doing them.”- Aristotle


POCKET-SIZED PRINCIPLES1. Our highest priority is to satisfy the

customer through early and continuous delivery of valuable software.

2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

4. Business people and developers must work together daily throughout the project.

5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

7. Working software is the primary measure of progress.

8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

9. Continuous attention to technical excellence and good design enhances agility.

10.Simplicity--the art of maximizing the amount of work not done--is essential.

11.The best architectures, requirements, and designs emerge from self-organizing teams.

12.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.


POCKET-SIZED PRINCIPLESPrinciples

Early Value

Welcome Change

Frequent Delivery

Collaborate Daily

Motivation & Trust

Face to Face

Working Software

Sustainable Pace

Technical Excellence

K.I.S.S.

Self-Organize

Reflect and Adjust



Teach Each Other“The best way to learn is to teach.”- Oppenheimer


INTERACTIVE SCRUM DISCOVERY


10/24/7

QUESTIONS?

@donmcgreal


THANK YOU

@donmcgreal


Download - Agile Learning - Agile2013

Top Related