Mapping Your MVP Product Development in 30 min or Less
Download as PPTX, PDF3 likes2,296 views
The document outlines the importance of agile product management, emphasizing user story mapping for effective product development. It highlights the iterative nature of agile methodologies, the role of user stories in representing business value, and the maintenance of product backlogs. Additionally, it promotes Salesforce's partner community resources and events for networking and education.
Mapping Your MVP Product Development in 30 min or Less
- 1. Accelerate Your Vision Mapping Your MVP Product Development in 30 Minutes or Less Rob Jacques Product Manager rob@codescience.com @inittowinit210 Jake Wills Product Manager jake@codescience.com @jwills
- 2. Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements. Safe Harbor
- 4. Agile Product Management Why is Story Mapping Important? Source: HCLS Industries Team
- 5. Agile and User Stories Overview
- 6. What is Agile? A group of software development methodologies with the following features: •Iterative and incremental development •Requirements and solutions evolve through collaboration •Teams are self-organizing and cross-functional •Adaptive planning, evolutionary development and delivery •A time-boxed iterative approach •A rapid and flexible response to change.
- 7. “Priorities” vs. “Scope” (Bang for the Buck) Adjust to New Information Quickly Monitor and Control Mechanisms Collaboration vs. Antagonism Working Code Every Two Weeks Continuous Feedback (“Fail Fast”) A Great Fit with SFDC & Cloud Computing Technologies Why Agile?
- 8. A user story represents a small piece of business value that a team can deliver in an iteration. While traditional requirements (like use cases) try to be as detailed as possible at the outset, a user story is defined incrementally. 1. User stories usually start off as an Epic, or a work item too large to be conceptualized by a developer. a. e.g. “The ability to purchase a product” 2. Story preparation exercises, inclusive of design outputs, refine larger Epic level stories into their component Features. a. e.g. “Shopping Cart”, “Products Catalog” 3. Further preparation decomposes features into buildable units of work that a Scrum team can fully deliver in an iteration. These are User Stories. Epics, Features, User Stories
- 9. User Stories are consumed by the Scrum team at the beginning of each iteration from the stack-rank prioritized product backlog for work. This is a vertical list of User Stories. This list is incredibly useful to the Scrum team. They pick from the top until the iteration is full. It is critical to maintain this artifact continuously so that the Scrum team experiences no ambiguity about work priority. Product Owners, however, have a very difficult time maintaining this priority due to the fact that as soon as the list grows beyond 15-25 user stories, our brains lose the ability to sort and remember disparate feature build order and overall product context. In the face of that very serious problem, what is the solution? Product Backlog
- 10. User Story Mapping The What, Why, and How
- 11. Product Backlogs always start easy to manage. Very soon you have hundreds of stories. Q: How is a product owner to prioritize this many items effectively? Q: How do we communicate the product at large to a wider audience? Q: How do we understand incremental enhancement via releases? A: User Story Map! Why Map User Stories?
- 12. Epics: • Large, system level functions • The breadth of the product • X-Axis is priority Features: • The breadth of an Epic, all the features that comprise that system function User Stories: • Stack-ranked priority • Use color, marker, and fill to reflect status • Grouping to reflect Release Plan (MVP) Introducing the User Story Map
- 13. The User Story Map is a living document, owned by the Product Owner. As User Stories are created, deleted, refined, and reprioritized, the User Story Map should reflect reality at a given moment in time. Let’s make one ourselves! Refine the Map!
- 14. Live Story Mapping Defining an MVP
- 15. Share Your Feedback, and Win a GoPro! 3 Earn a GoPro prize entry for each completed survey Tap the bell to take a survey2Enroll in a session1
- 16. Partner Community Your one-stop shop for education and engagement http://partners.salesforce.com/ • Partner Program Details • Communications • Training • Leads, Opportunities, & Projects • AppExchange Publishing • Webinars & Recordings • Office Hours • Sales & Marketing Resources • Technical Support
- 17. Looking for the Partner Session Replays and Slides? See the Partner Community Calendar – September 15-18, 2015 http://p.force.com/calendar
- 18. New ISV Module on Trailhead Earn your badge! https://trailhead.salesforce.com/module/isvforce_basics
- 19. Get into the Zone: The Partner Zone! :: Partner Community Theater :: Live feeds of the major Keynotes :: Free lunch served daily! :: Concierge :: Tech Expert Bar :: Partner Program Staff :: Charging stations :: Featured Partner Services :: Coffee Bar :: Prize Giveaways Daily partner networking events – 3:00pm - 5:00pm • Tuesday, Sept 15 – Luau Theme • Wednesday, Sept 16 – Global Theme • Thursday, Sept 17 – Fiesta Theme
- 20. Celebrate Success at the AppBash AppBash “I left my Cloud in San Francisco” When: Wednesday, September 16 Where: City View at the Metreon Who: Partners and Customers Access: Full Conference or Booth Pass plus ID required Time: 7:00pm – partners & alliances employees 9:00pm – customers and employees welcome
- 21. Thank you