jaminbw (3/11/2014)

---

Gary Varga (3/10/2014)

---

I find it frustrating that, from the software development side, when attempting to engage the DevOps (under whatever moniker) to find out how the development team can deliver in a way they want to receive together with any tools and utilities that they would like (e.g. deployment/configuration/installation validators) that they often fail to respond or push back until the very last minute. Additional frustration rises when they then use their veto to stop a rollout and everyone looks at the development team and considers it their failure. I am not talking days but months of attempted engagement. I see it time and time again. Maybe they are overloaded, however, in my experience this is a vicious cycle which they can break when there is a helpful development team willing to cooperate.

I have seen the opposite too; development teams throwing their software in an unpackaged form expecting it to be delivered there and then. This, I should imagine, is where their frustration lies.

This article talks about the common goal and the method of resolution that can be summed up in a single word: cooperate!!!

I agree.

I have had software sent to me for "code review" on a Friday at 4:45 for a deployment that was expected on Monday morning. When you ask for changes in that short time line the developer was upset and pushed that this was expected delivered.

I have also seen The failure to respond from a DBA because someone sending in changes burned them with code that should have been tested better last time.

So some times it is being overloaded but, other times in that case it is just picking to work on the issue when you have plenty of time you can set aside. I will often respond fast and move quickly on deliverables from some one if I have not had problems with deploying things for them before but, wait until I can devote a whole day to a deployment for other people. Such as the person that sent code late of Friday and wrecked my weekend plans.