This document discusses shifting from an IT to a product mindset. It emphasizes focusing on customers and delivering value over cost and schedule. This involves adopting a profit center mentality and continuously improving products. DevOps is presented as a culture of collaboration, not a role or department. It involves developers understanding infrastructure and operations understanding code. Validated learning is discussed as focusing on minimum viable products, testing and learning through experiments and A/B testing to reduce waste and improve conversions. The goal is a team that loves finding better ways to delight customers and increase market share through cultural evolution.

1. Increasing
Business Impact
Focusing on value delivery

2. Getting in touch
@alaverdyan
narek@alaverdyan.com
agile.am/nverdian

3. Business Impact
Delivering Value and delighting customers
Increasing MARKET SHARE

4. Themes
IT PRODUCT
MINDSET

5. From IT to Product “Mindset”
• Focusing on “THE BUSINESS”
• Order-taking technology team
• Cost-center mentality:
constantly reducing costs
• Success = cost, schedule, scope
• Focusing on Customers
• Responsible engineering team
• Profit Center Mentality:
Reinvest profit in Product
• Success = Delighted customers
credit:
Marty
Cagan
(www.svpg.com)

6. From IT to Product “Mindset”
What is IT?

7. From IT to Product “Mindset”
Cross-functional
Cross-discipline
Product
development

8. IT PRODUCT
MINDSET
Themes
DEV
OPS

9. DevOps is NOT
a new role
a new profession
a new department

10. DevOps IS
Here’s the secret. I’ll tell you EXACTLY what devops means.
• Devops means giving a shit about your job enough to not pass the buck.
• Devops means giving a shit about your job enough to want to learn all the parts and not
just your little world.
Developers need to understand infrastructure. Operations people need to understand code.
People need to fucking work with each other and not just occupy space next to each other.
credit:
John
E.
Vinicent (http://blog.lusis.org/)
a culture

11. DEV
OPSIT PRODUCT
MINDSET
Themes
KAIZEN

12. Continuous Improvement

13. Continuous Improvement: Tools
Delivering fast requires
new methods… and new tools!

14. Continuous Improvement: People
-­‐ Everett
Rogers
• No Perfect tool
• No Tool that we keep forever!

15. DEV
OPSIT PRODUCT
MINDSET
KAIZEN
Themes
VALIDATED
LEARNING

16. Validated Learning
• Focusing on Minimum Viable Product
• Strip down all Extras
• Making it compelling
TEST & LEARN

17. Split testing
A/B test

18. Split testing creates complexity
• 21 active a/b/.. Tests
• Different experiences
16,777,216

19. Reducing biggest waste
• 66% of what we deliver adds no incremental value
Bare MVP
Stripped down MVP
Compelling MVP
Fake MVP ?

20. From teams to streams
Experimentation
/ innovation teams
$$ $ $$$
- $ $
$$ $ $$$
- $ $
Core engineering teams
SplitTests, MVP-s,
Time to market, failing
fast, disruption
Stability, Quality,
architectural vision,
consistency, big tickets

21. KAIZEN VALIDATED
LEARNING
DEV
OPSIT PRODUCT
MINDSET
Themes

22. Where could this all take you … ?
• Shift of focus: “Can this be done” - > “Should this be done”
• Seeing better converting customers improves confidence
• Improved confidence creates an environment of definitive action
• Experimentation discourages vagueness and keeps everyone on point
A team that loves finding better ways to delight
customers - > Increasing market share

23. Cultural Evolution

24. Get better, in delivering more value…
e-Commerce in 2016 and beyond