Agile Australia 2015: Building the right thing

Just make it simpler! Every team desires to build simpler products. How do they go about doing this? The fundamental approach this talk takes is around ensuring teams are building the right thing. At Atlassian we take a multitude of approaches to ensure we are building the right thing for specific users. We've made plenty of mistakes and lots of wins along the way! Learn how you can take some of the lessons learnt from the Atlassian Product Management team – such as agile product requirements, prototypes, customer interviews, and user journeys – to deliver simple and great solutions for your customers.

Transcript

2. SHERIF MANSOUR • PRODUCT GUY • ATLASSIAN • @SHERIFMANSOUR Building the Right Thing Lessons Learned in Agile Product Management
3. Defining the problem Building the solution Getting feedback
4. Defining the problem
7. The Homer
10. 1 Focus 
 roadmap & development 2 Create better experiences 3 Improve marketing
11. 1 Focus 
 roadmap & development
12. 2 Create better experiences
13. 3 Improve marketing
14. http://bit.ly/ADG-Personas
15. Customer Interviews
16. Building a shared understanding
17. COMMUNICATE 
 OBSERVATIONS INTERPRET
 PROBLEMS CONNECTING 
 OPPORTUNITIES V A L U E
18. COMMUNICATE OBSERVATIONS CONNECTING OPPORTUNITIES A, B, C, D A, B, C, D INTERPRET PROBLEMS
19. COMMUNICATE OBSERVATIONS INTERPRET PROBLEMS CONNECTING OPPORTUNITIES A & B = Problem 1 C & D = Problem 2
20. COMMUNICATE OBSERVATIONS INTERPRET PROBLEMS CONNECTING OPPORTUNITIES Problem FEATURE REQUEST IDEAS 20% PROJECTS RELATED PROBLEMS @MENTION OTHERS
24. Building a shared understanding One Interview At A Time http://bit.ly/InterviewPyramid
25. I hate requirements
26. We Try Not To How Do You…
27. As A (User) 
 I Want (Objective) So That (Why) Backlog
28. As Alana
 I Want Plan An Event So That My Team Can Run Effectively
29. As Alana
 I Want Plan An Event So That My Team Can Run Effectively A User New Add Event Button They Can Add Events
30. Stories Get Their Name From How They Should Be Used, Not What Should Be Written. JEFF PATTON Story Mapping (2014) ” “
31. Individuals and interactions over processes and tools Working software over comprehensive documentation http://agilemanifesto.org
32. Prototypes Journey Maps Analytics Surveys Videos, Talks And Interviews Requirements Documents Your agile toolbox
33. Journey Maps
34. FRICTION FRICTION your awesome feature
38. Draw the journey.
39. Requirements Documentation
40. We Try Not To How Do You…
41. But Sometimes We Do How Do You…
42. Lines of Code (million) 17.5 35 52.5 70 W in 3.1 W in N T W in 95 ('97) W in 98 ('00) W in 2k ('01) W in XP ('01) W in Vista ('07) W in 7 ('09) W in 8 ('13)
43. Vs Confluence Team Calendars
 New product Confluence Page Layouts
 New feature, existing product
44. Vs • What is our MVP? • What is our MVP? • What about migration? • PDF/HTML/Word Export • Copy/paste • Email notifications • Resizing layouts • …
45. Vs
46. …By Understanding The Needs Of Your Customers You Will Be Able To Deliver Succinct And Sufficient Documentation… SCOTT AMBLER
 agilemodeling.org ” “
47. Persona-driven roadmap, 
 build better experiences,
 improve marketing opportunities problems observations Observations, problems, opportunities “Agile requirements”: Build your toolbox
48. Defining the problem Building the solution Getting feedback
49. Building the solution
51. BEFORE AFTER Spaces People Calendar Create Spaces
52. Choose carefully.
57. Hero shot One-line pitch Three 
 Pillars
58. Build your box. Hero Shot One-Line Pitch Three Pillars
59. What if we didn’t have any documentation?
61. 5 months 20,000 unique visitors
62. 20,000 9,000,000+ Confluence users
63. Assume you don’t have release notes Even if you’ve got a flashy video of a 
 good looking guy!
65. Build-a-box Domino effect Assume no docs
66. Defining the problem Building the solution Getting feedback
67. Getting feedback
68. Friction
71. FEEDBACK?
72. More to come…
73. ↓ fields
 Less fields, reduce required fields.
 Automatically populate where possible. * required Easily express yourself
 Quick and simple Rate this feature: bad good great ↓ barrier to entry
 Avoid login, be contextual, avoid context switching.
75. fake it ‘till you make it
77. http://developer.atlassian.com/design
79. fake it 
 ‘till you make it SAVE
 $$$ SAVE
 TIME RIGHT THING
80. Reduce friction Fake it ‘till you make it
81. http://bit.ly/AgileFeedbackLoops
82. Defining the problem Building the solution Getting feedback
83. Thank you. SHERIF@ATLASSIAN.COM • @SHERIFMANSOUR Questions?