Things Product Owners need to know about Software Engineering

Transcript

1. Prioritising comfy seats but not the engine Things Product Owners need to know about software engineering @andrewnesling @andynesling @andynesling@mas.to
2. New Frontiers Executive Summary January 2017 My journey Had a lot of old cars! • Varied product experience • Large and small orgs • Common themes • Why I needed to care about software eng
3. Technical debt
4. Spotting Technical Debt • What Is Technical Debt? • Spotting technical Debt • When should we take it on?
5. Example - Spotting Technical Debt
6. Paying Off Technical Debt • Why should I care about it? • When should we pay it off? • How should we pay it off? • How much to pay off?
7. Rebuild or Refactor?
8. Rebuild or Refactor? • What are the problems with rebuilding? • What are the problems with refactoring? • Do we have to choose?
9. Software Architecture
10. Architecture - need to knows ? • Responsibilities • Interface • Evolution
11. Architectural considerations
12. Continuous Delivery
13. Continuous Delivery • What does it mean? • This feels risky? • How does it help? • Feature Toggle • It is not free!
14. Continuous Delivery
15. Testability & Observability
16. Testability & Observability • Why I care about this? • How to get at the data? • How to use the data?
17. Observability
18. Team Topologies
19. Team Topologies • Responsibilities • Interfaces • Evolution
20. Team Topologies
21. Fit for purpose?
22. Fit for purpose? • Fit now - Technical debt - Testability Observability • Fit to Evolve - Architecture - Rebuild/Refactor - Continuous Delivery - Team Topologies
23. Wonderful books