13 agile practices that are less known of and can potentially improve your team, organization, yourself or your sex life.

1. @peitor
13 explosive things you
should try as an agilist
Peter Gfader

2. @peitor

3. @peitor
Abstract
Agile practices that are less known of and
can potentially improve your team,
organization, yourself or your sex life.

4. @peitor
Deutscher Abstrakt
10 verrückte explosionsgefährliche Dinge
die man als Agilist kennen sollte
Wir schauen uns 10 neuere Praktiken aus der agilen Szene an und wie man diese in der
eigenen Organisation umsetzen könnte, bzw. im aktuellen Projekt anwenden.
Wenn Sie noch nie von "MVP vNext", "MVE", "God mod design", "MDD" und
"Hypothesis Driven Development" und anderen Praktiken gehört haben dann sollten
sie vorbeischauen und mit-brainstormen wie man diese Praktik in die eigene Firma
bringen kann.

5. @peitor
About You

6. @peitor
What do you do in software?
• Analyze
• Design
• Code
• Test
• Architect
• Document
• Coach
• Manage

7. @peitor
About Me

8. @peitor

9. @peitor
4 years ago..
http://copycat.apphb.com/

10. @peitor
The plan
How we work?
# God mode design thinking
# Mob Programming
Team
# Core protocols
# Definition of Awesome
Personal
# Failure Bow
# Personal Retrospectives
# Improv Theater
Users & Value
# MVE
# MVA
# Job Stories
Approach work
# Working Backwards
# MDD
# HDD

11. MVP
Not 1st release
Don’t build something

12. @peitor
MVP  # MVE
Minimum Viable “Experiment”
• No prediction
oExpectations and assumptions
• No matter who's idea -> lets validate it
• Different thought process -> brain
• For the Enterprise
http://blog.alpha-ux.co/making-the-case-for-minimum-viable-experiments

13. Voting

14. Concierge MVP
From the book

15. Magic Test
ConciergeMVP for web

16. @peitor
When MVP doesn’t work?
•Used by my peers?
•Stick to the *next* launch

17. @peitor
When MVP doesn’t work?
• Used by my peers?
• Stick to the launch
 Build an audience
http://sethgodin.typepad.com/seths_blog/2011/11/when-minimal-viable-product-doesnt-work.html

18. @peitor
# MVA
Minimum Viable Audience
what people are willing to buy.
http://www.copyblogger.com/unfair-business-advantage/

19. @peitor
“People only truly tell you what they want
to buy…
…by buying it”

20. @peitor

21. @peitor
# MVA
1. What is your MVA?
2. How?
oFree content
oCrowdfunding Kickstarter
oInvite Only
•Eg https://number26.de

22. Voting

23. @peitor
Inspire by
What exists already
• http://37signals.com/bootstrapped
• http://www.producthunt.com/

24. @peitor
Inspire by
Failure & Feedback
• http://autopsy.io/
• Amazon 1* reviews

25. User Stories
As a user
I want a button
So that I can log in
WTF!?!

26. User Stories

27. @peitor
# Job Stories
http://popcornflow.com/

28. Voting

29. Elevator Pitch
We're giving (people) (this benefit) so that they can (do this)
For (ppl) who () [product is a ----- that---- unlike ---
(competitor/product)
Our [Product] is Uber for (service)

30. @peitor
# Working Backwards
• Start with the Press Release
• ½ pager
http://www.allthingsdistributed.com/2006/11/working_backwards.html

31. @peitor
Title
Product or Feature
Market
Summary
Problem
Solution
Quote
How to Get Started
Call to Action

32. Voting

33. Product Backlog
filled with
● Stories
● Features
● Epics

34. @peitor
# HDD
Replace “req” with hypotheses
Right product?
BMC (Lean Canvas) -> breakdown
Riskiest assumption 1st
http://www.hackerchick.com/2012/04/hypothesis-driven-development.html

35. @peitor
# HDD
• Hypothesis Driven Development

36. Voting

37. @peitor
How many experiments do you
run?
How often do you deploy to Production?

38. @peitor
How many experiments do you
run?
How often do you deploy to Production?
From Thoughtworks

39. @peitor
# MDD
• Metrics Driven Development
http://blog.librato.com/posts/2014/7/16/metrics-driven-development

40. @peitor

41. @peitor
# MDD
• What system hypothesis are you testing
• Bugs? -> Effect on metrics
• TDD -> Test your behavior?
• MDD -> Metrics for desired behavior?

42. @peitor
# of purchase / min
Avg basket $$$
# of new signups

43. @peitor
Experiments
&
Data
Arguments
&
Opinions

44. Voting

45. Six Thinking Hats

46. @peitor
# God mode design thinking
“How would god build this?”

47. @peitor
How close can you come?
Ideal design

48. @peitor

49. @peitor

50. Voting

51. Pair Programming

52. @peitor
# Mob Programming
• Whole team
• Work on same thing
• Same time
• Same space
• Same computer
http://mobprogramming.org/

53. @peitor
# Mob Programming
http://mobprogramming.org/

54. Voting

55. Self organizing Teams

56. @peitor
# Core protocols
Team commitments
• “Ask for Help”
• “Perfection Game”
• “Check In”
• “Click”
http://www.mccarthyshow.com/online/

57. Voting

58. Definition of Done

59. @peitor
# Definition of Awesome
“What would Awesome look like for your
Team? Product feature?”
“What would take you 1 step closer
to Awesome?”
Toyota Katahttp://blog.crisp.se/2012/08/23/henrikkniberg/problem-solving-template

60. @peitor

61. Voting

62. “Learn from failure”

63. @peitor
Failure bow
http://tedxtalks.ted.com/video/The-Failure-Bow-Matt-Smith-at-T

64. @peitor
Failure bow as an observer
Benjamin Zander on mindset and teaching… https://vimeo.com/18625943

65. Voting

66. Retrospectives

67. @peitor
# Personal Retrospectives

68. Voting

69. Theater

70. @peitor
# Improv Theater
live theatre
plot, characters and dialogue
are made up in the moment

71. @peitor
# Improv Theater
What is it not
• !being funny
• !natural performer
• !hard to learn

72. @peitor
# Improv Theater
• Turn off conscious brain
• Idea creation
• Commit to whatever happens
• Improvisation is everywhere

73. @peitor
# Improv Theater
my lessons
1. Try something crazy hard…
makes normal easy
2. Doing trumps reading
3. “Yes And” attitude
“Move forward” attitude
4. “You are not alone” mindset

74. Voting

75. @peitor
Done
How we work?
# God mode design thinking
# Mob Programming
Team
# Core protocols
# Definition of Awesome
Personal
# Failure bow
# Personal Retrospectives
# Improv Theater
Users & Value
# MVE
# MVA
# Job Stories
Approach work
# Working Backwards
# MDD
# HDD

76. @peitor
What do you start
tomorrow?