1
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
2
Shut Up and Play Yer Guitar
David Hussman will be standing in for Frank Zappa
We learn by coaching + producing
Design
Deliver
Learn
We learn through debate and dialog
3
We learn through diversity
We learn through comparison
How do they compare?
4
Let’s compare success (label free agility)
Let’s compare your views
Pair up!
5
Is this a good song?
What about this song?
Not bad for no documentation
6
Let’s compare software views
Is this a good software product?
The system overloaded, saved state, shut down, rebooted and reloaded
7
How about this?
1 billion downloads - 200,000 years played
What’s the secret of Angry Birds?
Why do people love it so?
How did the makers learn this?
8
Does linear burndown increase sales?
Does reducing WIP produce more fans?
So how does Zappa fit in?
Shut Up and Play Yer Guitar
Let’s compare two producers
9
Shut Up and
Play Yer Guitar!
(producer, musician,
songwriter, arranger)
Musicians learn by
1) practicing
2) jamming
3) recording
4) listening
5) learning
6) repeating
So where’s the comparison?
10
Shut up
and Produce!
( XP, Wiki, FIT,
Federated Wiki )
Ward teaches and learns
by doing …
… and reflecting and adjusting
11
So what have we really done? ( what can we learn from the past? )
The Good, the Bad, and the Ugly
The Good, the Bad, and the Ugly
“That’s not how we do Agile”
“Were doing it by the book”
“They’re trying to do pure Scrum”
Following process over examining results
The Good, the Bad, and the Ugly
from 10% of 100% to 100% of 10%
from hours work to product value
from test lying to test driven
We learned to shift …
from more docs to more use
from how big to too big
12
Visualizing Business Agility
from “10% of 100%” to “100% of 10%”
“Everything’s a five”
from “how big” to “too big”
Visualizing Technical Debt
from “test lying” to “test driven”
13
Where are we today? ( challenging our learning )
V= W H
How much process is enough?
Dude’s Law: Value = Why / How
can we continuously deliver and learn?
If we can continuously integrate,
14
or simply reading sentences in documents?
Are we talking about users and use,
Are we moving from software development,
to product development + product learning?
Looking Forward to the Future ( how will DevJam learn? )
15
What have I learned from game builders?
“done is fun, and challenging”
Slices guide the DevJam producers
Slices help cross cut perspectives
16
Slices help cross cut systems
Slicing help cross cut time locations
Thin Slicing a Product
17
18
19
20
21
22
Where can we go? ( what questions will help us learn? )
My questions for DevJam learning
What is the next best investment?
How much process is enough?
What do we need to learn next?
From IQ to EQ to CQ
( CQ == continuous questioning )
Related Documents
