Tagged: Forget Toggle Comment Threads | Keyboard Shortcuts

  • admin 9:53 am on November 14, 2015 Permalink
    Tags: , Forget, , , , These, ValueAdding   

    Investing in New Technology? Don’t Forget These 5 Value-Adding Steps 

    By Data and Analytics Staff

    IT departments are always on the lookout for the latest and greatest technological advance that will change the way their company works. But striking a balance between IT’s desire to implement a new technology, and the impact of said technology on the company’s bottom line, often can be tricky. For organizations in the processes of determining whether or not big data is right for them, comes the important task of identifying value.

    This is why the Teradata Business Value Services team offered some helpful insights to attendees of the annual Teradata Partners Conference last month. Determining the business value of a certain technological undertaking can be a hefty load. During the process, it’s important to consider current environments, processes, and pain points to help nail down exactly what the new technology should be and, more importantly, what it should be achieving. It’s important for organizations to project what could be achieved in the future, and remain focused on identifying those potential future benefits.

    Data Points, Teradata, Investing in new tech ID bus value

    There are certain steps that can be taken to ensure that ROI is successfully realized and captured, and that the whole organization is driven to create business value:

    1. Prepare and Plan. While it may seem like an obvious first step, too often companies attempt to dive head-first into a new business technology, without proper preparation. In this stage, organizations should take a step back to get a better understanding of what’s going on within the business, collecting important data to further prove the need for a new technology project or improvement. This could be financial data of the company to-date or business data that will give IT leaders a better sense of what shape the company is in and where further technology investment can take it.
    2.  Evaluate and Recommend. Once this pertinent data is compiled, take the time to digest all of the information, make sure it’s understood, and double-check that all the necessary information has been collected in order to put together a solid business case, including metrics, for the project to come. Backing new IT projects with fact-based recommendations surrounding business needs and the current environment can help to validate the business value to the C-suite.
    3.  Educate the Business. It’s important for executives and decision makers to be educated on a new initiative so that IT can gain a better understanding of whether or not an idea under consideration makes financial sense for the company as a whole. The marriage of IT to business and finance departments is important, and educating the masses is crucial. IT should be listening to the needs of the businesses from the very start to deliver value to the organization, not just new technology.
    4.  Develop a Roadmap. Various business improvement opportunities can be achieved by understanding, articulating and quantifying the impacts of a new project. Developing a project roadmap makes it easy to prioritize opportunities and optimize results.
    5.  Refine and Confirm. Once a new program, project or technology has been implemented, people often take a back seat and let it run its course. But when an organization is making such a critical investment it’s crucial to track these processes and make sure they’re reaping the planned value. Teams should start with a solid foundation of metrics upon implementation to make regular analysis a smooth process, and use those metrics to adjust if goals aren’t being met.

    By taking these steps, IT teams can better understand the long-term value of a new technology advancement and work to convey that message to the C-suite and the organization overall. By taking an inclusive approach to a technology investment, IT teams are able to display business value, upfront, and make effective technology use a reality for their organizations.

    The post Investing in New Technology? Don’t Forget These 5 Value-Adding Steps appeared first on Data Points.

    Teradata Blogs Feed

     
  • admin 9:53 am on September 28, 2015 Permalink
    Tags: , , Forget,   

    Forget End State Architecture – Aim for Endless State 

    Often working and discussing amongst peers and customers I hear the term “end state architecture”. It sounds like some magical nirvana where we all work hard to deliver and configure a solution that will meet all of the expectations (and maybe solve world hunger at the same time) at a point in time in the future. The sales division of vendors is partly responsible for this approach because the story usually starts off by defining the current problem as this mass of integration points/issues as depicted below:

    To an end state where life seems so much easier and simple.

    If only it was so easy……

    So in architecture should we aim for an “end state”? Shouldn’t we be aiming for an architecture that will support the business objectives at that particular point in time in the future? Whilst at the same time ensuring our architecture is flexible and adaptable if those business priorities change during the course of the project. Thus the endless state architecture concept.

    The last point above is important because too often we see an end state set in stone and all of a sudden the business priorities change and the cost to shift away from the end state is prohibitive and thus IT pushes on to deliver a solution that all of a sudden doesn’t support the business and the project becomes an expensive white elephant.

    The speed and rapidly changing nature of the analytics industry dictates that we shouldn’t have an end-state architecture but rather an architecture that evolves and adapts as the business changes. In essence there is never an end-state. A bit like a chameleon having to change it’s colour based on the environment it is in.

    Whether we like it or not, that’s the present day operating environment that we have to design architectures in. If you go down to a lower level and apply a traditional architecture approach to Hadoop and Big Data architectures, you’ll forever be chasing your own tail. Hadoop architectures, products and functionality are released at such a rapid rate that for me it is basically a full time job keeping on top of it all. So what’s the point of having an end state architecture when we’ll never reach it? It’s a major contributing factor as to why 68% of IT projects fail.

    Michael Nygard delivered a great speech on the concept of an endless- state architecture. The concept outlined here is that we should create architecture that is specifically optimized for change, with principles about where to place certain decisions and how to adapt over time. Optimized for change is important and as much as possible an architecture should be modular in it’s design. Each component should be best of breed, integrate together yet be swapped in or out over time to adjust to the changing business landscape. Another term applied to this concept is the sentinent enterprise.

    Lastly an evolving architecture also relies on the human element to succeed. The continuity of a cohesive team to deliver the architecture, the tenure of a CIO to ensure it is supported at the executive level and of course the developers and project managers at the coal-face to deliver the functionality to meet the requirements.

    Key tenants of an endless state architecture:

    • Use of open source technologies
    • Enterprise integration standards such as SOAP and Rest Services
    • Commodity hardware that is swappable
    • Skillsets within the team that are relevant and adaptable

    An eye on the changing priorities of the business.

    Ben Davis is a Senior Architect for Teradata Australia based in Canberra. With 18 years of experience in consulting, sales and technical data management roles, he has worked with some of the largest Australian organisations in developing comprehensive data management strategies. He holds a Degree in Law, A post graduate Masters in Business and Technology and is currently finishing his PhD in Information Technology with a thesis in executing large scale algorithms within cloud environments.

    The post Forget End State Architecture – Aim for Endless State appeared first on International Blog.

    Teradata Blogs Feed

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel