Cyber Security Predictions for 2017

2016 was a big year in the annals of Cyber Security, and 2017 promises to eclipse it.

Creating an Enterprise Data Strategy

An introduction to the process of developing comprehensive strategies for enterprise data manangement and exploitation.

A Framework for Evolutionary Artificial Thought

Let’s start at the beginning – what does this or any such “Framework” buy us?

The Innovation Dilemma

What things actually promote or discourage innovation? We'll examine a few in this post...

Digitial Transformation, Defined

Digitial Transformation is a hot topic in IT and big money maker for consultants - but what does it really mean?.

Showing posts with label Agile. Show all posts
Showing posts with label Agile. Show all posts

Tuesday, August 5, 2014

What is Digital Transformation?

It sounds a bit misleading perhaps - maybe one gets the impression that this is something akin to rendering special effects for movies. In mainstream IT however, Digital Transformation has come to mean something quite different.

The shorthand definition for it is this; "the coordinated integration of all customer-facing digital capabilities." This includes mobile, web and social media. There is perhaps an implied level of underlying integration supporting of all it, but that isn't always required - at least not at first anyway.

We use the word "customer" here a bit loosely, as Customer can refer to any users or members of a certain organization. So, a government entity might consider citizens as customers and the military could consider its rank and file 'customers' in this sense also. Digital Transformation can occur in just about any type of organization specifically because the set of technologies involved is common across industries.

Ten years ago a 'Digital Transformation' would have likely been referred to as a "Portal Strategy." At the time, it was thought that the portal metaphor (and associated software products) would suffice to meet all customer-facing needs. A typical portal might include the following elements in 2005:

  • Extranet
  • Intranet
  • Collaboration tools
  • Content Management tools

What happened since then? Well, at least two and possibly three revolutions in technologies with more on the cusp; the key revolutions include:

  • Mobile - (not laptops of course, but the smartphone and mobile)
  • Social Media - some re-branding of collaborative capabilities merged onto smartphones as well
  • Cloud Computing - re-branding of visualization - and importantly opening that up to customer facing apps (web and mobile).
  • with Big Data coming on strong (although to be honest, most places still don't know how to use it so it's an outlyer with respect to customer facing technology).

On the backend of course are all the systems that actually make the organization go - but for the customer this is like the engine within the chassis. Most customers don't care what's under the hood until or unless it fails to perform.

Digital Transformation is a lot like enterprise integration but on the customer facing side of things. It is the alignment, coordination and update in tandem of the core mission apps and interfaces. And it can potentially include the Web of Things as well. So for example, if you have a grocery store then perhaps there are kiosks inside and gas pumps outside and nifty new cooler video displays etc. All of that technology is customer-facing so for a true transformation it all must be managed within a shared context.  The transformation has one goal - to go from a heterogeneous mix of random technologies to a holistic solution designed to facilitate strategic goals.

So, how does an organization undergo a Digital Transformation? We will look at this in more detail in one of our upcoming posts.


Some organizations (like larger retailers) face dual Digital Transformations; in so much as they must serve both traditional customers and the needs of many thousands of employees (with separate capabilities) such as in the example above targeted to employees...


Copyright 2014, Stephen Lahanas


#Semantech
#StephenLahanas
#TechnovationTalks

Sunday, September 22, 2013

Top 5 Reasons IT Projects Fail

Last Fall, I wrote an article for Dice.com about the top 5 reasons ERP projects fail: that was in response to news of a specific project shutdown. However, the topic as to why IT projects in general seem to be so failure prone is worth exploring as well.

As far as hard statistics as to how many IT projects succeed or fail; it's difficult to get a clear picture. Part of the reason this is the case is that often when a project is clearly going to fail it gets "redefined" rather than cancelled. That redefinition represents a re-baselining effort that dramatically scales back expectations with the hopes that the reduced scope can be met. Sometimes that works, other times re-baselined projects are later cancelled anyway. If our measure for success was the original set of expectations associated with a project, the likely rate of IT failure would be extremely high - perhaps in excess of 50% of all IT projects.

