This document discusses an engineering-driven culture at a company. It emphasizes agile principles like continuous improvements, fast feedback loops, and releasing to production up to 30 times per day. It also covers estimating in short sprints, dealing with technical debt, adopting DevOps practices like automated testing and deployment, and having autonomous cross-functional teams organized by capabilities. The overall goal is to let engineers work efficiently, think things through, and ship the right solutions at the right time rather than meeting arbitrary deadlines.

1. ENGINEERING DRIVEN CULTURE
Roman Bugaev

2. CULTURE

3. CULTURE

4. CULTURE

5. INTERESTING FACTS

6. INTERESTING FACTS

7. INTERESTING FACTS
Unpredictable environment: 3X load in 2 months

8. PROCESS

9. AGILE - CONTINUOUS IMPROVEMENTS
Retrospectives / standups
Up to 30 releases to prod per day (CD)
Fast feedback loop / Fail fast
“Feel the pain" sessions
Week in support for onboarding
On duty schedule
Get involved

10. AGILE VS ENGINEERING
Deal with “tech debt”
Limit yourself (e.g. DB freeze)
20% of sprint dedicated to technical backlog
Measure (code quality, bugs, time to market)
Avoid “boiler rooms”
Measure twice, cut once (sometimes)
Agile architecture

11. ESTIMATES
2 weeks sprint - 26 data points for a year - insufficient
data to draw conclusions from
“Units of time”
Commitment vs. Forecast
Commitment to be professional/achieve goals/increment
Forecast for deliverables

12. CONCLUSION
Only add processes that reduce significant actual risk
Ship it when it’s ready, not before, not after.
Let engineers do their work, think things through and
write 15 lines of code instead of 150. Use code reviews,
testing, etc. The cost of shipping the wrong thing is
much higher than the cost of slipping arbitrary
deadlines to ship the right thing.

13. DEVOPS

14. DEVOPS
Dev – add new feature
Ops – keep system stable, fast and available
DevOps – combine both

15. DEVOPS
One team
Tests
Metrics & monitoring
Automate everything
Infrastructure as a code
Tests
Deployment
Alerting
Atomic increments

16. ARCHITECTURE

17. ARCHITECTURE
Cross functional teams
Organized around capabilities
Nothing shared
Separate repo, DB, independent deployment
Design for failure
Asynchronous design
Evolutionary design / Postpone decisions
Polyglot persistence & environment

18. TROUBLE SHOOTING / QA

19. RELEASES
Blue/green deployment & Feature toggling
Atomic update
Metrics/Logs/Alerts
Production tests

20. SUMMARY
Agile on steroids
Agile
DevOps
Engineering

21. @adforminsider