2. Using Atlassian Tools Itamar Goldminz Sr. Manager, Product Management Operations 2 Managing an Impure SaaS Model

3. What we’re trying to solve 3 Sales Engineering PM Client Input Product Vision Capacity

4. I will be talking about all of these: JIRA: Green Hopper Custom Fields RSS Feed (and some Ruby development) Transitions and Transition screens Confluence Smart page design Run Macro JIRA Issues Macro

5. Agenda 5 BackgroundApproachProcess Tools

6. Meet OPOWER 6 50+ Utility Clients, 10M + Households on Platform Agile software development delivered through a Software-as-a-Service business model

7. (Some) benefits of SaaS No need for duplication Leverage insights from one client to the rest Create a positive “network effect” Always deploy trunk 7

8. Meet our ecosystem Waterfall-ish clients $M deals Sale Cycle ~ 8 Months, contracts span multiple years Fixed time, fixed scope RFPs 8 More disciplined LT planning process The Roadmap is not just a “plan of intent”

9. Challenges  WYSIWYP  Strategy-driven product development  External Roadmap?!  Pure agile development: maximum flexibility = maximum value 9

10. #atlassiansummit Agile development / SaaS model pose unique challenges in some business environments and require creative mitigation techniques #summit11

11. Do nothing 11 SalesEngineeringPM

12. “It’s not us, it’s them” Shape the market – regulation & policy Sell clients on our vision of the product Be an agile evangelist All great. But not enough 12

13. “It’s not them, it’s us” Carefully balance strategy-driven and opportunity- driven product development Deep product empowerment of account specific experts (sales, engagement managers) 13

14. #atlassiansummit Friction between your business/development model and your market is your problem (not your clients’). Be proactive. Adapt. #summit11

15. Easily communicable requirement model Common language is a pre-requisite for everything else Handle requirements of different scale Need to address varying levels of uncertainty 15

17. Investment themes Not a requirement Not estimated Ensures alignment JIRA custom field 17

18. Initiatives Project-like Product-led decomposition Goes on Roadmap Estimate using DTIs (JIRA custom field) 18

19. Features Avoid “Epic” Anti patterns Functional collection of user stories Joint (PM/Dev) decomposition Goes on wave (release) plan Leads estimate using story point ranges 19

20. User stories Nothing new here Decomposed by leads Goes on iteration plan Teams estimate using story points 20

21. Easily communicable requirement model 21 TypeEstimation CurrencySize Investment Theme %pct of roadmapN/AEnsures RM-strategy alignment InitiativeDTI2-8Equivalent of a “project” in a continuous development framework FeatureSP Range0-3 DTIS Functional collection of user stories User StorySP<1/4 DTI

22. Case study: rate analysis tool 22 Initiative Feature User Story 1 2 3 4

23. Balancing strategy and opportunity 23 20102011

24. The token system Minimizes disruption to the strategic road map but still enables us to win deals 24 RFPTriageCommitSOW

25. Committing & tracking 25 Token System

26. 26 Commitment? Status Token Budget DTI Due date

27. “Run” + “JIRA Issues”

28. Tokens case study Multi $M RFP Saying “yes” to everything: 25 DTIs, ~15% of development capacity for 18 months Using the “token system” resulted in: Productive discussions and creative solutions to trim scope Tough compromises on both sides Scope of work reduced to <10 DTIs 28

29. #atlassiansummit Consider using a “Token System” to balance strategy and opportunity driven product development #summit11

30. Live roadmap: JIRA+Ruby+mongoDB 30

31. Live Roadmap: Jira+Ruby+mongoDB Filtering Metadata Details Release Title

32. Not your typical release notes What got done in the last iteration? Planning vs. delivery What will get done in the next iteration? What’s in the pipeline? 32

33. Different people are looking for different things Changes to the product that affect sales Set expectations with existing clients Configuring the product to enable new features General stuff we’re working on 33

34. Code Name Key features Tech impl Demo Day vids Screenshots

35. One line. Just the important stuff

36. Release dates Intentionally vague

37. #atlassiansummit Product empowerment tools: Interactive Roadmap Kick-ass release notes #summit11

38. Pushing the envelope Agile Enterprise-level long-term capacity planning: 38 Old SchoolNew Skool DatesIterations IndividualsTeams Man-hoursDTIs

39. Agenda Background – balancing client input, product vision and engineering capacity in a challenging environment Approach – balancing strategy and opportunity, empowerment Process – requirement model, token system Tools – live roadmap, awesome release notes 39