Orchestrating application delivery (part 4)


Rehearsals done: time for the overture

In the past three parts we have looked at Why, What and How. In this last part we are going to look at Who and distil down to the essentials what Orchestrated Application Delivery is all about.

It doesn’t matter what your development processes look like, nor what methodology you’re following nor which platform you are developing for. Whatever your technology topology you will find that automation will significantly improve how you deliver applications.

Of course it is all about the process and not the tools. But it is easier to improve automated processes than it is to improve manual ones; to enforce compliance, to obtain metrics, manage exceptions, report on status … when automation is in place. So the rule of thumb here is “automate then optimize”. Of course this results in the automation of bad processes: but it is going to be easier to fix that bad process in the long run.

So who do we start with when we want to automate processes? The short answer is we start where the most pain is being experienced. Automation brings rapid relief to organizational issues. These are often within a silo and can be implemented quickly as all the decision making authority is in once command structure.

They are, equally often, between silos, managing the boundary conditions and hand-offs, and can be implemented here too with speed and efficiency though with more negotiation as two (or more) groups have the decision making authority. As a result it is essential to have senior management commitment to the automation project.

Whether it is managing the exchange of tasks and artifacts or just keeping track of status: the importance of automation cannot be understated. Incredible amounts of effort are expended in every IT department doing manually what could be done with automation. You need to find a champion on each team, in each silo, and involve them in every step of the automation process. Empower them to make the decisions for their team and make them responsible for communicating the project detail to their team members.

As we enter the deployment phase your virtual team needs to celebrate the victories and highlight the benefits that are being accrued from the automation. This meansregular comparison of the results with previous baselines of data so that the productivity gains can be shown and that the errors rates can be seen to be falling.

About Kevin

In the past year Kevin has spoken at 20 conferences and seminars on a range of leading IT topics, including methodologies, business analysis, quality assurance techniques, governance, open source issues, tool interoperability, release management, DevOps, Agile, ITIL, from the mainframe to distributed platforms to the web, mobile, wearable and embedded systems. He is a much sought after speaker, recognized around the world for his provocative and entertaining style. Kevin is a 40 year industry veteran, holder of three technology patents and today is VP of Worldwide Marketing and Chief Evangelist at leading Application Development and Deployment vendor Serena Software. In the past decade he has been crossing the globe and has met with over 4,000 people. At Serena he works closely with industry analysts, the press, customers, partners and employees to exchange ideas about industry direction and business issues. He was born and educated in the UK and lives and works in the Bay Area, California.
This entry was posted in Business and Technology and tagged , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s