Successfully reported this slideshow.

What's your Skateboard? / Delivering the Most Valuable Features

1

Share

Loading in …3
×
1 of 50
1 of 50

What's your Skateboard? / Delivering the Most Valuable Features

1

Share

Download to read offline

Description

presented as a tutorial and talk at Dutch PHP Conference

Transcript

  1. 1. WHAT'S YOUR SKATEBOARD? EMILY STAMEY © PHOTO BY KENNY LOUIE 1
  2. 2. I'm a PHP developer I've o en worked directly with non-technical product owners and users I workED at a University 2
  3. 3. INSPIRED BY 3
  4. 4. A PROBLEMATIC PROJECT WORKFLOW 1. Research 2. Develop over several months 3. Deliver something 4. Learn if the big guess was correct 4
  5. 5. THE CLIENT-VENDOR ANTI-PATTERN 5
  6. 6. WHAT IS A STORY MAP? A diagram of a project that tells the story of the people and systems involved in a process. Detail is added as we learn more about the project The map can be built for an existing application or a new application. 6
  7. 7. THE STORY MAP 7
  8. 8. WHO SHOULD STORY MAP? Anyone who knows the process ... Not Just Developers At least one knowledgeable person from each group of stakeholders 8
  9. 9. WHEN TO STORY MAP?   When you have questions Before You begin development 9
  10. 10. WHY STORY MAP? Build shared understanding Encourage full discovery before prototyping Prioritize work to be done as a group *Lowers problems with estimates and feature creep 10
  11. 11. THE BIG PICTURE © PHOTO BY BARNYZ 11
  12. 12. FOCUS DURING DEVELOPMENT © PHOTO BY THEILR 12
  13. 13. WHERE? A large, clear wall or whiteboard. A place central to the team, at least in the beginning. 13
  14. 14. YOU'LL NEED painter's tape markers post-its (many colors & sizes) 14
  15. 15. A SIMPLE STORY List five tasks you do in order to get to work. Put each one on a post-it provided. 15
  16. 16. MY MORNING AT WORK (FIRST DRAFT) 16
  17. 17. FIND VARIATIONS Pick 3 things that you did today that are different from your normal work routine. 17
  18. 18. MY MORNING AT WORK (REVISED) There are variations between people, days of week, at- home and out-of-town work days 18
  19. 19. BUILDING THE NARRATIVE: USERS Who are the Actors/Users in your morning routine? 19
  20. 20. BUILDING THE NARRATIVE: ACTIVITY GROUPS Sometimes several tasks can be grouped together 20
  21. 21. BUILD THE STORY Let's put them together to build a story of your getting to work! 21
  22. 22. LEARN MORE Risk Assumptions Uncertainty If you cannot elaborate, mark it and revisit 22
  23. 23. CLARIFYING QUESTIONS What could we learn to replace risk with REAL information? Do we really know what has been mapped, or did we fill in assumptions? Are you sure about the story you're telling? 23
  24. 24. LABEL THESE 24
  25. 25. THOROUGH DISCOVERY Understand the full process Understand "why" steps are needed in the process Talk about things inside and outside of the app 25
  26. 26. THOROUGH DISCOVERY Simplify and lower risk at implementation Lowers the questions at the phase of implementation Limits Feature Creep (beginning implementation w/o understanding, new features come in) Better estimates 26
  27. 27. 27
  28. 28. MORE THAN JUST ADDING STORIES If the only thing you create while making sense of a big opportunity is more, small stories, you're doing it wrong. - Jeff Patton 28
  29. 29. FOUR STEPS TO DISCOVERY 1. Frame the idea 2. Understand Customers and Users 29
  30. 30. SIMPLE PERSONA 30
  31. 31. FOUR STEPS TO DISCOVERY 1. Frame the idea 2. Understand Customers and Users 3. Envision your solution 4. Minimize the plan 31
  32. 32. PRIORITIES 32
  33. 33. PRIORITIZING THE PROJECT Who will use this product? What steps must they accomplish for success? Remove/postpone the rest 33
  34. 34. PRIORITIZING FEATURES Differentiator - feature sets you apart from competition Spoiler - moves in on someone else’s differentiator Cost reducer - reduces organizational costs Table stakes - feature necessary to compete 34
  35. 35. FOCUS ON OUTCOMES What are you hoping to do with your application? Prioritize features based on the problem they solve Implement only what solves the problem or meets the objective 35
  36. 36. PROTOTYPING 36
  37. 37. PROTOTYPING What is the smallest thing you could build to prove/disprove an assumption? Sketch & prototype to test viability of the solution Aim for less than minimum, get feedback, and iterate o en When you give prototype to development partners you can include metrics to see what they actually do 37
  38. 38. MVP VS. MOST VALUABLE FEATURES Focus on releasing valuable features every time. Sometimes we plan features in a chronological order Or we divide the project into components 38
  39. 39. WHEN WE BUILD IN PIECES 39
  40. 40. WHEN WE BUILD IN PARTS 40
  41. 41. INSTEAD WE WANT TO ITERATE! 41
  42. 42. 42
  43. 43. STRATEGIES 43
  44. 44. 44
  45. 45. 45
  46. 46. 46
  47. 47. SUMMARY A tool you can use with non-technical subject matter experts, customers, etc A visual guide for managing your workload Focus on objectives when you prioritize Plan to deliver a usable product at each deliverable 47
  48. 48. SOOO... 48
  49. 49. WHAT'S YOUR SKATEBOARD? 49
  50. 50. @elstamey https://joind.in/talk/597d1 THANK YOU! EMILY STAMEY @ELSTAMEY HTTP://ELSTAMEY.COM 50

