DevOps Enterprise Summit81
Are there any anti-patterns of DevOps? If so, please explain.
Creating a DevOps team that is itself a silo
Creating a third team called “DevOps” that is the approval committee for anything “DevOps” to be approved and rolled out in the organization through the Project Management Office.
@FletcherJofanon Exactly. I see this all.the.time.
My most favorite anti-patter is having a team that says "we are the devops team and we set up everything for you and we have a blacklog to manage your request"
DevOps without regular releases and feedback from real users contributing to the product backlog - fake DevOps
Silos - including creating separate DevOps team, breaking down the silos and providing visibly across the systems
Commenting out failing tests!
centralized command control which create wait states in the value stream. This can be a change board or a centralized Performance testing team or Security testing team
I read countless CV's from people that once wrote a batch file and that are now "DevOps engineers"
Using the word DevOps to describe your old school, siloed way of working because you implemented one DevOps tool
Another anti-pattern - overhearing in post-mortem - "who did it?"
Pushing from the top without having bottoms up support and effort
@FletcherJofanon Creating a silo DevOps Team is absolutely THE anti-pattern
OH @carmendeardo : "like people going to quality conference & coming back and creating a Quality Team"
@schwartz_cio lol! yes!
OH - The Load Balancing team can't load balance themselves @topopal @realgenekim
DevOps anti-pattern is DevOps = tool. You need tools but you need collaboration, systems thinking feedback more
"Center of excellence" has a sense of eliteness to it.
@topopal - and lots of COEs often don't demonstrate excellence
Sometimes not obvious at all: amazing PPT by @andyburgin on Sky Betting Data Warehouse https://www.youtube....
Big Bang thinking is still a big anti-pattern. DevOps requires smaller batches. Hard to claim "DevOps" with a 6 mo deployment cycle
OH @scottprugh "Once people/teams go above 50%, queue times go exponential"
Jason A Cox
@topopal Anti-pattern: Architecture and engineering excellence can only come from CoE experts & towers
There is a ton of SrummerFall out there with the kabuki of Lean/Agile terminology over a big-batch waterfall process.
OH: "[without slack time], we feel like we're just stuck in a feature factory [that doesn't actually create value]"
Another very common antipattern is not investing in engineering system improvement.
On antipatterns, I'd also tag V-model thinking, that forces slow testing over fast feedback.
Assumptions about user behavior, rather than user-centric design and testing in production
@schwartz_cio +! on testing in production, with quantitative and qualitative validation.