DevOps is not just a practice, designation or concept, it is a smart collaboration between software developers and IT professionals, DevOps has become a most requirement for all big and mid-size organizations.

1. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
Seven Common Mistakes during
DevOps Implementation

2. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
Seven Common Mistakes
 Speed or Quality
 Separate DevOps Department
 Avoid Making ID a Bewildered Process
 Steady Rigidity in DevOps process
 No Magic Wand
 Respond Properly to the Pushbacks
 Testing at the end of Lifecycle

3. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
1. Speed or Quality
When it comes to DevOps then organizations consider that there must be great speed
in DevOps process and they try to even sometimes skip the testing step with no or little
amount of testing. DevOps Ensure -
Tips - Must not compromise quality to increase the speed
 Predictability
 Maintainability
 Improved Quality
 Lower Risk
 Cost Effective .
 Stability
 Streamline Delivery
Predictability
Maintainability
Improved
Quality
Lower RiskCost Effective
Stability
Streamline
Delivery

4. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
2. Separate DevOps Department
A commonly seen practice by DevOps implementers is the creation of a separate
DevOps department to manage framework and DevOps strategy.
Tips - Organizations must focus on the DevOps process rather than a new team or separate
department for operation execution.
Dev
Ops
DevOps

5. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
3. Avoid Making ID a Bewildered Process
Larger organizations have complicated processes and it becomes difficult to draft a
proper strategy for DevOps process for them.
Tips - Train your employees and educate them on this new process.

6. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
4. Steady Rigidity in DevOps process
Rigidity in DevOps process makes it a little bit complicated and disturbed.
1 It is critical to compliance with core DevOps tenants.
2 There must be intelligent adjustments.
 Repeat
 Ensured that key DevOps pillars will remain static
 Adjustments in internal benchmarking
 must backtrack and locate the root cause of diversion

7. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
5. No Magic Wand
DevOps implementation is not a magic and will not
be managed by itself. Manage various DevOps
related tasks like -
 Managing Resources
 Budget
 Goals
 Progress

8. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
6. Respond Properly to the Pushbacks
The core DevOps tenants :
 There will be a pushback when you will implement DevOps for the first time in your
enterprise.
 At the time of implementation, some of the employees or experts may be able to adopt
new technologies and tools
 while a few others may be asked to work with their old tools that may be replaced in
future.
Tip : When it comes to implementation of these tenants then there should be no compromise in
the implementation of these practices. Even the teams may be massively scattered and spread
out but the practices must be implemented properly.

9. www.JanBaskTraining.coCopyright © JanBask Training. All rights reserved
7. Testing at the end of Lifecycle
 Due to modern domain-specific language and open
source tool, performance testing can be done by
the developers. So, teams must take advantage of
such tools and test the application by themselves.
 Even testers or developers can do functional and
performance testing simultaneously by themselves
with the help of API endpoints. Ultimately, testing
must never increase the overall deployment time of
the software.

10. www.JanBaskTraining.comCopyright © JanBask Training. All rights reserved
Thank you
Happy learning