14. How long would it take your organization to deploy a
change that involved just one single line of code?
Do you do this on a repeatable, reliable basis?
Mary & Tom Poppendieck
Implementing Lean Software Development
Determine cycle time
15. Reduce risk of release
« If it hurts, do it more frequently »
58. noun
1 a feeling of fear or agitation about something that may happen: the
men set off in fear and trepidation.
2 trembling motion.
Embrace change
trepidation | trep·i·da·tion
60. Do not be afraid to fail.
Learn what doesn’t work first, then see how to make it better.
61. Continuously improve
Japanese for "improvement", or "change for the better"
Refers to philosophy or practices that focus upon continuous
improvement of processes in manufacturing, engineering, and business
management.
Kaizen | 改善
When business come to you and say you’re releasing too frequently – you’re on the right way.
Short Lead time fasterFeedbackCD is expensive. Leanisabout WASTE not COST. High long-term ROI.Increases motivation, as you get things done faster, less stress
Большинство– тормозы. Неэффективность процесса и ОПАСНОСТЬ.
The most complex task is push button.
Create environment where people get responsible for consequence of their action and they will care (DevOpsphylosophy)
- Modules / services / entities / staticcontent
Whybranches? Parallelization. Multipleversionsoftheapp.Unability to keepapplicationstableduringdevelopment.Onegoal, extracare. No merges. Oneversion, pushupteamsforsynchronizationBringspainforward, raisesprofessionalismIsolationillusion
If people have to use feature branch, something is wrong with your architecture.
3WReduce TTD (Time to detect), TTR (Time to recover)