Archive

Posts Tagged ‘Strategy’

How to build a roadmap in 7 steps

January 2nd, 2015 Comments off
Reading Time: 7 minutes

RoadMapMoving Information Technology (IT) into the sphere of “the business” is still a challenge in a lot of organisations. How to move up requires that the IT/ICT teams demonstrate value (showing how you can support the business achieve its goals) to more senior executives within the business, where to start is always a hard question. Whilst there are many ways to approach this, the roadmap is one of the simplest ways of getting started.

 

Over the years I’ve noticed that there is little consistency in the generation and development of roadmaps; Infrastructure, Application or even Business structure. This can be for various reasons including:

 

  • There isn’t visibility of the full picture, but you have to show some degree of thought
  • Enterprise Architects are now really Technology Architects so the views are skewed towards a technology, conversely there are consultants posing as Enterprise Architects who have nothing more than an MBA and no experience or exposure
  • Businesses don’t truly understand what they are doing with ICT or why they need to be planned and not reactive
  • It’s a contract deliverable and come hell or high-water you’ll deliver something.
  • Newly minted TOGAF, SABSA or other practitioners attack this discipline with too much vigour that they get quickly shutdown by the business.

 

Regardless of the reason, it is important to be able to show those needing to invest in ICT services, what they are going to invest in and why they are going to invest. I’ve found that providing clear traceability between business objectives, ICT strategies (where available) and the roadmap help you as the architect understand WHY better which helps when presenting up higher the the organisation; communicating in the business’ terms and not techno-speak.

It can also help the CIO/Director of ICT/etc. understand how their organisation is supporting the wider business and its initiatives.

Remember a roadmap is generally for inside an ICT organisation. it requires distilling into bite-sized chunks for management to absorb

So let’s get to it. Building a roadmap can be broken into 7 stages

  1. Confirm the business’ priorities
  2. Current State
  3. Define End state
  4. Identify the measures
  5. Gap analysis!
  6. Sequence the events
  7. Publish the end goal

Read more…

Stealing your data while you watch

December 20th, 2014 Comments off
Reading Time: 4 minutes

medium_4612834833 In IT and IT Security there is a constant complaint about the risks of shadow IT, and the adoption of consumer collaboration and sharing tools. Over the last couple of years we also saw the emergence of novel exfiltration techniques including the persistent ultrasonic technique, where the infected devices  communicates with other compromised hosts via high frequency; or the Twitter based technique, where malware sends out data 140 characters at a time for anyone to read;  and the more recent Video technique, encrypting data in video files and putting corporate secrets onto video sites or later retrieval.

Read more…

Ethics in Technology

November 3rd, 2014 Comments off
Reading Time: 2 minutes

Warning, today is a bit of a rant. I had an email and chat exchange with a friend that wasn’t treated well recently and felt compelled to ramble.

Ethics is extremely important in business as it is the foundation of relationships. Ethics in the IT business is especially important as members of the Technology team(s) are responsible for representing IT to the wider business. Through the relationships IT builds with the business it is able to better understand the needs of the business itself and can develop real value through the strategic use of IT, using the collective smarts (IP) of the team. The Technology teams inside an organisation supports the business’ strategy, balances the wider strategic needs of the organisation and business units with the explicit needs of IT and IT strategies. Unethical behaviour can destroy this.

Let me be clear, when I say unethical I mean behaviour that isn’t:

  • Honest;
  • Courteous;
  • Done with Integrity;
  • Performed Efficiently; and
  • Respectful of Property

Our individual actions ultimately reflect our ethical beliefs.When we are in a position of authority these also shape the way those around us operate.

The consequences of unethical behaviour in our IT teams is that it breaks the relationships, both internal to the team and the external ones to the organisation. This can cause team-members to become disconnected and jaded, holding back the IP that could make a difference between completing that aggressive project on time, creating that innovative new product or demoralise the wider team around them. The greater flow on affect is that IT will become disconnected from the business (again) and relegating it to that group that just cost a lot of money and doesn’t deliver anything.

It is easy to be dismissive in the heat of corporate action, but let’s face it, for the most part corporate IT is not life and death. Take the extra minute to think about the repercussions of the decisions you make and the actions you take, it may mean the ultimate success or failure for the perception of IT in the business.

/rant.

OK I think I’m prepared for that Ethics section in today’s exam!