11 common DevOps Bottlenecks

1. Inconsistent Environments

Create standard infrastructure blueprints and implement continuous delivery to ensure all environments are identical.

 2. Manual Intervention
Automate the build and deployment processes and implement a test automation methodology like test driven development (TDD)

3. SDLC Maturity
Invest in training and hold blameless post mortems to continously solicit feedback and improve.

4. Legacy Change Management Processes

Companies with legacy processes need to look at how they can modernize processes to be more agile instead of being the reason why their company can’t move fast enough.


5. Lack of Operational Maturity

Assess your operational processes, tools, and organization and modernize to increase agility and transparency.


6. Outdated testing practices

Quality is everyone’s responsibility, not just the QA team.


7. Automating waste

Automate processes after the bottlenecks are removed.


8. Competing or Misaligned Incentives and Lack of Shared Ownership

Work with HR to help change the reward and incentives to foster the desired behaviors.

9. Dependence on Heroic Efforts

If your organization relies on heroes, find out what the root causes are that creates these dependencies and fix them fast.

10. Governance as an Afterthought

Assign an owner and start building a plan for scaling DevOps across the organization.

11. Limited to No Executive Sponsorship

If running a grassroots effort, gather before and after metrics and be prepared to sell and evangelize DevOps upward.





Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros
Read more

Sense of urgency the Agile way

“You must take action now that will move you towards your goals. Develop a sense of urgency in your life.” H Jackson Brown Jr Why sense of Urgency: In a complex product development especially which is just not an enhancement but development from the scratch, a sense of urgency is very much needed.  In today's fast changing world, if there is no sense of urgency then there is a high possibility that customer will leave you soon.  Who builds the sense of urgency: Leadership team need to build this and this is done by communicating the vision and value the product development will give. if the core team who is in charge of development do not know why they are building and what is the motivation then there is a high possibility that your development team will lose focus in building a world class product. How does Scrum/Agile helps: Product owner /Scrum Master in a typical Scrum model work in a aggressive mode especially with the dependent stakeholder
Read more