DevOps is an emerging IT role but also a culture; and changing culture does not happen overnight
- Elevate empowerment and give courage to people to "raise hand" and volunteer to fix things. Even if they are wrong- interest in areas outside one's primary role is good for the entire DevOps culture.
- Shared accountability - no blame game between developers, PMs, testers, QA, etc.
- Do not want to have to be dependent on "lone genius" or "firefighter"- need to share and transfer knowledge.
- Offer time to learn. Encourage hacking for new features and for hardening security and find bugs.
- Embrace failures in retrospectives to prevent repeated mistakes on future work.
- Provide the right incentives to motivatve the values you want to reward: reward delivery of quality vs. fire fighting.
- Understand "value streams" (esp. value stream bottleneck and how can we optimize all constraints) to know where to spend time accordingly.
- Focus on CONSTRAINTS.
- Avoid Configuration Drift- Config changes should cascade to all environments (QA, DEV, TEST, STAGE, PROD).
- Automate the Path to Production.
- Use pull-based systems so that people integrate each others changes and learn how everything works in unison/concert.
- People should not fear for their jobs- Systems Admin becomes more important not less so, in DevOps
- DevOps is how you work not just what you buy or what tech you are using.
- Total adoption happens in stages/iterations.
- Traditional Project and Documentation mindset is outmoded, outdated, and disconnected from a living IT mission.
- Lack of DevOps leads to waste and waiting (waiting for ppl with the right skills to work on things vs. having team that can easily shift contexts or frameworks/languages).
- SHARE KNOWLEDGE AND EMPOWER COLLEAGUES TO DO MULTIPLE TASKS AND UNDERSTAND SOME OR ALL ASPECTS OF MULTIPLE RESPONSIBILITIES OF THE SOFTWARE PROCESS CHAIN.
Reference: https://app.pluralsight.com/library/courses/devops-big-picture/table-of-contents (Richard Seroter)
No comments:
Post a Comment