7 Signs you may need Application Release Automation

Posted on : 31-05-2013 | By : jo.rose | In : Innovation

Tags: , ,


With the increasing complexity of business environments and the quickening pace of application updates from both third parties and internal development, it is easy for an environments or operations teams to feel overwhelmed. The answer to this on-coming storm may be more release automation.

Here are 7 signs that you may need Application Release Automation:

  1. When releasing to an environment, you have a mess of remote desktop sessions open on your workstation and keep performing tasks on the wrong machine, when you don’t realise just in time that is.
  2. Someone leaves or goes on holiday and you discover, to your horror, that no-one knows the magic incantation needed to perform an obscure part of a release in a particular environment.
  3. The development team need access to your precious environment configurations in order to deliver you a releasable build from their agile/waterfall/tantric process.
  4. In your busy team, it is difficult to keep track over time of who is pushing out the most releases, who is having to pull back the most release that they should not have pushed out and who is playing Candy Crush.
  5. Whilst you are releasing to an environment, someone else starts up that environment causing chaos.
  6. You cause chaos by starting up an environment that someone else is releasing to.
  7. Your Mean Time to Pub (MTP) has increased dramatically and opportunities for this vitally important team building activity have dwindled with consequent effects on team cohesion.

If you recognise any of the above then you might want to think about automating your release processes. With pressure on teams to cope with an ever accelerating level of application change, now is the time to cut out the repeated pain of  taxing releases and put in place repeatable and recoverable processes.

Contributor: Andrew Porrer – Technical Director – Heathwest Systems (www.heathwest.com)

For a demo of our application release automation and management software or to talk about your requirments, please feel free to contact me at andrew.porrer@heathwest.com


Are you suffering from Complexity Drag?

Posted on : 24-06-2011 | By : jo.rose | In : Innovation

Tags: , , , , , , , , , ,


You have bought in the different software you need to run your business processes. Your system experts have pushed them to their limits as you have expanded.

To protect your critical production systems, you sensibly now have a series of environments (system integration testing, pre-prod, prod, etc.) which allow software upgrades to be fully tested and accepted before hitting your production environment.

However the various systems you now have are complicated with many inter-dependencies and your many environments have varied topologies. Even stopping or starting a small element or whole environment required specialist knowledge of the underlying systems.

When a required upgrade for some of your third party software comes in, it is a major event and the decision to deploy it through the environment chain is a big one. The system experts are now heavily involved throughout the deployment process. Even after their initial configuration work, their knowledge of the different configurations and dependencies within each environment is still required at each stage.

Instead of improving your systems or developing the next big thing, your system experts are now stuck in a constant cycle of pushing out software updates through the whole chain.

Stuck in a constant cycle

Stuck in a constant cycle

You are suffering from complexity drag. The effect when the greater complexity of your systems puts an increasing drag on future work. Further improvements or developments are slowed or stalled as your team is increasingly tied up with maintaining your current systems rather than driving forward necessary change.

Would it not be nice if your system experts could wrap up their systems knowledge and the necessary control along with a software update into a ball and then then just pass that ball up the chain with minimal further involvement?

Liberated experts and empowered users

Liberated experts and empowered users

The challenge is to move from the old model with its substantial knowledge silos to a more devolved system where knowledge is shared out and control delegated out to those that need it. This would empower gate-keeper users to maintain their own domains and push out any expert-approved updates themselves.

This can be achieved through use of a holistic system which encapsulates a repository of system knowledge including a store of all software and their updates. Each user can then receive customised views and control of the systems they require (as defined by the system experts), all of their actions can be centrally audited and the experts can be alerted in real-time to any problems.

Now that a lot of the support and maintenance work has been delegated to the relevant gate-keeper users and safe in the knowledge that they maintain close control of the entire system, the system experts are finally liberated to get on with those business-enhancing things that they were always meaning to do.

Contributor: Andrew Porrer – Technical Director – Heathwest Systems (www.heathwest.com)
For a demo of our application management software, please feel free to contact me at andrew.porrer@heathwest.com