Guiding practices for dealing with IT Budget cuts


It is that time of the year when the CIOs, IT managers and financial analysts are trying to close on 2013 IT budgets while still managing the business needs and IT vendor costs. Add to this, the risk of unchartered Big Data and Analytics projects which promise a hidden treasure of $ but with an added rider of new investments.

Here are some guiding practices which you may want to consider while optimizing your project portfolio in 2013 and still carry on with your vision of Apache Hadoop projects.

1)      No short cuts please:

So while you may want to do away with frills and riders considering the cost cut, keep in mind that the standard compliance norms apply as much for your Hadoop and Big Data projects, as much they apply for other projects. So, you still have to ensure data security, access role segregation and purging policy as you apply for other data projects. Private Information (SPI/BPI) rules apply here as well. So, make sure, your Business Analyst and Architects have this ticked on your charts. Don’t leave it to the vendors or to the developers to ensure this all important compliance to avoid regulator and legal hassle later.

2)      Start with Basic(s):

Most of the Hadoop Distributions come with a Basic Edition which can be easily leveraged for your pilot projects. As you see business interest and technical team confidence in the project, you can order up the Enterprise stack. A decent level of due diligence is expected before you pick on a basic version as this is the distribution you may like to stick to when buying the Enterprise package.

3)      Cloud is here to stay:

As much as you would like to own your kingdom, it is a fact that basic upfront cost and lead time can be avoided with cloud provisioned hardware and software. The catch could be that small developer mistakes could lead to infinite processing loops and hundreds of $ added to your bill overnight. Make sure your set in system for monitoring cloud usage and wherever possible en-cash on free tiers and sign up incentives for your pilots.

4)      Agile is the way to go:

While business team have always harped on Agile for ages, your project portfolio may find it difficult to suddenly adopt a new delivery way. With volatile requirements and new discovery being a reality in Big Data, it is better to break projects into sprints or better use a Kanban Task based approach. Agile will also ensure you don’t invest in all resources up-front and refine your cost plan through the project prioritizing for each storyboard item.

5)      Invest in DevOps:

It is essential to ensure a smooth handshake between Dev and Ops.  While it is true that each portfolio has its own complexities, ensure that you enforce tools and standard operating procedures which make staging and deployment a cake walk. Better dev machines, automated code push and training could lead to a leap and bound improvement in productivity for the team resulting in a net lower cost of development.


The list could be bloated further to stress on partnerships, open source pilots and focus on revenue driven projects. However, as may have been evident to you each year, each CIO needs to reach a crucial mix of strategic moves along with cost cutting initiatives. Staff downsizing as has been stressed always should be last step even though it always catches the biggest attention due to it major cost pie percentage.  This list though written with Hadoop projects in mind may in fact hold true for other technology projects also.

Judicious use of each penny and still leveraging the benefit of cutting edge Hadoop and Big Data projects has to be exemplified as a CIO skill rather than a top driven mandate.  So, Mr.CIO, go out and make the most of the new tech – let the $ guys shrimp it with a shirk. 

------------------------------------------
Image source: rackspace.com, wikipedia.org