Product Roadmaps Relaunched. How to Set Direction while Embracing Uncertainty - Helion
ebook
Autor: C. Todd Lombardo, Bruce McCarthy, Evan RyanISBN: 9781491971673
stron: 272, Format: ebook
Data wydania: 2017-10-25
Księgarnia: Helion
Cena książki: 143,65 zł (poprzednio: 167,03 zł)
Oszczędzasz: 14% (-23,38 zł)
A good product roadmap is one of the most important and influential documents an organization can develop, publish, and continuously update. In fact, this one document can steer an entire organization when it comes to delivering on company strategy.
This practical guide teaches you how to create an effective product roadmap, and demonstrates how to use the roadmap to align stakeholders and prioritize ideas and requests. With it, you’ll learn to communicate how your products will make your customers and organization successful.
Whether you're a product manager, product owner, business analyst, program manager, project manager, scrum master, lead developer, designer, development manager, entrepreneur, or business owner, this book will show you how to:
- Articulate an inspiring vision and goals for your product
- Prioritize ruthlessly and scientifically
- Protect against pursuing seemingly good ideas without evaluation and prioritization
- Ensure alignment with stakeholders
- Inspire loyalty and over-delivery from your team
- Get your sales team working with you instead of against you
- Bring a user and buyer-centric approach to planning and decision-making
- Anticipate opportunities and stay ahead of the game
- Publish a comprehensive roadmap without overcommitting
Osoby które kupowały "Product Roadmaps Relaunched. How to Set Direction while Embracing Uncertainty", wybierały także:
- Tkinter GUI Application Development Blueprints, Second Edition 157,37 zł, (29,90 zł -81%)
- Mastering SVG 135,91 zł, (29,90 zł -78%)
- Fixing Bad UX Designs 124,58 zł, (29,90 zł -76%)
- Python Web Scraping Cookbook 124,58 zł, (29,90 zł -76%)
- Hands-On Chatbots and Conversational UI Development 124,58 zł, (29,90 zł -76%)
Spis treści
Product Roadmaps Relaunched. How to Set Direction while Embracing Uncertainty eBook -- spis treści
- Praise for Product Roadmaps Relaunched
- Foreword
- Preface
- Dear Roadmap
- Who Is This Book For?
- How to Use This Book
- Why Listen to Us?
- C. Todd Lombardo
- Bruce McCarthy
- Evan Ryan
- Michael Connors
- Acknowledgments
- 1. Relaunching Roadmaps
- What Is a Product Roadmap?
- Key Terms and How Were Using Them
- Product
- Stakeholder
- Customer
- Where Did Product Roadmaps Come From?
- Requirements for a Roadmap Relaunch
- A Roadmap Should Put the Organizations Plans in a Strategic Context
- A Roadmap Should Focus on Delivering Value to Customers and the Organization
- A Roadmap Should Embrace Learning
- A Roadmap Should Rally the Organization Around a Single Set of Priorities
- A Roadmap Should Get Customers Excited About the Product Direction
- A Roadmap Should Not Make Promises a Team Cannot Deliver On
- A Roadmap Should Not Require Wasteful Up-Front Design and Estimation
- A Roadmap Should Not Be Conflated with a Release Plan or a Project Plan
- Summary
- 2. Components of a Roadmap
- Primary Components
- Product Vision
- Product Vision Is Your Guiding Principle
- Business Objectives
- Business Objectives Help You Measure Progress
- Timeframes
- Broad Timeframes Avoid Overcommitment
- Themes
- Themes Focus on Outcomes Rather Than Output
- Disclaimer
- The Disclaimer Protects You (and Your Customer)
- Product Vision
- Meet the Wombat Garden Hose Co.
- Developing the Wombat Roadmap
- Secondary Components
- Features and Solutions Show How You Intend to Deliver on Your Themes
- Stage of Development
- Confidence
- Target Customers
- Product Areas
- Secondary Components Added to the Roadmap
- Complementary Information
- Project Information
- Components in Context
- Components in Context
- Components in Context
- Components in Context
- Summary
- Primary Components
- 3. Gathering Inputs
- Understand Where Your Product Is in Its Life Cycle
- New Product Phase
- Growth Phase
- Product Expansion Phase
- Harvesting Phase
- End-of-Life Phase
- Gathering Input from Your Market
- Understand Your Ecosystem
- Define the Problem and the Expected Outcome of the Solution
- Gathering Input from Your Customers
- Customer Roles
- User Types
- Users Versus Buyers
- Roles Versus Personas
- Gathering Input from Your Stakeholders
- Summary
- 4. Establishing the Why with Product Vision and Strategy
- Mission Defines Your Intent
- Vision Is the Outcome You Seek
- Values Are Beliefs and Ideals
- Product Vision: Why Your Product Exists
- Value Proposition Template
- Example for Our Wombat Hose
- Duality of Company and Customer Benefit
- Product Strategy: How You Achieve Your Vision
- Objectives and Key Results
- The 10 universal business objectives
- Key results (and metrics)
- Outcome Versus Output
- Timing
- Case Study: SpaceX
- Business Objectives
- Themes
- Key Results
- Summary
- 5. Uncovering Customer Needs Through Themes
- Expressing Customer Needs
- Themes and Subthemes
- Ways to Uncover Themes and Subthemes
- User Journeys and Experience Maps
- Existing Product Needs
- System Needs
- Opportunity-Solution Trees
- Using Job Stories and User Stories to Support Themes
- Themes Are About Outcomes, Not Outputs
- Relating Themes Back to Your Objectives
- Real-World Themes
- The High Cost of Space Travel
- Slacks Theme-based Roadmap
- GOV.uks Gantt Chart with Benefits
- Summary
- 6. Deepening Your Roadmap
- Features and Solutions: How They Can Work with Themes
- When and Why Do Features Appear on the Roadmap?
- Probable solutions
- Infrastructure solutions
- Carryover solutions
- Where Do Features Appear on the Roadmap?
- Buffers feature-level roadmap
- Feature questions
- When and Why Do Features Appear on the Roadmap?
- Using Stage of Development
- Stage of Development Questions
- Communicating Confidence
- Confidence Questions
- Identifying Target Customers
- Target Customers Questions
- Tagging Product Areas
- Product Areas Questions
- Secondary Components Summary
- Strive for Balance
- Summary
- Features and Solutions: How They Can Work with Themes
- 7. Prioritizingwith Science!
- Why Prioritization Is Crucial
- Opportunity Cost
- Shiny Object Syndrome
- Exponential Test Matrix Growth
- Features Versus Tests
- Bad (but Common) Ways to Prioritize
- Your, or someone elses, gut
- Analyst opinions
- Popularity
- Sales requests
- Support requests
- Competitive me-too features
- Prioritization Frameworks
- Critical Path
- Critical path for existing products
- Kano
- Desirability, Feasibility, Viability
- Desirability
- Feasibility
- Viability
- ROI Scorecard
- Strategy defines value
- Deliberate imprecision
- The effort side of the equation
- Estimating effort without frightening engineers away
- T-shirt sizing
- Think cross-functionally
- Risks and unknowns
- Critical Path
- A Formula for Prioritization
- A simple scorecard
- A more complex scorecard
- MoSCoW
- Tools Versus Decisions
- Dependencies, Resources, and Promises (Oh, My!)
- Prioritization Frameworks
- Summary
- Why Prioritization Is Crucial
- 8. Achieving Alignment and Buy-in
- Alignment, Consensus, and Collaboration Walk into a Bar...
- Alignment
- Consensus
- Collaboration
- Shuttle Diplomacy
- Shuttle Diplomacy for Product People
- Why Does Shuttle Diplomacy Work?
- How to Engage in Shuttle Diplomacy
- Shuttle Diplomacy Canvas
- Whats Difficult About Shuttle Diplomacy?
- Rapport
- Location
- Meetings and Workshops
- Presenting Recommendations
- Co-creation Workshop
- Workshop agenda
- Hopes and fears
- Vision and goals
- Back-plan
- Sizing and prioritizing
- Software Applications
- Summary
- Alignment, Consensus, and Collaboration Walk into a Bar...
- 9. Presenting and Sharing Your Roadmap
- Why to Share Your Roadmap Internally
- Inspiration
- Alignment
- The IKEA Effect
- Why to Share Your Roadmap Externally
- The Risks of Sharing
- Overpromising and Underdelivering
- The Osborne Effect
- Competition
- Who should see your roadmap?
- Multiple Roadmaps? Not So Fast!
- Presenting the Roadmap to Stakeholders
- What the Development Team Needs in a Roadmap
- Secondary Components
- Features and solutions
- Stage of development
- Product areas
- Complementary Information: Platform Considerations
- Scalability
- Technology and infrastructure
- Complementary Information: Project Information
- Schedule and resources
- Dependencies and risks
- Status
- Secondary Components
- What Sales and Marketing Need in a Roadmap
- Secondary Components
- Stage of development
- Target customers
- Confidence
- Features and solutions?
- Complementary Information: External Drivers
- Secondary Components
- What Executives Need in a Roadmap
- Complementary Information: Financial Information
- Market opportunity
- Profit and loss
- Complementary Information: Financial Information
- What Customers Need in a Roadmap
- The Roadmap Presentation
- Preparation
- Case Study: Chef.ios Roadmap Presentation
- Dropping Like a Lead Balloon
- Making Changes
- CASE STUDY: Chef.ios Roadmap Presentation
- Dropping Like a Lead Balloon
- Summary
- Why to Share Your Roadmap Internally
- 10. Keeping It Fresh
- Roadmap Evolution
- How Far Out Should Your Roadmap Go?
- Planned Change
- Change Frequency
- Unplanned Change
- When Features Are Late
- Schedule
- Scope
- Resources
- Quality
- When Features Are Late
- When to Compromise on Quality
- Special Requests
- External Pressures
- Changes in Strategy
- Communicating Change
- Why
- What and When
- Roadmap Changes
- Forks in the Road
- Lather, Rinse, Repeat
- Summary
- 11. Relaunching Roadmaps in Your Organization
- How to Get Started
- Step 1. Assess your situation
- Roadmap Health Assessment Checklist
- Approach A: Course Corrections
- Approach B: The Full Relaunch
- Step 2. Get buy-in for change from from your key stakeholders
- Step 3. Train your stakeholders how to contribute
- Step 4. Start small and work incrementally
- Step 5. Evaluate your results and align on next steps
- Step 6. Keep relaunching
- Gillians Story of Roadmap Change
- Step 1. Assess your situation
- Postscript
- How to Get Started
- Index