WEBVTT
00:00:02.180 --> 00:00:05.524
- So, hello everyone.
00:00:05.524 --> 00:00:08.408
I'd like to state and for the record,
00:00:08.409 --> 00:00:10.577
I love the blue dots.
00:00:10.577 --> 00:00:11.976
(audience laughs)
00:00:11.976 --> 00:00:16.507
I've been sitting there
watching the blue dots.
00:00:16.507 --> 00:00:23.116
So, I've been cast in the role of
the person who finds the problems
00:00:23.116 --> 00:00:26.203
with the topic that we're all praising.
00:00:26.203 --> 00:00:29.228
I do like agile design, I like it a lot.
00:00:29.228 --> 00:00:32.804
And I like the concept of
agile learning design,
00:00:32.804 --> 00:00:34.981
I like it a lot.
00:00:34.981 --> 00:00:40.536
But, you know, I've been in the field
of programming for many years.
00:00:40.536 --> 00:00:43.840
I've been in the field of learning design
for many years.
00:00:43.840 --> 00:00:47.561
I've worked on small projects,
I've worked on big projects,
00:00:47.566 --> 00:00:50.111
I've been the peon
at the bottom of the pile
00:00:50.111 --> 00:00:55.171
and currently I'm the program leader
responsible for producing outcomes.
00:00:55.171 --> 00:00:57.204
So I've seen it from different angles.
00:00:57.204 --> 00:01:00.838
And there's so many ways it can go wrong,
00:01:00.838 --> 00:01:03.922
especially when we move
00:01:03.922 --> 00:01:08.212
from the fairly static domain
of software design
00:01:08.212 --> 00:01:13.533
to the far less static domain
of learning design.
00:01:13.540 --> 00:01:16.006
That's learning design.
00:01:16.006 --> 00:01:20.991
It's the least agile thing
you'll ever see.
00:01:20.991 --> 00:01:25.277
That's actually a graphic from IMS
00:01:25.277 --> 00:01:28.960
which produced the learning design
specification.
00:01:28.960 --> 00:01:31.554
That's supposed to be
pretty open and flexible,
00:01:31.554 --> 00:01:36.426
It's like a play with a director and roles
and all of that.
00:01:36.426 --> 00:01:40.296
But, you know, once you're into the thing,
00:01:40.296 --> 00:01:42.803
there isn't a whole lot of flexibility
happening
00:01:42.803 --> 00:01:48.910
and it leads to questioning just
what is it that we're up to
00:01:48.910 --> 00:01:51.774
when we are talking about
agile learning design?
00:01:51.774 --> 00:01:56.676
Are we talking about
agile learning design
00:01:56.676 --> 00:02:01.781
or are we talking about
the design of agile learning?
00:02:01.781 --> 00:02:03.773
Two different things.
00:02:03.773 --> 00:02:06.415
And it seems to me that
it doesn't make sense
00:02:06.415 --> 00:02:11.040
to give the instructional designers
all that freedom and flexibility
00:02:11.040 --> 00:02:13.920
if we're gonna march students
lockstep through
00:02:13.920 --> 00:02:18.252
a predefined kind of process.
00:02:18.252 --> 00:02:22.495
Here's what agile learning design
ought to look like.
00:02:22.495 --> 00:02:24.513
There's a flow.
00:02:24.513 --> 00:02:26.677
This is agile design generally, right?
00:02:26.677 --> 00:02:28.505
And it's an iterative thing,
00:02:28.505 --> 00:02:30.781
and yet people don't talk
about that so much
00:02:30.781 --> 00:02:32.765
but it's an iterative thing.
00:02:32.765 --> 00:02:38.750
Each iteration is like designing a full
and complete product,
00:02:38.750 --> 00:02:42.866
and then you might spin off
some side things, some prototype things
00:02:42.866 --> 00:02:47.467
as you need to, but, you know,
version one, version two,
00:02:47.480 --> 00:02:50.441
you're doing the same thing over again.
00:02:50.441 --> 00:02:53.281
No course in the world,
well, maybe not no course,
00:02:53.281 --> 00:02:56.779
but few courses in the world
are designed that way.
00:02:56.779 --> 00:03:00.402
Courses progress from lesson one,
lesson two, lesson three, lesson four.
00:03:00.402 --> 00:03:05.869
They don't cover all of geometry
and then all of geometry in more detail
00:03:05.869 --> 00:03:07.590
and all of geometry in more detail.
00:03:07.590 --> 00:03:13.130
It's a different way of thinking
about the process.
00:03:13.130 --> 00:03:18.587
So, one of the major concepts
in agile learning design,
00:03:18.587 --> 00:03:21.432
in agile design generally, is the Scrum.
00:03:21.432 --> 00:03:27.351
The Scrum is basically
a self-organizing development team.
00:03:27.351 --> 00:03:30.178
It is originally drawn from the idea that
00:03:30.178 --> 00:03:34.864
programmers are the smartest people
in the world and do not need management.
00:03:34.864 --> 00:03:39.669
No, I'm just kidding, but there is
the idea here that
00:03:39.669 --> 00:03:45.502
the programmers know how to program, and
they know how to produce the outcomes,
00:03:45.503 --> 00:03:50.252
if they're left to do the job for
themselves, to organize for themselves.
00:03:50.252 --> 00:03:54.791
And indeed, in the Scrum meeting,
as you are mapping out the task,
00:03:54.791 --> 00:04:00.031
each of the tasks, in the Scrum,
is self-selected by the programmer.
00:04:00.031 --> 00:04:03.589
So, they're volunteering to jump in,
to do these things.
00:04:03.589 --> 00:04:08.414
They're taking commitments on themselves,
they're specifying how much time,
00:04:08.414 --> 00:04:11.980
how much effort will be required
to produce the commitment.
00:04:11.980 --> 00:04:16.589
So, okay, that's good
00:04:16.589 --> 00:04:20.249
but this doesn't happen by magic.
00:04:20.249 --> 00:04:25.221
It takes time, and agile
is typically employed
00:04:25.221 --> 00:04:27.744
in larger software development projects.
00:04:27.744 --> 00:04:31.824
But when we're doing learning design,
we're doing something a lot smaller
00:04:31.824 --> 00:04:33.445
and a lot more precise.
00:04:33.445 --> 00:04:35.099
The question came up earlier, you know,
00:04:35.099 --> 00:04:38.481
"What about, you know, high-volume
instructional design?"
00:04:38.481 --> 00:04:44.548
Well, high-volume instructional design:
you don't have time for 3,4,5,6,7 weeks
00:04:44.548 --> 00:04:50.405
of your development team
organizing itself.
00:04:50.408 --> 00:04:52.541
Another problem:
00:04:52.541 --> 00:04:58.822
as your projects get bigger, and we've
worked on some very large projects,
00:04:58.822 --> 00:05:02.464
your teams get very large.
00:05:02.464 --> 00:05:04.882
If you think about
all the different people who can,
00:05:04.882 --> 00:05:08.859
and eventually will get involved
in the design of your learning,
00:05:08.859 --> 00:05:11.983
or in the delivery of your agile learning,
00:05:11.995 --> 00:05:17.023
you've got designers, you've got
subject matter experts,
00:05:17.023 --> 00:05:23.101
you've got programmers, you've got
human interaction specialists, etc.
00:05:23.101 --> 00:05:27.381
Eventually you get a very large,
very complex team.
00:05:27.381 --> 00:05:32.729
As you get larger teams, you do not
generate more efficiency, it's well known,
00:05:32.729 --> 00:05:35.069
you generate less efficiency.
00:05:35.069 --> 00:05:37.163
So, what's the solution?
Split the teams.
00:05:37.163 --> 00:05:42.447
Okay, now you have competing
development teams
00:05:42.447 --> 00:05:45.447
working on the same project.
00:05:45.447 --> 00:05:49.747
This sounds, like, you know, OK,
we've split the task, it's great.
00:05:49.747 --> 00:05:53.041
But when you split the task,
00:05:53.041 --> 00:05:59.032
you now have two different groups
of people with different objectives,
00:05:59.032 --> 00:06:01.188
different responsibilities.
00:06:01.188 --> 00:06:05.958
They're competing often for resources,
they're competing often for priority.
00:06:05.958 --> 00:06:09.880
We have a project where we had
two agile teams.
00:06:09.880 --> 00:06:15.032
We ended up with two versions
of the thing that we were developing.
00:06:15.032 --> 00:06:19.245
Basically, they had, they didn't split
into functional groups,
00:06:19.245 --> 00:06:22.379
they, what's the word for it?
00:06:22.379 --> 00:06:26.969
Ah, when cells divide, mitosis.
00:06:26.969 --> 00:06:33.589
So basically, we got two small versions
of the project we were trying to create.
00:06:33.589 --> 00:06:36.141
Another pitfall:
00:06:36.141 --> 00:06:41.708
if you try to organize your groups into,
you know, okay,
00:06:41.708 --> 00:06:44.734
this group will do this part of it,
this group will do that part of it,
00:06:44.734 --> 00:06:48.560
you get specialized Scrums.
00:06:48.560 --> 00:06:53.805
So now, nobody's working on
the final project, on the final product.
00:06:53.805 --> 00:06:57.641
And there is the danger, and I've
seen this and we've had this,
00:06:57.641 --> 00:07:00.701
and in fact, I'm living this
at this very moment
00:07:00.710 --> 00:07:06.580
where everybody, all the teams
want to do the analysis bit,
00:07:06.584 --> 00:07:09.837
or the rapid prototyping bit.
00:07:09.837 --> 00:07:16.463
But we're trying to bring a product
to actual users, at the end.
00:07:16.463 --> 00:07:18.879
We want it to be a deliverable product.
00:07:18.879 --> 00:07:25.445
Nobody wants to do the last stage
of error testing, of hardening the code.
00:07:25.445 --> 00:07:29.117
That's the least popular scrum.
00:07:29.117 --> 00:07:34.655
So they go back to, they all want
to do prototyping again.
00:07:34.655 --> 00:07:39.064
Finally, well, not quite finally
but we're getting there,
00:07:39.064 --> 00:07:42.058
who is the product owner?
00:07:42.058 --> 00:07:47.242
In the Scrum process,
you're delivering outcomes
00:07:47.242 --> 00:07:52.031
and the idea is that,
as you go through each sprint,
00:07:52.031 --> 00:07:56.477
which is short-term cycle
through your development process,
00:07:56.477 --> 00:07:59.919
you're producing outcomes,
you're producing deliverables
00:07:59.919 --> 00:08:04.038
and these deliverables
are delivered to the product owner
00:08:04.038 --> 00:08:08.487
who will set the deliverable,
and even more importantly,
00:08:08.487 --> 00:08:13.150
define the conditions for the completion
of that deliverable.
00:08:13.150 --> 00:08:15.237
Did you do it or not?
How do you know?
00:08:15.237 --> 00:08:19.450
Well, you have to have certain criteria.
It passed this test.
00:08:19.450 --> 00:08:21.490
It produced this function.
00:08:21.490 --> 00:08:24.172
It has to be really solid
and concrete.
00:08:24.172 --> 00:08:28.960
Well, that good in education, or sorry,
that's good in software development,
00:08:28.960 --> 00:08:31.592
your product owner is your client,
00:08:31.592 --> 00:08:34.738
perhaps your architect,
somebody like that.
00:08:34.738 --> 00:08:36.841
They know what they want.
00:08:36.841 --> 00:08:39.581
Education is completely different.
00:08:39.581 --> 00:08:44.755
In education, there is
no product owner per se.
00:08:44.755 --> 00:08:50.448
Think about it, think about the different
populations that are involved in learning.
00:08:50.448 --> 00:08:54.379
There is the end user,
also known as the student,
00:08:54.379 --> 00:08:59.339
who, in the typical instructional design
process, does not show up until
00:08:59.339 --> 00:09:03.302
after the instructional design
has been done.
00:09:03.302 --> 00:09:05.938
It makes it very hard to be agile.
00:09:05.938 --> 00:09:11.311
There is the subject matter expert,
also known as the professor.
00:09:11.311 --> 00:09:16.016
The professor has his or her own ideas
of what the deliverable must be.
00:09:16.016 --> 00:09:20.522
Then there is the administrator,
the dean or the president,
00:09:20.522 --> 00:09:23.636
or the department of extended learning,
or whatever,
00:09:23.636 --> 00:09:27.438
who have other objectives,
often revenue objectives,
00:09:27.438 --> 00:09:31.906
or course completion objectives.
They have their own definition.
00:09:31.906 --> 00:09:34.491
All of these definitions are different.
00:09:34.491 --> 00:09:38.484
I guarantee you they're conflicting
and they're competing.
00:09:38.484 --> 00:09:41.862
You can't just pick one,
because if you pick one,
00:09:41.862 --> 00:09:47.159
you're not being agile for the others.
00:09:47.159 --> 00:09:48.870
What's worse?
00:09:48.870 --> 00:09:54.930
To have not just competing interests,
to have different levels of expertise.
00:09:54.930 --> 00:09:58.276
We're designing a system right now,
00:09:58.276 --> 00:10:02.363
where we're trying to create
agile learning itself.
00:10:02.363 --> 00:10:04.904
This is, I'm not going to talk
about that,
00:10:04.904 --> 00:10:07.388
but that's not the purpose
of this particular talk,
00:10:07.388 --> 00:10:12.797
but the ideas here is that
as the learning is unfolding,
00:10:12.797 --> 00:10:16.398
the process, the outcomes,
the deliverables and all of that
00:10:16.398 --> 00:10:20.487
can change
as the needs of the learner change.
00:10:20.487 --> 00:10:23.058
Very ambitious, really hard.
00:10:23.058 --> 00:10:27.210
We have to think about learning
differently, in order to do that.
00:10:27.210 --> 00:10:29.621
Well, we've got our development teams.
00:10:29.621 --> 00:10:34.937
Our development teams were raised
in the traditional educational system.
00:10:34.937 --> 00:10:38.322
Their idea of education
and online learning is
00:10:38.322 --> 00:10:41.860
create some videos, put them online.
00:10:41.860 --> 00:10:47.236
Well, if we're iterating over a project,
the first version of the project,
00:10:47.236 --> 00:10:51.064
also known as
the minimally viable product,
00:10:51.064 --> 00:10:55.152
it's going to be pretty simple and it's
going to be something that you could do
00:10:55.152 --> 00:10:57.530
with fairly traditional methods.
00:10:57.530 --> 00:11:02.397
And your programmers and developers,
all other things being equal,
00:11:02.397 --> 00:11:05.262
will fall back on the traditional methods
00:11:05.262 --> 00:11:08.862
because they're not being challenged
with the minimal viable product.
00:11:08.862 --> 00:11:14.853
The end goal where you want to get to
is something really flexible and dynamic,
00:11:14.853 --> 00:11:17.966
but by the time you get
to stage five or so,
00:11:17.966 --> 00:11:22.548
they've built many, many
static structures,
00:11:22.548 --> 00:11:26.370
because that's what it took to
the minimally viable product
00:11:26.370 --> 00:11:29.843
at each release, at each iteration.
00:11:29.843 --> 00:11:32.454
So you have to start over.
00:11:32.454 --> 00:11:36.059
And you start over and everybody agrees,
00:11:36.059 --> 00:11:40.308
okay, the project is about something
a lot more flexible than that
00:11:40.308 --> 00:11:44.877
and you start developing again
and the same sort of problem happens
00:11:44.877 --> 00:11:48.743
because your developers and your designer
00:11:48.743 --> 00:11:52.543
did not acquire that expertise
in the meantime.
00:11:52.543 --> 00:11:54.667
So they go back on what they already know.
00:11:54.667 --> 00:11:56.954
So there's a difficulty here.
00:11:56.954 --> 00:12:03.221
In instructional design, we're attempting
to create an outcome
00:12:03.221 --> 00:12:10.244
that is not part of the skill set of the
people producing the product
00:12:10.244 --> 00:12:14.107
that results in the instructional design.
00:12:14.107 --> 00:12:16.905
Finally, learning objectives.
00:12:16.905 --> 00:12:19.772
This is the meta thing, right?
00:12:19.772 --> 00:12:24.053
And I get this one all the time: we do
connectivist-style MOOCs,
00:12:24.053 --> 00:12:28.228
the connectivist-style MOOC.
We say there is no curriculum.
00:12:28.228 --> 00:12:32.099
It's not about acquiring a certain
predefined body of content,
00:12:32.099 --> 00:12:37.319
because we want to meet
participants' needs
00:12:37.319 --> 00:12:42.301
as they go through the course, and
these needs are different for every person
00:12:42.301 --> 00:12:45.360
and these needs change over time.
00:12:45.360 --> 00:12:51.515
And it should be up to the participant,
who ought to be the product owner,
00:12:51.515 --> 00:12:56.081
to define what success is and
define what the outcome should be.
00:12:56.081 --> 00:12:58.425
It's a moving target.
00:12:58.425 --> 00:13:04.547
Nobody who funds education
wants to deal with that. Nobody.
00:13:04.547 --> 00:13:10.178
Every last one of them wants to see
course completions, certificates,
00:13:10.178 --> 00:13:13.651
competencies, curricular outcomes.
00:13:13.651 --> 00:13:18.229
They want them defined ahead of time.
They want them approved
00:13:18.229 --> 00:13:22.478
by the curriculum board or
the school board or whoever is in charge.
00:13:22.478 --> 00:13:26.428
All of this must be set ahead of time.
00:13:26.428 --> 00:13:28.938
And then you're supposed to go
and be agile.
00:13:28.938 --> 00:13:34.258
It is two very contradictory perspectives
at work here.
00:13:34.258 --> 00:13:40.920
It's not possible to do agile learning,
much less agile learning design
00:13:40.920 --> 00:13:46.868
in an environment where the structures
and the outcomes are all predefined.
00:13:49.058 --> 00:13:52.635
That's meek, that's my short talk
and I thank you very much.
00:13:52.635 --> 00:13:54.912
(applause)