In IT, building bridges to nowhere is fairly common, but no less costly...
This is a rather incredible statement of course, especially if we compare IT with most other types of projects across industries. What exactly does this level of failure really indicate though? It could represent any or all of the following factors:

  • That the expectations of the stakeholders were out of touch with the reality of what their IT provider organizations could manage.
  • The level of complexity was not properly gauged or managed.
  • IT is changing so fast now that a project defined last year might require major changes if it is still 'in motion' this year. 
  • The project was driven more by the perception of some need than the reality of a need. This of course refers to all those projects that are spun up in response to industry hype without a clear set of requirements. 
  • The technology assumptions (driven from the expectations) were hastily made and then never challenged later (or perhaps more appropriately - no challenge was permitted). 

While these five factors might be taken as the reasons that so many IT projects fail, they are in fact only the backdrop for the real reasons. Our focus needs to be directed to the fifth bullet point above - assumptions. Thus the five reasons we're focusing on here are related to why failure occurs after a project has been launched.

Even if a project wasn't launched under the best of circumstances, it still has a chance of succeeding if it is flexible enough. But what makes a project flexible? Is it the application of some Agile methodology or some other unique lifecycle management approach? Maybe not. Let's look at the real top five reasons that IT projects fail once they've begun:

  1. An inability to examine or challenge assumptions.
  2. A "silo" mentality.
  3. The inability to compromise.
  4. Technology-centric rather than capability centric perspective.
  5. Poor role definition and lack of project dynamics.

Let's look at these a little closer now...

1 - As noted previously, the inability or unwillingness to challenge assumptions is a huge issue on many projects. This is a problem precisely because of the manner that many projects get spun up (the factors listed previously). This is a little different than the traditional dialog on 'requirements' that's heard when explaining Agile methodology because in that conversation the focus is on the detailed design. Here the focus is on the big picture assumptions which in truth are much harder to face or deal with.  In any project, there are perhaps less than 10 issues which will determine the success or failure of the effort. You may have another 10,000 detailed issues or requirements in a backlog and each of those may be dealt with successfully yet still not save the project from failure if the core issues aren't addressed. Those core 10 or so issues are almost always associated with the initial assumptions connected to the project.

Those types of issues include things like the original intent of the solution, preliminary technology choices and solution architecture decisions as well as organizational approaches. There is no one correct mix of all these types decisions that ensures a successful project and that's precisely why those decisions should be reexamined on a regular basis. In other words, we shouldn't view the first hectic weeks or months of a larger initiative as infallible exercises in perfect thought or planning, but for some reason, many people do.

2 - The Silo Mentality. This refers to projects that become over-compartmentalized; where each sub-unit views itself more or less divorced or separate from every other. While everyone on a project needs to understand their roles (point 5) by the same token they must also all share responsibility for the outcome. There is nothing sadder and less justified than internal finger-pointing when failure occurs. This is a problem that is easily corrected with the right leadership and project structure. Whenever you begin hearing various players within a large project stating that issues relating to them are someone else's concern or responsibility then you know the project has developed this problem.

3 - The Inability to Compromise - We talked about this in a previous post from the perspective of team leadership; here compromise has an even broader context. Compromise here represents compromise between teams, by leaders - as well as compromise on large, tough issues. Lack of compromise is one of the chief symptoms of an 'inflexible' project. People will always have excuses and cite deadlines yet invariably where compromise fails to occur, deadlines are shot anyway and often the entire project ends up being cancelled.

4 - Technology-Centric Projects - This may sound funny coming from an IT geek however it is nonetheless valid. Let's look at Big Data as an example. What exactly does that new technology category mean to a business that wishes to jump onto the hype bandwagon? Does it imply faster data systems, better storage management or is it tied to specific Use Cases associated with that organization? If the expectations end up looking just like a Gartner article on who's doing what instead of Use Cases that illustrate how it can be exploited in your organization then you might say you've got a technology-centric project. The fact that you think everyone else is doing something shouldn't drive your decisions. If you've been stuck with a hype driven project then use the initial period to re-tune it to ensure that its aligned to your business. If you find that it's not then have the courage to reverse course if necessary (the earlier, the better - you can always come back to it later).