Description

presented as a tutorial and talk at Dutch PHP Conference

Transcript

  1. 1. WHAT'S YOUR SKATEBOARD? EMILY STAMEY © PHOTO BY KENNY LOUIE 1
  2. 2. I'm a PHP developer I've o en worked directly with non-technical product owners and users I workED at a University 2
  3. 3. INSPIRED BY 3
  4. 4. A PROBLEMATIC PROJECT WORKFLOW 1. Research 2. Develop over several months 3. Deliver something 4. Learn if the big guess was correct 4
  5. 5. THE CLIENT-VENDOR ANTI-PATTERN 5
  6. 6. WHAT IS A STORY MAP? A diagram of a project that tells the story of the people and systems involved in a process. Detail is added as we learn more about the project The map can be built for an existing application or a new application. 6
  7. 7. THE STORY MAP 7
  8. 8. WHO SHOULD STORY MAP? Anyone who knows the process ... Not Just Developers At least one knowledgeable person from each group of stakeholders 8
  9. 9. WHEN TO STORY MAP?   When you have questions Before You begin development 9
  10. 10. WHY STORY MAP? Build shared understanding Encourage full discovery before prototyping Prioritize work to be done as a group *Lowers problems with estimates and feature creep 10
  11. 11. THE BIG PICTURE © PHOTO BY BARNYZ 11
  12. 12. FOCUS DURING DEVELOPMENT © PHOTO BY THEILR 12
  13. 13. WHERE? A large, clear wall or whiteboard. A place central to the team, at least in the beginning. 13
  14. 14. YOU'LL NEED painter's tape markers post-its (many colors & sizes) 14
  15. 15. A SIMPLE STORY List five tasks you do in order to get to work. Put each one on a post-it provided. 15
  16. 16. MY MORNING AT WORK (FIRST DRAFT) 16
  17. 17. FIND VARIATIONS Pick 3 things that you did today that are different from your normal work routine. 17
  18. 18. MY MORNING AT WORK (REVISED) There are variations between people, days of week, at- home and out-of-town work days 18
  19. 19. BUILDING THE NARRATIVE: USERS Who are the Actors/Users in your morning routine? 19
  20. 20. BUILDING THE NARRATIVE: ACTIVITY GROUPS Sometimes several tasks can be grouped together 20
  21. 21. BUILD THE STORY Let's put them together to build a story of your getting to work! 21
  22. 22. LEARN MORE Risk Assumptions Uncertainty If you cannot elaborate, mark it and revisit 22
  23. 23. CLARIFYING QUESTIONS What could we learn to replace risk with REAL information? Do we really know what has been mapped, or did we fill in assumptions? Are you sure about the story you're telling? 23
  24. 24. LABEL THESE 24
  25. 25. THOROUGH DISCOVERY Understand the full process Understand "why" steps are needed in the process Talk about things inside and outside of the app 25
  26. 26. THOROUGH DISCOVERY Simplify and lower risk at implementation Lowers the questions at the phase of implementation Limits Feature Creep (beginning implementation w/o understanding, new features come in) Better estimates 26
  27. 27. 27
  28. 28. MORE THAN JUST ADDING STORIES If the only thing you create while making sense of a big opportunity is more, small stories, you're doing it wrong. - Jeff Patton 28
  29. 29. FOUR STEPS TO DISCOVERY 1. Frame the idea 2. Understand Customers and Users 29
  30. 30. SIMPLE PERSONA 30
  31. 31. FOUR STEPS TO DISCOVERY 1. Frame the idea 2. Understand Customers and Users 3. Envision your solution 4. Minimize the plan 31
  32. 32. PRIORITIES 32
  33. 33. PRIORITIZING THE PROJECT Who will use this product? What steps must they accomplish for success? Remove/postpone the rest 33
  34. 34. PRIORITIZING FEATURES Differentiator - feature sets you apart from competition Spoiler - moves in on someone else’s differentiator Cost reducer - reduces organizational costs Table stakes - feature necessary to compete 34
  35. 35. FOCUS ON OUTCOMES What are you hoping to do with your application? Prioritize features based on the problem they solve Implement only what solves the problem or meets the objective 35
  36. 36. PROTOTYPING 36
  37. 37. PROTOTYPING What is the smallest thing you could build to prove/disprove an assumption? Sketch & prototype to test viability of the solution Aim for less than minimum, get feedback, and iterate o en When you give prototype to development partners you can include metrics to see what they actually do 37
  38. 38. MVP VS. MOST VALUABLE FEATURES Focus on releasing valuable features every time. Sometimes we plan features in a chronological order Or we divide the project into components 38
  39. 39. WHEN WE BUILD IN PIECES 39
  40. 40. WHEN WE BUILD IN PARTS 40
  41. 41. INSTEAD WE WANT TO ITERATE! 41
  42. 42. 42
  43. 43. STRATEGIES 43
  44. 44. 44
  45. 45. 45
  46. 46. 46
  47. 47. SUMMARY A tool you can use with non-technical subject matter experts, customers, etc A visual guide for managing your workload Focus on objectives when you prioritize Plan to deliver a usable product at each deliverable 47
  48. 48. SOOO... 48
  49. 49. WHAT'S YOUR SKATEBOARD? 49
  50. 50. @elstamey https://joind.in/talk/597d1 THANK YOU! EMILY STAMEY @ELSTAMEY HTTP://ELSTAMEY.COM 50

More Related Content

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

×