The first time I heard of the Monday Morning Effect was when a customer told me that they had cured it using our deployment automation tools. My response was, “Huh.. the what effect?”
The Monday Morning Effect is actually a pretty common pattern. Deployments of new and updated software into production are executed over the weekend. On Monday, everyone (including the tired deployment team) spends the morning trouble-shooting and putting out fires as the updated systems are used. Once things settle down, the deployment team heads home and gets some rest while the rest of the stakeholders keep a careful eye on the systems.
Big systems, deployed infrequently by hand almost always will have problems. There are simply too many things to get right in the deployment to avoid a typo here or there. Automating the process will reduce the risk of typo and help give teams the freedom to deploy a bit more often – reducing the batch sizes and associatedrisks.
A couple weeks ago I was reminded of the pervasiveness of the Monday Morning Effect when were scheduling a proof of concept with a prospective client. We had determined that we would need 3-4 days, and found a good week for tire kicking. Our engineer suggested starting on Monday. Naturally, the response was, “How about Tuesday? We have a big release over the weekend, so Monday won’t work.”
UrbanCode CEO and co-founder, Maciej Zawadzki, explains that Continuous Integration is more than just merging code. Join him as he explains some of the fundamentals of Continuous Integration in the third installment of the uChat video series.
Companies may not know exactly what DevOps is yet, but they know they want people with “DevOps” on their resumes. For the last few months, I noted the steady flow of “Wanted: DevOps Engineer” postings floating past on the forums I frequent. While in past presentations I’ve fought the idea that DevOps is a job title, I’m nearly ready to concede defeat.
The trend is definitely towards hiring people for jobs that require DevOps skills or titles. PC World reports on this trend with a look at what’s going on at the popular techie job site Dice. Over 200 listings per day show up with a mention of DevOps. Filling these positions is hard, and those with the skills are getting paid better and better. And while classic Web 2.0 players, and e-commerce players like Amazon and Ebay are present, you see more mainstream companies looking for these skills as well (NPR, Travelers Insurance, etc).
I think that for job seekers, this trend is one to take advantage of. If you were providing build, deployment, or release infrastructure and regularly interfaced with both App-Dev and operations teams, your resume should say, “Worked on a DevOps team that…”. You should do so because its true. We finally have a term for people who grok both sides of the house. Embrace it and run with it.
For everyone else, I think this is a pretty clear signal. It’s time to embrace your counter-parts on the other side of the wall and start working together more and more. This isn’t a fad. It’s the mindset IT shops are re-organizing themselves around.
I recently attended devopsdays Rome. This was my first time at a devopsdays conference and I enjoyed the mix of talks and open spaces sessions. It was obvious that the presenters and the attendees have felt the pain of trying to introduce continuous delivery in their organizations and were there to share stories and seek advice to help.
The theme for this conference was “Culture”. If DevOps is a “culture thing”, then surely we need to involve both Dev and Ops. The surprising part was that there did not seem to be anyone from the Dev side of things. In fact, there were topics like “getting Dev to think in terms of DevOps”. The goal being to entice developers to think about the infrastructure of their applications including the operational concerns such as: scalability, redundancy, performance, monitoring, and feedback.
Monitoring was a very big topic, being covered by some 70% of the talks. For this crowd, Puppet, Chef, and CFEngine define configuration management. But it stopped there. Adding all of the discussions about stacks, tools, and cloud together yields something that looks like PaaS. It allows them to provision and configure machines or virtual machines to provide well-managed and monitored services on which applications can sit. However, at that point, Dev has no skin in the game.
Application delivery is needed to get Dev thinking in terms of DevOps. Specifically, if while developing application components, developers need to concern themselves with how their components will be deployed to an environment and in a state where they can deliver value.
uDeploy deploys complex, multi-component applications. For example, a simple web site consists of a web component (WAR file) and a database component (DDL). Continue reading →
In last week’s “DevOps Imperative” webcast, I mentioned that DevOps is more directional than prescriptive. I mentioned that the key directions to follow were to push towards more collaboration and automation to enable your team to deliver more frequently with less risk.
Four of the principals and laws we cite most frequently in white papers and webcasts can help reinforce this direction and provide some needed checks as you begin transforming towards an organization whose path from idea to value (the software development lifecycle or SDLC in stodgy terms) needs to be more DevOps friendly.
What it is: “organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations”
Why you should care: Conway’s law points out that when we design some solution, and we put three teams on the project, the solution will likely have three sub-systems and the Continue reading →
I work with “The Enterprise” everyday. Sadly, this has nothing to do with Star Trek – just big companies with lots of internal politics. As our friends champion our products internally,the political challenges are often tougher than the technical ones.
If politics is going to be a barrier, it’s fair game to use political theory to fight back.
The Overton Window
The Overton Window is a concept that has been gaining traction over the past few years. The idea is that people are scared of extreme ideas, and prefer moderate ideas. To push an idea towards the idea of acceptability one can work hard to persuade the group that it is reasonable. Alternatively, an ally can propose a new and more radical idea that makes your idea seem reasonable by comparison.
A new idea fills the window of what the public regards as unthinkable, causing the desired idea to shift into the window of what the public views as sensible, without its proponents necessarily having explained any benefits of the desired idea. *