5 - Poor Role Definition and Project Dynamics - How you build the project is usually just as important as the underlying assumptions behind it. Understanding roles and how those roles and groups ought to work with one another is important. For example, an architect and a tech lead are two very different roles - one owns the technology the other designs the solution (completely different perspectives). Yet many organizations regularly confuse those two roles. Also, there's often not clarity in regards to who has oversight or leadership across groups. This last point relates 'project dynamics.' A flexible project still needs leadership - but leaders who act as facilitators rather than strict commanders. And the folks they lead need to be able to form working groups that have clear purposes and escalation paths to ensure corrective action can occur when needed (and not just on the little issues).

There are of course other factors involved in the failure of complex IT projects, but a large chunk of what tends to happen can be mapped to the issues raised in this article. In a future post, we will look at some of the warning signs associated with a project 'at risk."


Copyright 2013, Stephen Lahanas

Wednesday, May 22, 2013

How to Set Trends


IT is a very trendy industry. You might say we’re more or less slaves to fashion. The priorities which are set in company boardrooms and technology departments are quite driven by the set of 'must have' capability being hyped at any given time. We’ll forgo discussion as to whether this is a good thing or not for now and focus instead on the act of setting a trend rather than merely following one.

First of all, why would someone want to be a trendsetter in IT; well here are a few potential motivations:

  1. Because inventing something is fun, exciting or at the very least represents a break from the typical routine. 
  2. Because identifying a trend can result in benefits to the trendsetter. I’ll emphasize “can” here because living on the cutting edge often results in some blood loss. There are risks to being new, different or the first one out of the gate.
  3. Because creating your hype is and always has been good business. Not everyone can pull it off, but many of the most successful technology companies were built (at least initially) on hype.

Now, it may sound like I’m trivializing the topic a bit or perhaps implying that there is little substance behind most trends – but I’m not really. There can be a marriage behind trend-setting and true innovation if that’s the way you wish to pursue it. Obviously, some trends involve a much higher investment threshold than others. For example, inventing the next commercial quantum computing platform is going to require a lot of capital up front to pull off. However, there are lot’s opportunities hidden with the mass of existing technologies that remain unexploited as well. For most of us, the easiest path towards that exploitation is through invention of new practices.

Who defines the road ahead?
So what does that mean exactly? Practice, any practice, is the day to day approach that a professional takes to do their job. In Medicine, practice is the application of diagnostic and prognostic algorithms (rulesets and techniques) based upon understanding of a much wider body of knowledge. Individual practice in Medicine can influence the holistic practice of medicine across an entire society (or the world) through the publication of these new techniques and insights. Those new techniques if grouped together can also be viewed as trends. Some examples from Medicine of recent trends include:

  • Introduction of Electronic Healthcare Records 
  • Reductions in the amount and frequency of antibiotics being prescribed
  • Exploitation of genetic markers to predict, diagnose and treat a wide array of illnesses

Notice that in the above examples, two of the three trends listed were in fact technology-focused. This is an important consideration when thinking about becoming a trendsetter – nearly every industry now depends on IT to provide a significant amount of its innovation. This means that IT professionals have the opportunity to set trends not only for their own industry but every other one as well. This is exciting and extremely cool if you think about it. For the first time in perhaps forever – folks who weren't trained in specialized fields are helping to redefine those fields because of the technology being applied. It’s not uncommon for an IT consultant to move across industries from one project to the next – in each one learning the business enough to determine how best emerging technology might improve it.

