how to talk to your developers
TRANSCRIPT
We are Spin42…
Marc
Thibault Loïc
Presence: psychological
Town: Bryan, Texas
Skills: He teaches Agility to Chuck Norris
Presence: physical
Town: Louvain la Neuve
Skills: His first book was Metaprogramming Ruby Presence: physical
Town: Louvain la Neuve
Skills: He speaks as fast as he codes
Developers are …
Not freaky, crappy, ugly guys
handsome guys who can to talk
They can talk… but Why talk to them?
Yet another project
How the customer explained it
How the business described it
How the developer wrote it
What Do You Want?
Something to Show
Get Customer/User Feedback
Get Funded
Earn Money
Robust
Minimal Viable
High quality Simple Relevant
High Quality Simple
Relevant
High quality Simple Relevant
Robust
Minimal Viable
PrototypeBuild
Measure
Learn
Increment
MVPBuild
Measure
Learn
Increment
How to Get There? “Simplicity is the ultimate sophistication”
Leonardo da Vinci
1Define Your Needs
User Stories
As a <type of user>, I want <some goal to do something> so that <it
brings me some value>
SMART User Stories
SpecificMesurable
AchievableRelevant
Time Bound
I want a search field to search based on the firstname and lastname
As a community manager, I want to search in the customers list so that
I can see what previous conversations I've had with them
Prioritize2
Dimensional Planning
Idea: If complete version of a functionality is impossible, a simple version can be super easy
Goal: Increase project throughput and shorten the feedback loop
3+1 dimensions: time, resources, scope and depth
Dirt Road
Barely viable product level Take what you need then
throw out a third
Paved Road
Sober but robust implementation
Asphalt Road
Full implementation You probably don’t need features implemented at
this level
Flying Cars
SCI-FI ultra cool things So cool that you’ll never
implement them
Poker Planning
Idea: It’s the discussion and not the number that matters
Goal: Mesure the relative complexity of a user story compared to another
Let’s Play a Game
How hard is it to cut those fruits in one eatable piece?
3
The greater the task, the harder it is to estimate
And then treat them as deadlines
We’ll ask for estimates
Find your team maximum workload
How many cookies can you eat in one minute?
Build it3
Kanban
http://www.ted.com/talks/tom_wujec_on_3_ways_the_brain_creates_meaning
Test it4
Test it
Cost
of c
hang
e
Time
Fast untested coding
Simple tested coding
Collect Feedback5
Do it AgainWelcome to the feedback loop∞
What Should we Achieve? “In the long history of humankind (and animal
kind, too) those who learned to collaborate and improvise most effectively have prevailed”
Charles Darwin
Startup to Stay up
Startup to Stay up
Cost
of c
hang
e
Time
Critical Mass$ of change
$ of change
Wanna Stay Up?
Interact With Your Team
Be PragmaticRespond to change
Collaborate with Customer
Build a Working Software
Programming is like sex One mistake and you have to support it
for the rest of your life
Questions ?