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

How A Two Speed IT Structure Can Give Any Company The Edge...

It is a concept which has not gone mainstream yet but it has been gathering a following now for a few years.

I am talking about the concept of having a Slow Speed IT lane and a High Speed IT lane within the same organization.

Over the past years a lot of companies have embarked upon the digital transformation the market place (their customers) have demanded.

Digital transformation means a lot of different things to different people but most commonly the following IT challenges are understood to be part of the digital transformation package:


  • Online Systems (Web Applications)
  • Mobile Apps
  • Social Media 
The challenge is of course that things happen much faster on the web (the digital marketplace) than a lot of IT organizations are used to operate at. An IT department which has been supporting the legacy component of an organizations IT infrastructure does usually not need to move very fast. 

Legacy systems are ordinarily updated rather infrequently...so there is often times the mindset that being slow or deliberate is not a bad thing. There are still plenty of organizations which run enterprise software off an AS/400 and/or use Windows Vista.  

The issue of course is that this mindset is producing  a competitive disadvantage in the digital marketplace. 

Companies are falling behind in their Key Performance Indicators vis a vis their more aggressive, digitally savvy  peers. 

CIO's and Decision makers do realize that a huge part of addressing the shortcomings is to foster a culture which is more geared towards the Digital Marketplace. 

Needless to say...sometimes this is easier said than done.

Often times the very same decision makers which are tasked with spearheading the transformation are part of the culture where slow and deliberate is good.

So..the question of how to get ahead of the curve and transform into the Digital Marketplace deserves to be looked at. 

Perhaps the easiest and most practical solution is to outsource the Digital Transformation to outsourcing companies who have a lot of experience in that area while maintaining the existing In House IT infrastructure.

The effect is what is being called a Two Tier IT infrastructure. One lane is High Speed (Digital Transformation and Strategies) and the other lane, Slow Speed lane, deals with  Core Legacy and Maintenance. 

There are a few advantages operating a two tier IT infrastructure. Presumably the outsourcing provider is up to date on the latest technologies and even more important,  stays up to date...thus ensuring that the organization is able to outperform its competitors. 

The core IT team remains relatively unaffected and can concentrate on the issues they have proven to  be good at. 

In combination the two Speed Lanes can offer a successful blueprint how an organization can become more agile while maintaining the continuity needed to safeguard existing business processes.



 


Agile Project Management...Is Your Software Outsourcer / BPO Firm Using It ?....

One problem I frequently run into when discussing project guidelines for outsourced software development  is that most of the clients  are well familiar with Gantt charts or Waterfall charts. As such they prefer to look at the project guidelines, timelines and milestones based upon those  charts.

Nothing wrong with that of course...but the software development world has moved on and at least the better companies are now mostly using an Agile Software Development set of principles. The concept of an Agile environment is that it is much more "free flowing" and not bound to the traditional milestones and tightly defined guidelines which are being used in a Non-Agile environment.

The challenge is how to provide the accountability to the client  (the ones who pay the bill) while harvesting the advantages the Agile environment can deliver.

The Agile Development environment is based upon the following 12 principles:


  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the principal measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly



A practical problem of an Agile development is that there are really no Milestones the teams are working towards. As such there is no firm date which can be given so that the customer can review a an interim work product (milestone).   


A practical solution to this dilemma (and one we use internally) is to still provide Gantt charts but use an  Agile environment in House.  The process has to be of course managed properly...but if done well it is entirely  possible to utilize an Agile environment while also providing the form and accountability the client is looking for.  

A great article which goes into details as to the way an Agile Development Environment works can be found below.