Maybe the best way to describe how to become a trendsetter is through an example – so I’ll draw upon one from my own experience. In 2007, I was consulting for a firm that specialized in Business Intelligence and Data Warehousing. They asked me to determine if some of their solution offerings might be cobbled together into some sort of unified practice approach. I had worked with them before and seen their solution in action and had worked in that industry space quite a lot as well. So here’s what I did:

  1. I identified all of their strengths and characterized them in depth.
  2. I assessed the current practice approaches in industry (circa 2007) for BI and DW and identified a list of gaps.
  3. I mapped the identified strengths of the company against the industry gaps and as I suspected there were several key areas of alignment. In other words, there were things that the company was doing that wasn't commonplace in industry yet – but really needed. 
  4. I took that and expanded upon it; identifying a theme for a practice approach as well as a methodology and also identified areas where some technology gaps still existed (even within the new model). 
  5. This then led to a standard solutions architecture and detailed process approach based upon the theme and high level methodology. 
  6. I actualized this within the company buy presenting the findings and recommendations – many of which were focused on how to blend the new practice approach within the current business model.
  7. I then launched an outreach effort – through existing customers and social media. 

The practice I created for them was coined “Agile BI.” At the time, the reception was mixed. Very few in the industry were viewing Business Intelligence or Data Warehousing as something that could be considered Agile. This was before the explosion of Big Data and NoSQL solutions. The main premise I was promoting though is very close to what the industry is defining as Agile BI now:

  • That BI projects can be time-boxed into clearly defined increments (you don’t have to use Scrum per se). The key is that some capability is delivered within each increment. 
  • The approach was less product-focused and more capability focused. In other words, in this practice a wider variety of tools and capabilities were considered mainly because of the recognition that most environments have a wide variety of data needs / solutions.  
  • That BI and the underlying data structures needed to be engineered for performance from day 1.
  • That BI and DW were not IT only efforts but required very close collaboration at all stages with key business stakeholders. 
  • That new modeling or architecture techniques were needed (that extended beyond 3NF ERD) to help unify management of diverse data resources. 

I recall presenting this all in Chicago in 2007 at an industry conference and receiving a lot of blank stares. This of course is where the risk comes in; it takes years and some serious marketing to go from a kernel approach to widespread industry adoption. In this particular example – that actually has occurred - ( see The TDWI Agile BI Portal ). The company I introduced the practice to did not have the resources to wholeheartedly pursue the approach and stuck to their old business model and I moved on, but not before posting several presentations online and creating a blog that may have helped contribute to the general mindshare behind the industry premise. Granted – it was an obvious and logical progression that would have likely occurred anyway - but my contributions proved to be a worthwhile exercise none-the-less.  

One of the side benefits though of helping to shape industry-wide expectations of how technology practice ought to look like is that eventually you find yourself in projects that have adopted the trend you helped to set – which in itself is fairly satisfying – especially if you really did help to promote a better way of getting things done instead of just generating more hype.

Tuesday, November 27, 2012

Exploring Governance Process - part 1


Today's post presents a Governance Case Study; in this case the introduction of SOA Governance within an enterprise environment. 

The larger context for SOA Governance 

Process Context
The process depicted in the figure above represents one of several related processes. We've referred to this process as the SOA Service Approval and Governance process. This is used to help document to provide oversight for SOA service development and management. The other processes that this will become integrated to will include a modified project and portfolio management process, an engineering design process and an application lifecycle management process. Each of those processes will have hooks into and out of the governance process. Both the governance and design-related processes will definitely involve collaborative small group involvement (and that involvement will include collaboration between both technical and business representatives). The eventual goal would be to further integrate the related processes and to provide automation for all of them. 

Process Overview
The SOA Approval and Governance Process is at its heart both a requirements management process as well as a configuration control process. We've also included some elements of design review within the process in order to provide  the most flexible approach and least number of processes possible. The primary objective of this process is to help provide a documentation baseline of all potential service opportunities within the enterprise. The primary role within the process is that of the SARB - this could be translated to either Services Architecture Review Board or Software Architecture Review Board. At first the focus will primarily be directed to SOA services but eventually the board can extend governance across all business logic . The other roles presented in this process include:

  • Stakeholder - stakeholders represent business analysts, management and possibly even customers.
  • Developer - developer represents any technical resource that would be involved in either constructing a service or utilizing a service as a system-level consumer. Developers and stakeholders are the primary participants in both design process activities as well as design review activities within the governance process.
  • CM - CM stands for configuration management and in this context would represent one person designated as the point of contact and responsible for documenting specific configuration information within the SOA Center of Excellence (COE) wiki.
  • Manager - this is self-explanatory and of course the management role is responsible for integration of governance with project portfolio management.
