If you are looking at a significant use of cloud computing, have you considered what this might mean for your network? Corporate networks are an often overlooked factor when thinking about cloud computing. The problem is that cloud computing increases the criticality of your network, because if your network isn’t available then your cloud services aren’t either.
We are often called on to justify the particular option or path we are taking. We often have good articulate reasons for choosing this option over that one, for why we are taking this particular path, but we are rarely asked to justify why we are doing anything at all. But surely, this is the more important question? Why are we doing something at all? Why are we doing something rather than nothing?
I recently had a discussion with a colleague about what the real purpose of architecture documentation is. The simple answer of “documenting the architecture” seems unsatisfactory to me – “what is the point in that?” I think. My response to him was that architecture documents are for recording (and communicating) architectural decisions.
This is basically the question that many project managers ask me when we have a discussion about adhering to governance. They want to know what value their project gets from adhering to governance processes, from generating artefacts for governance gates. The short answer is “none – governance is not something we do for you!”
Here’s an idea to help your projects go smoothly. Start each project off making sure that the team understands the business context it is operating in by performing a SWOT analysis.
Something about the typical language of enterprise architecture is starting to bug me. The overuse of the word “alignment”. When people are asked to describe what enterprise architecture is all about, they often answer with the phrase “it’s about the alignment of IT with business strategy”. But is that enough? Should it be something more?
This is the sixteenth post in my series on BYOD. In my last post on the subject I discussed a range of technologies that can be used to solve issues raised by BYOD. Here I’d like to give my broad recommendations around which of those technologies are most likely to solve the kinds of problems that are typically found in organisations that are looking to embrace BYOD.
Does your architecture pass the “So What” test? Can you demonstrate the specific value that a particular architectural deliverable or activity will add? If not, why are you even bothering? In this case, as with justice, your activity must not just add value, it must be seen to add value.
In case you haven’t heard Microsoft is ending support for Windows XP and Office 2003 in April of 2014. What this means is that Microsoft will no longer patch security vulnerabilities discovered in XP or Office 2003, and therefore there will be security holes discovered that can be exploited by hackers which will never be fixed. My personal opinion is that in practical terms within a few months users of XP will be wide open to exploits by hackers. Potentially, they will be able to steal your data or take control of your PC and there will be nothing you will be able to do about it! For most organisations this represents an unacceptable level of risk. If you haven’t already started your move off Windows XP, you should – immediately!