DevOPS implementation - Practical approach - Continuation...
Nelson Kulandairaj
Championing IT Service Delivery & Operations | COO certified from IIM Lucknow | Emerging Technologies | Startup advisor | Industry-Academia connect | Board of Studies Member | Public Speaker
#DevOPS #Agile #Automation #BlamelessCulture #CrossFunctionalTeams #IncrementalDelivery #CI/CD
This is in continuation to my previous post on this captioned subject.
In this post I want to talk about #BlamelessCulture (the term I learnt during my #Agile journey): this can be related to one of the pillars of #Scrum #Empiricism: #Transparency and one of the principles of #Agile : “Build Projects around Motivated Individual. Provide Them the Environment and Support They Need and #Trust Them To Get The Job Done”
Based on my personal experience, for implementing #DevOPS kind of transformation initiatives a high level of #Transparency and #Trust that build a #BlamelessCulture is a must. Otherwise the whole initiative will be a failure and the whole transformation will be a futile attempt.
Let's take this scenario : A team member missed to run one of the test cases and that resulted in an UAT bug instead of getting caught during the SIT/Regression testing time. First there should be #Transparency in place (enabled through a process) to let the entire team know that such an incident (bug/issue) is reported, and the root cause is/is being located and the leadership team should have the #Trust that the team will resolve that issue. If required, additional helping hands should be extended to resolve the issue through effective #Collaboration. Don't ever talk about the individual or the mistake he/she had committed during this (resolution) time. However, during the retrospective session - hear from that individual regarding this miss and offer him/her suggestions to avoid this happening in the future. There could be solutions in the form of Test Automation (assuming Test Automation is not in place by then), even a review of the SIT/Regression test cases may result in a trimmed version of the test cases that can be run in a shorter time frame with optimal coverage. This is one among the opportunities to display a great #EmpathyQuotient, too.
What I have shared here is just one scenario – towards building a #BlamelessCulture team/organization. However, "response-behavior" to a situation, attitude, and the leadership/working styles of the team & organization could foster building the #BlamelessCulture efficiently. Tough but definitely possible.
Will continue to share to learn…
Chief Architect, Microsoft Practice Leader & India Microsoft Community Leader at Capgemini. Igniting Potential. Empowering Futures! Unleash Talent!
5 年We instinctively react to the a situation to see who has done wrongly than what has gone wrong.? Lot of times we discuss on a person than on the issue.? Conscious effort need to be made to stay with the issue.? This will go a long way in building trust with teams.