Your SlideShare is downloading. ×
Continuous Learning & Delivery
Digital PM Summit, October 15, 2013

Josh Seiden
Principal
Neo New York
josh.seiden@neo.com...
Me and my #hashtags

Josh Seiden
www.neo.com
@neo_innovation

@

jseiden

leanUX
#leanStartup
#

leanUXbook

#
1. BEYOND THE PROJECT
2. KEY CONCEPTS
3. DISCUSSION
3
Old assumptions, new reality

4

4
Old assumptions, new reality

4

4
Old assumptions, new reality

4

4
Old assumptions, new reality
No more “Model Years”

6
No more “Model Years”

6
SOFTWARE
ENABLES
CONTINUOUS
CHANGE
7
SOFTWARE IS
EATING THE
WORLD.
Mark Andreessen,
WSJ, Aug 2011

8
Coping with Continuous Production
Business?
Business

Design?
Design?
Business?

Agile
Coping with Continuous Production
Business?
Business

Design?
Agile UX
Design?
Business?
Agile UX
Agile
Coping with Continuous Production
Business?
Business
Lean Startup

Design?
Agile UX
Design?
Lean Startup
Business?
Agile U...
Ideas
Learn

Build

Data

Product

Measure
USER NEED | BUSINESS MODEL | ENHANCEMENTS
PRODUCT LIFE-CYCLE

11
KEY CONCEPTS
(FOR COPING)
12
KEY CONCEPTS:

1. CONTINUOUS LEARNING
2. OUTCOMES, NOT FEATURES
3. SMALL, X-FUNCTIONAL TEAMS
4. THE NEW ORGANIZATION

13
1

CONTINUOUS LEARNING

14
A system built on continuous learning

Risk

Learning!

Diagram concept: @clevergirl

15
Continuous learning rhythm
Continuous learning rhythm

2 week sprint

2 week sprint

2 week sprint
Continuous learning rhythm
Theme

2 week sprint

2 week sprint

2 week sprint
Continuous learning rhythm
Theme

2 week sprint

2 week sprint

Sketching/Ideation

2 week sprint
Continuous learning rhythm
Theme

2 week sprint

2 week sprint

Iteration planning meeting
Sketching/Ideation

2 week spri...
Continuous learning rhythm
Theme

2 week sprint

2 week sprint

Iteration planning meeting
Sketching/Ideation
Testing: usa...
Continuous learning rhythm
Theme

2 week sprint

2 week sprint

Iteration planning meeting
Sketching/Ideation
Testing: usa...
2

OUTCOMES, NOT FEATURES

17
Output, Outcome, Impact
Output, Outcome, Impact
§

Output: the software we build. The materials we produce.
Easy to trace. Example: A new log-in ...
Output, Outcome, Impact
§

§

Output: the software we build. The materials we produce.
Easy to trace. Example: A new log...
Output, Outcome, Impact
§

§

§

Output: the software we build. The materials we produce.
Easy to trace. Example: A new...
Output
Outcome
Impact
Don’t manage output.

Instead, focus on outcomes.
Don’t make teams responsible for impact.
3

SMALL, CROSS-FUNCTIONAL TEAMS

23
Small, dedicated, co-located & cross-functional
Small, dedicated, co-located & cross-functional
Small, dedicated, co-located & cross-functional

1.

Two-pizza teams
Small, dedicated, co-located & cross-functional

1.
2.

Two-pizza teams
1 project each
Small, dedicated, co-located & cross-functional

1.
2.
3.

Two-pizza teams
1 project each
1 location (same time zone)
Small, dedicated, co-located & cross-functional

1.
2.
3.
4.

Two-pizza teams
1 project each
1 location (same time zone)
S...
4

A NEW ORGANIZATION

25
Enterprise?
Client?
Lean Startup
Business?
Business

Design?
Agile UX
Design?
Lean Startup
Business?
Agile UX
Agile
Product validation
Small team

Business model validation
Small-chunk, outcome-based, predictable funding
Stakeholders

$$
$
Product validation
Small team

Business model validatio...
KEY CONCEPTS:

1. CONTINUOUS LEARNING
2. OUTCOMES, NOT FEATURES
3. SMALL, X-FUNCTIONAL TEAMS
4. THE NEW ORGANIZATION

28
DISCUSSION
29
THANK YOU!
@jseiden

www.leanuxbook.com
www.neo.com
30
Upcoming SlideShare
Loading in...5
×

Continuous Learning and Delivery @ DPM Summit 2013

1,192

Published on

Slides from my talk / discussion at the Digital Project Management Summit, Oct 15, 2013. How do we manage "projects" when we work with software, a medium that is continuous in nature.

Published in: Technology, Business

