Your team uses Agile to rapidly evolve its development plan based on customer needs. However your CEO needs feature commitments for an upcoming tradeshow announcement, and your customers are harassing your support team about when a favorite feature will be built. Learn how to bridge this divide using product roadmaps and get several best-practices for implementing them in your product organization.

1. Product
Roadmapping
How To Bridge Agile &
Company Objectives
Samuel Clemens
Founder & CPO, InsightSquared
@scclemens
linkedin.com/in/sclemens

2. Mindset Gap
Between Execs
& Product?
CEO:
Where will we be
in four quarters?
Product:
…um, we do 2
week sprints…

3. Management Team
Discussions About
Product Priorities?
We need
Feature X!
~ Sales
Let’s discuss
pros &
c…MMMPH
~ Product
We need
Feature Y!
~ Services

4. When are we
getting
Feature X?!
We’re not telling!
We do Agile™!!
^%@$#^%@$
#^%
Product
Communications
with the Front Line?

5. A roadmap is just a
communications
tool
The details matter
less than several
salient
characteristics

7. 1. Calibrate
the roadmap
timing
according to
your
company’s
metabolism
a
b
c

8. 2. Make the
uncertainty
explicit

9. 3. Keep the
granularity
above the
feature level

10. 4. Be careful with the
distribution:
- Only Execs?
- Whole company?
- Customers?

11. 5. Connect the
company roadmap
to the product
roadmap

12. 6. Describe why you
moved the cheese

13. BONUS ROUND
Leverage your new
roadmap into analysis

14. Thank you!
Samuel Clemens
@scclemens
linkedin.com/in/sclemens