What should Product Managers know about the Engineering organization? Why should they care? How will understanding the goals and processes of the engineering team help you get better results?

1. Product and Engineering
GSB S509
February 2017

2. About.me
IDF/ 8200
Engineer
Team Lead
Eng. Manager
OffScale
Founder
CEO
EverythingMe
Head of Search
Life360
PM
(Location,
Partnerships,
Globalization)
Clear Lending
Partner
Mortgage Geek

3. Agenda
Why Should You Care?
Meet the Engineering Team
Development Processes
Behind The Scenes

4. Why Should You Care?
Building Products is a Team Sport

5. Meet the Engineering Team
Who is Who

6. Who is on The Team?
QAEngineers
Process
Management
CTO

7. Different Teams are Different
What shapes a team?
TechnologyProduct Type
Quality
Requirements
Industry

8. Quality
Future-enabled
Solving hard problems
Staying current
Impactful work
Don’t throw away work
Motivation & Drivers

9. Development Processes
How is this managed? Why Do I care?

10. Waterfall
How it used to be done
Works if team understands
both problem and solution well
Easier progress measurement
Single rigorous planning phase

11. Agile
How we do it now
Complements Customer
Development
Iterative, Team-based,
delivery-driven
Prioritization by business
value

12. Time Estimates
Sometimes, they just don’t know
Very accurate
estimate
Complete
unknown
I can imagine
every line of
code
I think I know
what needs to
be done, done
similar things
IDK
I have an idea,
but it’s new
territory
2X 4X ?

13. Making Product Decisions
When something has to give
Cost
Time
Quality
Scope
Product concessions
Vs.
Engineering concessions

14. Behind The Scenes
How The Magic Happens

15. 3rd Party Functionality
SDKs
Open Source
APIs OEMs Services

16. (continuous) Delivery
Getting your product to the customer
Rapid
Prototyping
Continuous
Integration
Software Hardware

17. Thank You
@a_taichman
taichman@gmail.com