Prerequisites
There are several prerequisites for the governance process; these include a Center of Excellence wiki, a preliminary capability inventory, templates for the process deliverables and extended guidelines splitting the function of this process in the SARB which would be posted on the wiki.

Goals
There are several critical goals associated with this process:
  1. Standardization of requirements capture, documentation and management.
  2. Standardization of SOA services design through enforcement and oversight.
  3. The ability to reconcile requirements and designs across the retail enterprise.
Service Level Versus Enterprise Engineering
One of the key concepts associated with this particular process is the separation of design and design review as well as the separation of discrete design from enterprise design. All these considerations are managed through the first and second level analyses within the process. In other words, we are viewing the SOA designs at two different stages in the governance process – stage I allows us to ensure that the granular service is constructed according to agreed upon standards. Stage II allows us to ensure that services fit within the enterprise in the most efficient way possible.

part 2 of the post will examine the process steps...


Copyright 2012  - Technovation Talks, Semantech Inc

Tuesday, October 16, 2012

Process Management & Process Fusion

Innovation and Technology both require comprehensive management - while there are quite a few paradigms out there already in regards to assuring best practices in program/project or portfolio management, none of them seems to have yet been able to wrap everything together seamlessly.  We are going to examine this problem space in the context of something we refer to as Program Lifecycle Management (PLM), which we will define in a future post. Today we're going to look at one part of the program management equation - Process.

Since the late 1990’s, there has been a certain level of obsessive focus on process management as a cure to the ills of program management. The basic premise is that any process paradigm is better than none at all. A variety of organizations including the Software Engineering Institute (SEI) and International Standards Organization (ISO) have produced massive quantities of literature on the subject along with a variety of process management guidelines design to help PMOs develop new processes or improve existing ones. More often than not however, larger organizations are finding that they have to deal with multiple types or levels of process management. For example, an organization may employ one or more SDLCs (Software Development Lifecycles) as well as a variety of solutions that manage workflows and business rules. The government considers Lifecycle Management so important that it is restructuring various DoD commands as "Lifecycle Management Centers."

One of the better known examples of an SDLC* is CMMI (Capability Maturity Model Integration). In the federal government, CMMI certification is often used as a criterion for awarding IT contracts (i.e. a contract must demonstrate that they have achieved a certain CMMI level of competence through a formal accredited certification). The problem that many have found when relying on process management and / or such certifications is that they are not accurate indicators of the organizations performance in specific project scenarios. So, while the fact that an organization does have some repeatable or mature processes it doesn’t necessarily prepare them to solve problems any better than before. This may sound counter-intuitive but it is has been proven by a rather larger backlash in the software industry where complex process paradigms are now being replaced by new ‘Agile’ methodologies.

The most basic premise of the Agile movement is that trying to over-regulate processes subverts the core goals of innovative and rapid development, thus the process becomes a bureaucracy or ideology more than a facilitation medium. PLM views process management as it views all other elements of PMO business – all are aspects within a larger whole and cannot be easily separated from one another without losing the relationships and contexts necessary to make the larger organism work. Product Lifecycle Management (which is what most people view as PLM today) is becoming especially dependent upon the successful implementation of Agile processes, given the ever-decreasing sales and product development lifecycles.

Process Fusion, defined
Process Fusion is a realization that processes or process families do not occur in exclusion to one another - all of the processes inherent within a typical PMO serve the same overall set of goals & objectives. This can be applied in the context of a single solution lifecycle or hundreds depending upon the scope of the organization involved. Process Fusion requires mapping of key elements of process with one another to ensure that all aspects of complex programs remain coordinated.

Process Fusion requires automation and a comprehensive management paradigm...

* some would contend that CMMI is used for more than software development, however it is still a software development lifecycle approach at its core. 


Copyright 2012, Semantech Inc. All rights Reserved