LSCon 2017 LLAMA: Agile Project Management for eLearning 101

Post on 22-Jan-2018

134 views 3 download

Transcript of LSCon 2017 LLAMA: Agile Project Management for eLearning 101

Session 108 LLAMA – Agile Project

Management for eLearning

Megan Torrance TorranceLearning

Orlando, FL • March 22 – 24, 2017

mtorrance@torrancelearning.com @MMTorrance @xAPIGnome @Tlearning @MyEleventure linkedin.com/in/megantorrance

4 You can buy this shirt on Amazon.com

5

Think about your best project ever.

"Do more of what works, & do less of what doesn't."

Kent Beck, author of

Extreme Programming (XP) Explained

7

Our projects are complex & we have to keep up with an

ever-increasing rate of change.

9

Source: Wikimedia Commons NASA_Space_Shuttle_Atlantis_landing_(STS

-110)_(19_April_2002).jpg 10

The first day of a project is the worst day to plan what the end product will be (and

how much it will cost).

11

12 Photo credit: ThinkStock 115796521

Squirrel!

Every day you learn something new about the project you're working on.

13

iStockphoto.com/10587442 14

ANALYZE

DESIGN

DEVELOP

IMPLEMENT

EVALUATE

TIME

15

A

D

I+E

D

I+E

D D D D

TIME

Agile is … An iterative, incremental method of guiding design & build projects

in a highly flexible & interactive manner, focusing on maximizing customer value and fostering high team engagement.

16

17

LLAMA is … An iterative, incremental method

of guiding instructional design & build projects in a highly flexible & interactive manner, focusing on maximizing customer value and fostering high team engagement.

18

THE AGILE MANIFESTO: We are uncovering better

ways of developing software by doing it and helping others

do it...

19 source: www.agilemanifesto.org

We are uncovering better ways of creating learning

experiences by doing it and helping others do it.

20

Through this work we have come to value:

Individuals and interactions over

processes and tools

21 source: www.agilemanifesto.org

Through this work we have come to value:

working software over

comprehensive documentation

22 source: www.agilemanifesto.org

Through this work we have come to value:

customer collaboration over contract negotiation

23 source: www.agilemanifesto.org

Through this work we have come to value:

responding to change over following a plan

24 source: www.agilemanifesto.org

25 Dollarphotoclub_25873819

WRITE LEARNER PERSONAS

Use learner personas as a guide to keeping training design & your project focused.

26

27 http://www.elcidweddings.com/wp-content/uploads/2012/08/Real-Weddings.jpg

How do you choose just one persona?

• Quantity

• Impact

• Business Risk

• Opportunity

• Degree of Difficulty

• Priority / timing for phases

29

DEFINE SCOPE WITH STORIES

Write learner stories and story cards to define scope and plan the project.

30

Stories capture business needs and performance

outcomes in a format that's useful for planning &

production.

31

Story Cards 3 Things

32

33

As a I want so I can

<who> <what> <why>

Use Agile story mapping for

building tools, things & software.

34

Use Cathy Moore's Action

Mapping to define stories for Agile learning projects.

35

36 http://blog.cathy-moore.com/

! Design a solution to meet stated needs

! Remove a kidney stone

! Provide verbal feedback to teammates

! Collect & enter data accurately

! Nail roof shingles safely

Practice in Training

Business Goal that solves a

Business Problem

Adapted from: Cathy Moore

Know . . .

PLAN THE WORK VISIBLY

Prioritize and schedule work

43

Define at the outset what

type of project this is.

iStockphoto.com/4689051 44

Zero-Surprises Project Management

1. Break big things into little ones.

2. Plan from the big to the little.

3. Work from the little to the big. (if they don’t match, start talking)

4. Make it visual.

45

46

Bottom-up Planning is based on estimates

47

Top-Down Planning: SME & Reviewer schedules Holidays Resource Plans Hard part

48

49

50

51

52

WORK ITERATIVELY until the work is ‘done’

Prioritize and schedule work

53

Make small mistakes faster.

Skip the big mistakes. Agile Explained, Menlo Innovations

54

55

57

A

D

I+E

D

I+E

D D D D

TIME

The Minimum Viable

Product

59

M.V.P.

Why iterate?

60

You always have something usable. You catch errors early. It’s easier to estimate. It’s psychologically way more satisfying.

How to iterate?

61

Alpha > Beta > Final By Project Phase By Delivery Medium By level of finish/functionality By language By audience

Megan’s Rules for Iterations It does real work.

Someone else has to use it.

You gather data.

Data informs the work to do in the next iteration.

62

63

mtorrance@torrancelearning.com @MMTorrance @xAPIGnome @Tlearning @MyEleventure linkedin.com/in/megantorrance