- 1. How to develop software faster and have more stable releases?
- 2. How to develop software faster and have more stable releases?
- 2.1. Self introduction
- 2.2. Goal of the company / organization
- 2.3. Goal of the company / organization
- 2.4. Goals of employees
- 2.5. Goals of employees
- 2.6. Goals - Contradiction?
- 2.7. Business needs for change
- 2.8. Value creation - Time is Money
- 2.9. How to Faster, Cheaper, Better?
- 2.10. Value creation
- 2.11. Product types
- 2.12. Fast or stable?
- 2.13. Release frequency
- 2.14. Deploy per day VS value (Value creation)
- 2.15. MTTR - Mean time to repair
- 2.16. Old model
- 2.17. Wall of Confusion
- 2.18. The business cost
- 2.19. The human cost
- 2.20. High Performing organizations
- 2.21. High Performing organizations
- 2.22. Getting faster
- 2.23. Priorities
- 2.24. Small Batch size
- 2.25. Reduce Multitasking
- 2.26. Multitasking Exercise
- 2.27. Build only what you need
- 2.28. Create fast feedback loops
- 2.29. Feedback Techniques
- 2.30. Learn from the mistakes
- 2.31. Retrospectives
- 2.32. Daily feedback meetings
- 2.33. Continuous Integration (CI)
- 2.34. Toyota Andon cord
- 2.35. Andon cord
- 2.36. Test-Driven Development
- 2.37. Optimizing Developer Effort
- 2.38. Pair Programming
- 2.39. Refactoring
- 2.40. Architecture
- 2.41. Conway's Law
- 2.42. Small Teams
- 2.43. End-to-end Ownership
- 2.44. Project boundaries
- 2.45. Design
- 2.46. Features
- 2.47. Continuous Deployment (CD)
- 2.48. Decouple deployment
- 2.49. Blue-green deployment
- 2.50. Canary release
- 2.51. Infrastructure as code
- 2.52. DevOps loop
- 2.53. Continuous Improvement
- 2.54. Hierarchy of abstractions
- 2.55. Resilience testing
- 2.56. What is in there for me, the developer?
- 2.57. The transformation process
- 2.58. Theory X and Theory Y
- 2.59. Time boxing experiment
- 2.60. Greenfield projects VS brownfield projects
- 2.61. Getting Started
- 2.62. Top down approach
- 2.63. Team level approach
- 2.64. Resources
- 2.65. Contact me
- 2.66. Sources