Self-brewed complexity is evil – fight it! It’s amazing to see again and again how teams complicate their lives without any necessity.
They dream up features “urgently” required by their imaginary customers and then start a death march to launch them at an arbitrary, self-invented date. Why is it so hard to simplify things and get going? Let’s have a look at possible reasons and ways to fight them. Excitement If you start something new, everything seems possible and you nearly burst by all the energy which that excitement gives you. 6 Bad Ways of Conveying Urgent Tasks (And How to Fight Them) Sometimes, due to the high urgency of issues, the owners of tasks are not patient enough to use your standardized way of filing a ticket in your issue tracking system.
Instead, they resort to various ways of conveying the new task to you or your team, disrupting your seamless ticket flow. Here’s a list of some of their favored weapons (from least devastating to most): Send an emailSend an Instant MessageCall you on SkypeCall you on your mobileWalk over to your deskMake your boss do one of the above In The Importance of Having a Seamless Ticket Flow, I explained why it’s a bad idea to break the standard flow of issues. DevOps. DevOps (a portmanteau of development and operations) is a software development method that stresses communication, collaboration and integration between software developers and information technology (IT) operations professionals.[1][2] DevOps is a response to the interdependence of software development and IT operations.
It aims to help an organization rapidly produce software products and services.[3][4][5][6][7] Companies with very frequent releases may require a DevOps awareness or orientation program. Flickr developed a DevOps approach to support a business requirement of ten deployments per day;[8] this daily deployment cycle would be much higher at organizations producing multi-focus or multi-function applications.