Transcript of "Continuous Learning and Delivery @ DPM Summit 2013"

  1. 1. Continuous Learning & Delivery Digital PM Summit, October 15, 2013 Josh Seiden Principal Neo New York josh.seiden@neo.com @jseiden
  2. 2. Me and my #hashtags Josh Seiden www.neo.com @neo_innovation @ jseiden leanUX #leanStartup # leanUXbook #
  3. 3. 1. BEYOND THE PROJECT 2. KEY CONCEPTS 3. DISCUSSION 3
  4. 4. Old assumptions, new reality 4 4
  5. 5. Old assumptions, new reality 4 4
  6. 6. Old assumptions, new reality 4 4
  7. 7. Old assumptions, new reality
  8. 8. No more “Model Years” 6
  9. 9. No more “Model Years” 6
  10. 10. SOFTWARE ENABLES CONTINUOUS CHANGE 7
  11. 11. SOFTWARE IS EATING THE WORLD. Mark Andreessen, WSJ, Aug 2011 8
  12. 12. Coping with Continuous Production Business? Business Design? Design? Business? Agile
  13. 13. Coping with Continuous Production Business? Business Design? Agile UX Design? Business? Agile UX Agile
  14. 14. Coping with Continuous Production Business? Business Lean Startup Design? Agile UX Design? Lean Startup Business? Agile UX Agile
  15. 15. Ideas Learn Build Data Product Measure
  16. 16. USER NEED | BUSINESS MODEL | ENHANCEMENTS PRODUCT LIFE-CYCLE 11
  17. 17. KEY CONCEPTS (FOR COPING) 12
  18. 18. KEY CONCEPTS: 1. CONTINUOUS LEARNING 2. OUTCOMES, NOT FEATURES 3. SMALL, X-FUNCTIONAL TEAMS 4. THE NEW ORGANIZATION 13
  19. 19. 1 CONTINUOUS LEARNING 14
  20. 20. A system built on continuous learning Risk Learning! Diagram concept: @clevergirl 15
  21. 21. Continuous learning rhythm
  22. 22. Continuous learning rhythm 2 week sprint 2 week sprint 2 week sprint
  23. 23. Continuous learning rhythm Theme 2 week sprint 2 week sprint 2 week sprint
  24. 24. Continuous learning rhythm Theme 2 week sprint 2 week sprint Sketching/Ideation 2 week sprint
  25. 25. Continuous learning rhythm Theme 2 week sprint 2 week sprint Iteration planning meeting Sketching/Ideation 2 week sprint
  26. 26. Continuous learning rhythm Theme 2 week sprint 2 week sprint Iteration planning meeting Sketching/Ideation Testing: usability/value 2 week sprint
  27. 27. Continuous learning rhythm Theme 2 week sprint 2 week sprint Iteration planning meeting Sketching/Ideation Testing: usability/value Metrics: quantitative learning 2 week sprint
  28. 28. 2 OUTCOMES, NOT FEATURES 17
  29. 29. Output, Outcome, Impact
  30. 30. Output, Outcome, Impact § Output: the software we build. The materials we produce. Easy to trace. Example: A new log-in page.
  31. 31. Output, Outcome, Impact § § Output: the software we build. The materials we produce. Easy to trace. Example: A new log-in page. Outcome: the change in the world after we deliver output. Harder to trace. Example: increase user log-in rate.
  32. 32. Output, Outcome, Impact § § § Output: the software we build. The materials we produce. Easy to trace. Example: A new log-in page. Outcome: the change in the world after we deliver output. Harder to trace. Example: increase user log-in rate. Impact: the change we see over time. Very hard to trace. Example: Our service is profitable.
  33. 33. Output
  34. 34. Outcome
  35. 35. Impact
  36. 36. Don’t manage output. Instead, focus on outcomes. Don’t make teams responsible for impact.
  37. 37. 3 SMALL, CROSS-FUNCTIONAL TEAMS 23
  38. 38. Small, dedicated, co-located & cross-functional
  39. 39. Small, dedicated, co-located & cross-functional
  40. 40. Small, dedicated, co-located & cross-functional 1. Two-pizza teams
  41. 41. Small, dedicated, co-located & cross-functional 1. 2. Two-pizza teams 1 project each
  42. 42. Small, dedicated, co-located & cross-functional 1. 2. 3. Two-pizza teams 1 project each 1 location (same time zone)
  43. 43. Small, dedicated, co-located & cross-functional 1. 2. 3. 4. Two-pizza teams 1 project each 1 location (same time zone) Self-sufficient
  44. 44. 4 A NEW ORGANIZATION 25
  45. 45. Enterprise? Client? Lean Startup Business? Business Design? Agile UX Design? Lean Startup Business? Agile UX Agile
  46. 46. Product validation Small team Business model validation
  47. 47. Small-chunk, outcome-based, predictable funding Stakeholders $$ $ Product validation Small team Business model validation Culture / Infrastructure to support continuous learning
  48. 48. KEY CONCEPTS: 1. CONTINUOUS LEARNING 2. OUTCOMES, NOT FEATURES 3. SMALL, X-FUNCTIONAL TEAMS 4. THE NEW ORGANIZATION 28
  49. 49. DISCUSSION 29
  50. 50. THANK YOU! @jseiden www.leanuxbook.com www.neo.com 30

×