Sunday , 17 December 2017
Home >> N >> NEWS >> Biggest mistakes in DevOps? Trying to do too much, not prioritising and environment over-ambitious targets

Biggest mistakes in DevOps? Trying to do too much, not prioritising and environment over-ambitious targets

Trying to do too much, too soon; a miss of prioritisation; and, environment extravagantly over-optimistic objectives and targets are only some of a mistakes that a consultant row during Computing’s DevOps Summit 2017 warned representatives to equivocate as they start their tour into DevOps.

Sandra Christie, use lead, analysis, during tradesman John Lewis, Ryan Bryers, arch record officer during e-payment association Worldline UK Ireland, Dale MacDonald, technical group lead during Thomson Reuters, and Tom Clark, conduct of commons height during broadcaster ITV, were responding to a doubt from a audience, ‘What’s a biggest mistake we have done in your tour to DevOps?’

“I attempted to do too most during once,” pronounced Clark. “I come from a growth and engineering background, so it’s roughly like we was given this large trainset on that we could do whatever we wanted and suddenly, we wanted to do everything…

“It didn’t unequivocally have an impact on a platform, since we had a good team, though we scarcely finished adult murdering myself over it.

“So we schooled a lot about prioritisation; must-haves, could-haves, should-haves; and what should come first.

“I have a large ‘Trello board’ of all my tasks. I’ve still got tasks on there that we came adult with 3 years ago, and we will get to them eventually, we keep revelation my boss, though we have got to prioritise – we shouldn’t try and do too most during once,” pronounced Clark.

McDonald during Thomson Reuters echoed Clark’s advice. “There haven’t been any sight smashes, though one of a things [we grappled with] in a early days was removing a change right. You’ve got all these new, imagination collection and gadgets. But one of a things that we unequivocally do need to magnitude is that we are indeed creation progress.”

So, suggested McDonald, it’s critical not only to digest a metrics for measuring progress, though to revisit them, three- or six-months down a line.

For Sandra Christie during John Lewis, it was her unrestrained for ‘objectives and pivotal results’ (OKRs), a horizon of defining and tracking objectives and their outcomes, “to try and concentration people, to grasp something, broach it, news it”.

The extreme series of OKRs both lifted expectations, on a one hand, though was demoralising, on a other hand, when too many of them weren’t met by a finish of a initial entertain underneath a new DevOps regime.

Bryers during Worldine, meanwhile, reported identical challenges. His IT group were using opposite a series of territories, and DevOps enabled it to step-up a speed with that it could deliver.

“We accelerated a DevOps/technical side faster than a business could keep up. We focused on a technical people, though it doesn’t work unless you’ve got a business plugged in… we don’t consider a business was as wakeful of a gait we were going to do this since they had been used to waterfall,” pronounced Bryers.

In other words, a business as a whole was used to a IT group relocating during most some-more totalled speeds and was taken by warn with a changes that DevOps entailed.

In essence, a recommendation from all 3 DevOps specialists could be boiled down to: don’t try to do too much, don’t overcome staff with daunting lists of objectives, prioritise objectively and pretty – and keep a business sensitive about DevOps and what it can (and can’t) deliver. 

Missed Computing’s DevOps Summit 2017? Stay present with a latest events during Computing’s dedicated events website

Further reading



  • <!–

  • Save this article

  • –>

==[ Click Here 1X ] [ Close ]==