Few pointers from the book Accelerate- Science of lean software and devops

1. People are organisation #1 Asset, but that is not how organisation operate
2. Can Devops solve the problem to build secure,resilient,rapidly evolving distributed systems at scale?
3. 31% of the industry is not using continuous integration and delivery
4. Focus on capabilities not maturity which doesnt allow continuos improvement,Capability models are multi dimensional and dynamic
5. Few lines of code for a solution rather more lines which increases maintenance and higher cost of change
6. 4 metrics to focus - delivery lead time,deployment frequency,time to restore service(MTTR),change fail rate
7. Reducing batch size reduces cycle time,variability in flow,accelerates feedback, reduces risk and overhead
8. For High performers deployment frequency in on demand(multiple deploys per day), Lead time to change is < 1 hour,MTTR is < 1 hour,change failure rate is 0-15%.
9. Keep branches short lived (less than one day work) and integrate in to trunk/master frequently
10. Automated unit and acceptance test should be run against every commit to version control to give developers for fast feedback on changes
11. Collaboration is required across teams - UX, developers, testers,product and operations resources
12. Version control for Application code,System configuration,Application configuration,Scripts for automating build and configuration is mandatory for developer excellence
13. Continuous delivery - Continuous delivery, Deployment automation,Continuous Integration,Trunk based deployment,Test Automation, Test data management, Shift left on security, loosely coupled architecture,Empowered teams,Monitoring and Proactive notification
14. Westrum Organisation culture - Risk Shared, Messengers trained,High cooperation,Bridging encouraged,Failure leads to enquiry, Novelty implemented
15. Impact of continuous delivery - less deployment pain, less burnout
16. Best performers spend 49% of their time in a day for new code, 21% on unplanned work/rework,30% on other work(meetings, maintenance etc)
17. TDD(Test driven development) forces developers to create more testable designs
18. Focus on short continuous merging and integration time periods
19. Security management is often overlooked
20. Lean management - Limit work in progress,Visual management,feedback from production,light weight change approvals
21. Only high risk changes like data base changes need to go for CAB approval
22. Lean Product development -work in small batches,make flow of work visible,generate and implement customer feedback and team experimentation
23. Build systems that are designed to be deployed easily in to multiple environments.can detect and tolerate failures in other environments and can have various components of system updated independently
24. Burnout - due to work load and value conflicts between individual and organisation
25. eNPS - Employee Net promoter score to improve operations efficiency, if employees are treated well, they will take care of the client and customers well
26. Transformational leadership - Vision, Inspirational leadership,Intellectual stimulation,Supportive leadership,Personal recognition
27. Give flexibility to work on technical debt, create space after releases to learn new tools, capabilities etc, allow employees to work on side projects for creative thinking

It was an interesting read quite while ago, just thought of sharing it after practicing it. Please let me know your views