As we look to enhance our ways of working and shift from project-based methodologies to product thinking, it's easy to overlook the technical aspects of this change. Let's not make that mistake.
In this webinar, Cprime's Ken Robinson, and Anne, Chief Product Coach, delve into the technical aspects of switching from project to product. What does this mean for our engineers, testers, and product teams? Equally important, what does this mean to the health, resilience, and maneuverability of our codebases and environments?
We'll approach these topics across the following dimensions:
-Development - new product development as well as maintenance and enhancements
-Testing
-Delivery Lifecycle
Lastly, we'll bring it all together to illustrate how engineering for speed + quality and the concept of "total product ownership" reduces time to market, enhances product quality, and fuels maneuverability.
4. 4
Agenda
01 Project to Product: Setting the Stage
02 Why Do We Need To Go Fast?
03 How to Achieve Speed + Quality
04 Harnessing Change for Competitive Advantage
05 Keys to Success and Q&A
5. From Project to Product
Product Over Project
05/12/2021 | Anne Steiner, VP of Product & Technology
6. 6
A project is a temporary
endeavor undertaken to
create a unique
product or service.
A product is the thing
that you build
(or the service you provide)
that impacts people.
7. 7
From Project to Product
Plan
Driven
Value & Quality
Driven
Cost Schedule
Scope (Rqt’s) Cost Schedule
Scope (Outcomes)
Fix cost and schedule;
float the scope
Fix the scope; float
the cost and schedule
Project
The plan drives cost &
schedule estimates.
Product
The vision drives outcome-
based roadmaps. Business
need drives investment.
Time, Budget, Scope – Pick 2
9. 9
Customers Need & Expect More
● “Why is that new feature/bug
fix/stability improvement taking
so long?”
Everything is mission-critical
10. 10
● Missing/ineffective features
● Production defects
● Outages
● Slow performance
● Lost/stolen data
● Slow/unhelpful support
Obstacles to Customer Satisfaction
These all impact customer experience.
Product teams need to account for all of them.
15. 15
● Speed + quality is unfamiliar
○ “Do you want it fast or do you
want it good?”
● Traditional IT intentionally slows
things down
Old habits are hard to break.
How Do We Move Fast Without Breaking Things?
16. 16
Achieving Speed + Quality
Development Make your software reliable and easy to change
Quality Shift quality left
Delivery Streamline the path to production
Management Measure and manage the flow of value
17. 17
Cloud-native, microservices,
oh my!
• Simplicity
• Scalability
• Resilience
• Extensibility
Independent deployability
• Teams & architectures
Making Software Reliable & Easy to Change
18. 18
● Leverage our knowledge to consistently get better
● “We value refactoring over perfect code”
● Refactoring improves speed + quality
● Refactor incrementally (duh :-))
The Refactoring IS a Required
19. 19
● Early discovery = easier/cheaper/faster to fix
● Make testing part of development
● Design & test for dependability up front
● Minimize rework through conversation
Delivering value, not simply work - it’s everyone’s work
Shifting Quality Left
20. 20
● Focus on incremental delivery
● “We value how long over how many”
○ End-to-end cycle time
○ Work mix
○ Time to remediate
How often do you deliver new features
to customers?
Measuring & Managing the Flow of Value
23. 23
Follow us on Social Media
Share in the conversation & keep updated on
thought leadership, events & more!
on LinkedIn, Twitter, Facebook, & YouTube