cloud camp

Today there was a Cloud Camp in Perth. It was basically a frank discussion among people involved with cloud technologies.

There were people from a lot of different fields and the discussions were all at a very high level. I gained a bit of insight into various viewpoints.

One of the discussions I found interesting was around proper investigation of business requirements BEFORE making any significant change, like moving to ‘the cloud’. This seems obvious to me, however at least in my (abeit limited) experience, it doesn’t happen nearly as often as it should.

If memory serves, this topic was kicked off by a presentation by Red Ember Solutions

One of the questions that came up around this issues was, “how do I determine if its worth going to the effort and expense of an assessment (including requirements), before doing the assessment”. Thats a question that strikes a particular chord with me, as I’m currently involved (at various levels) with a few large-scale cloud infrastructure projects, that frequently want a justification before even beginning the project.

This doesn’t seem like too much to ask, however it is a bit of a ‘chicken and egg’ situation. My only suggestion is not to get too caught up in detail in the justification, make broad (and documented!) assumptions and move on. Being too detailed at this stage might well backfire and place less importance on the assessment phase, or make it not happen at all. I’ve seen it happen.

As always, just my 2cents. :)

Leave a Reply

The opinions expressed on this site are my own and not necessarily those of my employer.

All code, documentation etc is my own work and is licensed under Creative Commons and you are free to use it, at your own risk.

I assume no liability for code posted here, use it at your own risk and always sanity-check it in your environment.