Showing posts with label offshore software development. Show all posts
Showing posts with label offshore software development. Show all posts

Here Are The 8 Issues Every Company Needs To Consider When Outsourcing IT....

Whenever I sit down with a company and discuss an outsourcing structure it becomes quickly apparent that there are a few reasons and considerations  why companies want to pursue an outsourcing solution for IT related services.

Sometimes it really is only one or two reasons..and sometimes it is a combination of 5 o 6 reasons which in aggregation compels the company to consider an outsourcing provider.

What makes it interesting is that not every company has the same priorities...but they never the less share most of the same considerations. What is important for one company might be less significant as a reason to outsource for another.

The following reasons / considerations are usually part of the decision making process to decide upon executing an outsourcing strategy:



Consideration # 1 Expenses
Always one of the main reasons (if not the main one).  CIOs are expected to cut costs while maintaining service levels. CIO's have to keep their existing, classic IT  landscape running (slow tier) while at the same time developing the fast tier (Social Media, Cloud and SaaS). All of that has to happen while KPI's are maintained and preferably improved. New technology needs have to be addressed and incorporated all the while CEO's expect the value being added at a lower price point, Outsourcing can address all of the above at a lower price point.

Consideration # 2  Forming a Partnership
Contractual obligations are one thing in IT outsourcing – trust is another. Before corporations  outsource IT, decision-makers contemplate if their potential outsourcing partner is trustworthy. Some of the questions which needs to be addressed are: Has the outsourcer related industry experience ?  Does the offered service seem reliable and at the needed quality level ? Is the outsourcer up to deal with the rapidly changing technology environment ?  Does he meet the operational and legal requirements for the security of the entrusted Intellectual Property?  Are the existing customers happy ?

Consideration # 3 Expertise
The Cloud and Web 3.0  is forcing companies to change  existing business processes and/or establish new ones. Specific  departments have requirements and expect the  IT department  to implement them as quickly as possible. Additionally the  IT organization is now looked upon as a revenue creator...it has to innovate and offer new services itself in an attempt to outperform competitors in the digital marketplace. An outsourcing provider needs to be aware and proficient in strategies incorporating those requirements.

Consideration # 4 Cyber Security
Cyber Security if front and center now for IT executives. Data security, data  privacy and  protection are key drivers of any decision making process.  Cyber attacks are getting progressively more sophisticated and IT departments are caught in an arms race they try to fight with limited resources. A top level outsourcer with significant experience in cyber security can alleviate a lot of the pain points for companies trying to harden their network and infrastructure.

Consideration # 5 Customer Focus
According to IDG, onshoring is the most popular sourcing strategy.  The advantages are  that the service provider can be contacted quickly and directly. Often times onshoring delivers its services through a combination of onshore, nearshore and offshore activities. A heavy emphasis on customer service without compromising service quality is what corporations are looking for. Of course, the price point at which the desired level of service is delivered is always key and center for corporations.

Consideration # 6 Innovation
Companies feel the constant need to innovate. Innovation is what keeps them ahead of the competition. The problem is how to innovate without spending human resources (and capital) in a non productive manner. A good outsourcing partner might very well be solution to the innovation dilemma. The outsourcing provider will stay up to date on the latest technologies without the company having to needlessly spend human capital. (and its associated costs)

Consideration # 7 Scarcity of Talent
A recent Bullhorn (2016) study showed that 77 % of respondents in the technology filed reported a skill shortage they have trouble filling in the labor market. Besides the scarcity of talent the price and premium to be paid to address the skill shortage are the main problems identified. Corporations which employ a sourcing strategy involving outsourcing are able to fill the skill gap while maintaining a lid on personnel expenses.


Consideration # 8 Quality of Final Work Product
Perhaps the biggest challenge IT departments have been facing over the past 10 years is the need to change. Digital Services, Cloud and SaaS as well as Social Media have forced companies to innovate at a faster pace then any other time during the past 30 years. IOT and AI (Web 3.0) are the next challenge which need to be addressed by a lot or corporations. IT departments face tremendous pressures to get it right on the first try. As such the pressure is on for Outsourcing providers. The quality of the work product has to be right. There is not a lot of time available for trial and error releases which are fixed post release.


Of course, the above list is not all inclusive. There might be other consideration an individual company might contemplate. However, in my experience the list provided above is rather comprehensive.

Corporations which start the process can use the 8 points listed above as a check mark list to see where they are standing and what is important to them.









Onshore, Nearshore or Offshore Software Development...here are some pros and cons

The day has come where you decide to outsource a software development project. There might be multiple reasons why but you now face the task of how to do it and get it done.

For someone who has never outsourced software development this might seem like a rather daunting task. After all...how do you get from idea to conclusion without having major hiccups on the way.

Business is all about proper execution of strategy...and you should treat your outsourcing approach the same way.

One of the first decisions has to be the geograpic which decision as to what type of outsourcing you want to pursue. There are 3 different categories of outsourcing available to you. Each comes with positives and negatives associated with their relative geographic area.



The table below provides some insight into some of the considerations you may want to entertain. The point of vies used is from a US perspective.

If you are based in Europe the geographic point of view  provided below are obviously  somewhat different.

Definition
The Pros
The Cons
Onshore
Any development partner which resides in your country is typically considered an outsourced onshore development 
No cultural issues which can lead to misunderstandings

Same time zone, cooperation during the day is a breeze

Easy to visit the development partner, domestic flight, train or car trip

Consequently it is easy to supervise

Onshore development is the most expensive. Reputable firms easily charge well above 150 US-$ for contract work

Onshore software development firms frequently outsource their work to offshore providers. As a client you might never learn about it. Hence you might overpay.

In some cases onshore firms are very much tied into business networks which are closely aligned with your business. Ideas or concepts you deem as confidential are leaking to other companies in your space. This can happen through staff attrition or related development work

Nearshore
A company which resides in neighboring countries with a time zone difference  of perhaps up to  4 or 5 hours is usually considered Nearshore. Examples are South America, Canada, Jamaica
The provider is removed but you still have between 4 to 6 hours of overlap in the time zones, enabling you to efficiently cooperate throughout the day.

Pricing will be significantly cheaper than onshore pricing.

There is a certain cultural alignment. Developers in nations mentioned as nearshore providers are used to the US way of thinking.

Nearshore development is not a radical solution. It is more expensive than offshore development as such a lot of the advantages are mitigated.

Nearshore provider are not easy to reach. Travel times are frequently more than 8 or 10 hours and flight is the only option.

Nearshore providers might have significant language barriers.

Offshore
Offshore Development is usually associated with development done on other continents with significant time zone differences. Examples are Asia and Europe
Offshore providers are usually the cheapest by a wide margin.

Not unusual to find development companies with big product portfolios and a lot of related work  experience.

Because true offshore development companies tend to be bigger in size they usually have defined processes to manage a relationship


Offshore Development centers reside on the other side of the clock. Time zone differences are usually 8 hours or more.

The command of the English language is often times average. Only Project Managers and Senior Developers speak good English.

Work hours usually only overlap up to 4 hours.


At the end of the day it really comes down to what the company is prepared to pay...and the trade off the company is prepared to accept if it decides to pursue a lower cost provider.

 There is little doubt that onshore development is the easiest one to manage. The downside is of course that the expense is by far the highest.

Conversely, true offshore development in Asia is usually the cheapest. A lot of corporations are comfortable with offshore development and are prepared to accept some of the difficulties working with a company on the other side of the clock.


Here Are The 5 Reasons Why Every CEO Should Consider Outsourcing IT As A Business Strategy...

When outsourcing and IT are mentioned in the same sentence a lot of people are thinking about job losses and the disruption it will cause to the company. Sometimes this is the case. More often though outsourcing augments an existing business strategy without disrupting existing work processes.

Outsourcing IT has become a business strategy to improve overall operational efficiency, helping companies to realize their Key Performance Indicators (KPIs).

Some of the specific reasons why a company should consider making outsourcing part of  their overall business strategy are below:


Reason # 1:

For years now the role of the IT manager has become more all encompassing.  IT strategy has become a core concept to drive and maintain revenues and the competitive position of the business.

Today's IT managers have seen additional requirement layered upon them. Besides the traditional workload IT managers now have  to address requirements in areas like cloud implementation, integrating legacy systems, hybrid cloud strategy and  operational audits. On top of that businesses now look to IT management for valuable input as to business strategy development.

Another important responsibility IT managers have to deal with nowadays is Digital/Cyber crime which alone can chew up the daily workload of any seasoned IT professional.

With all of these new requirements layered upon IT management it is no wonder that a lot of IT professionals are overburdened.

Outsourcing part of the responsibilities to professionals with significant experience in any of those areas can relive the existing IT management and help the business to hit its internal Key Performance Indicators. (KPIs)

Reason # 2

Outsourcing allows management to augment their existing IT team. Delegating lower level or repetitive tasks to an outsourcing team will relieve the internal team, thus allowing it to focus on higher level development and tasks.
.
If done right it will boost the In House morale of the IT team since they will feel relief is on the way without having to worry about job security.

The concept of augmentation enables the company to maintain a core team with core competency whiles scaling up (or down) resources as needed.

Reason # 3

One of the more intriguing aspects of outsourcing is the easy access to a wider talent pool.

When a company decides to adapt a new technology platform which is not part of the skill set of the existing IT team outsourcing is often time the ideal solution.

The talent is available at a lower price point and can be scaled up or down as needed.  As such the investment into new technologies can be minimized without sacrificing performance.

Reason # 4

The organization will become more nimble and address changing market needs much faster.

Every company faces the problem of being stuck in their ways. This is not limited to just IT heavy organizations but the problem is perhaps more difficult to address for them.  Retraining existing personnel to use newer technologies is in almost every case prohibitively expensive or simply not practical.

Because of the high hurdle companies are forced too maintain existing older technologies much longer than is good for them.

Having a nimble outsourced IT organization at your disposal can break this cycle. Compabies can create a two speed IT lane where innovation is driven at different pace.

Reason # 5

It goes without saying,  outsourcing done right will also save money. It should not be the reason why a comp nay considers outsourcing as a business strategy  it but it certainly is a benefit a lot of companies like to realize.



Every company has a unique situation it needs to evaluate in order to decide if outsourcing enhances the corporate strategy.

I vouch to say that it should always be added to the mix. It is a tool which should always be at the disposal of the CEO/CIO. Even if the strategy is used on a very small scale, perhaps as an experiment, it will educate the C level as to what is possible.

Even a very limited outsourcing approach  will prepare  the company for the moment outsourcing becomes a part of the corporate strategy.






Does Agile Makes Software Development More Expensive...Yes And No...Here Is Why

I am in the business of providing outsourced software development. When we design the requirements of a new software development a Requirement Manager will go through the entire project with the client and find out what specifically the client needs.

Often times the client is not necessarily aware of all the requirements it has when the project starts. There are general ideas,  but sometimes the general concept has not been completely thought out.

A good Requirement Manager can be extremely beneficial in a situation like this. He/She will think along with the client and sketch out in technical terms what functionality the developers have to code.

The requirements then form the basis of the development model.

In a traditional development model (Gantt Charts and Milestones) at certain predetermined intervals the clients get a chance to review an interim product built and, once approved, the next step of the product will be developed.

The Agile development is different in so far that the client stays much more involved in the development. There is a constant back and forth (usually daily) with questions raised by the developers (typically through the Project Manager) and being answered by the client.

For a more in depth explanation of what an Agile project development looks like see here

Testing of certain functionalities happens much more frequently and often times unrelated development steps are being conducted at the same time.

The whole idea of an Agile  project development (versus Gantt and Milestones) is to make the client more involved, thus enabling  him to constantly improve upon the final product. Nonsensical development is supposed to be recognized earlier on..thereby reducing 'errand" development time.

 One can argue  which approach is better. I certainly feel Agile is the way to go.

One inherent side effect which develops out of the Agile Project Management approach are changing requirements. What typically happens is that the more the client gets involved in the development process and gets to play around with the product...the more the client gets a feel for what the final solution should truly look like under real life conditions.

Consequently a client will update the requirements. Features get added and / or amended.

Needless to say...the adding of additional features makes the development more expensive. Every time an additional feature is added more hours have to be paid for.

Therefore the argument has been made that Agile is "more expensive".

I  wholeheartedly disagree with that opinion and, as a matter of fact, believe that an Agile approach will make the development cheaper.

That might seem counter intuitive at first..but here is why.

It is a simple fact that the Minimum Viable Product built ( MVP , the first development) is always just the first step to a more final product. As soon as the MVP is out and people start using it there is feedback coming in, suggesting updates and improvements.

Using an Agile approach ensures that the MVP is a much better solution than the MVP built using a simple Gantt based approach.

Precisely because the client has been more involved in the development and was able to add and/or update features while development was still going on less actual software development (= less developer time)  had to be done.

It is obviously much cheaper to add a feature at an early stage (or amend functionality) when there are less interconnections to be worried about. By completing these changes earlier in the project a significant time saving can be accomplished versus changes to a released  Minimum Viable Product built.

The Agile Development approach delivers a reduction in development time  because the product release will be much closer a a more  "More Final Product".

Using a Gantt development approach the costs to bring a Minimum Viable Product to a a more Final Stage Product are often times significant.

Anyone who has been in the Software Development Business long enough can tell stories where entire functionality modules were just missed...and had to be created after the fact (the MVP built) at great expense.

Using Agile a better MVP gets created, one which much  more resembles a Final Product. Because the  MVP  built using the Agile approach is better  the overall development costs are reduced.















Why Excel And Email Should Not Be The Backbone Of Your Outsourcing Relationship...True Story What Went Wrong

Amazing but so true....It is a well established fact that a lot of companies are managing their outsourcing relationship through the use of Email and Excel. For a small job limited in scope and duration this solution might do the job, at least on the surface.  (I would always advise against it though).

What is a bit surprising  is that even bigger contact values, some of which have annual contract values of a few hundred thousand US-$ (or more) are being managed this way.

I recently had a discussion with a new client who is, to put it mildly, in major trouble because their outsourcing vendor and the company agreed to collaborate using email and excel.

Now...there are lots of reasons why this is  a bad idea. (productivity , level of collaboration and so on...)  For today though I will limit myself to tell the story what happened to my client.

The company started with a vendor in Bulgaria about 3 years ago. The relationship commenced  with a small software development project, limited in scope and duration.

As mentioned earlier..the use of email and Excel might seem adequate at first ...but you never know what might happen.

Sure enough, the outsourcing vendor did a pretty good job and the relationship continued to evolve. Additional layers were added to the initial development, each with its own functionality.

What was a small and isolated deployment became an enterprise solution.  Everything worked just fine. The relationship was managed by a project manager in Bulgaria and the head of IT in the US.

Let me be clear what I mean when I say "It worked just fine".

What worked was the day to day operation and cooperation between the vendor and the company. Senior management on the company side did not get involved and neither did (so it seems) management on the Bulgarian side.

As is often times the case in the the outsourcing world....the vendor decided to merge with another entity.

Both of the outsourcing companies agreeing to merge were smaller which might explain what happened next.

The Project Manager on the Bulgarian side decided he was dissatisfied with the new working arrangement and left. A new Project Manager was put in charge...but unfortunately he did not have the complete access to all of the old emails.

Apparently a decent chunk of the emails were sent  and received from the personal laptop of the Project Manager...and when he left he took what was his personal laptop.

What ensured was that the Head of IT became the back up to the Bulgarian company. A relationship which worked because both parties had worked together and knew the functionality  of every development became one sided. The new Project Manager in Bulgaria was now being trained by the Head of IT.

From there it went downhill rather quick. Some old emails hadn't successfully migrated when the Head of IT had gotten a new computer. The very same files were not available anymore at the now newly formed Bulgarian company. Obviously a major problem.

The Head of IT..undoubtedly recognizing that trouble was brewing...then tendered his resignation. A new Head of IT was appointed and by the time he fully started to get into all of the mechanics of the outsourcing relationship it was time for the old Head of IT to leave.

At this point it had become apparent to everyone involved that what was a successful relationship had suddenly become a major mess.

There was almost no documentation, the chain of emails was often times non nonsensical because anything discussed and agreed via skype was at least partially missing and it had become sometimes impossible to square the discussion of an email chain with the functionality or module which was discussed.

In short..there was no place for the new Head of IT to get all the relevant information relating to a specific development...nor was there a chronological approach for him to review the emails to get a good understanding what had transpired.

Fortunately the company managed to work through the issues and it overcame what was a very difficult time.  Some of the missing files were recovered  from old back ups and the new Head of IT made it a point to assemble proper  documentation.

It had taken months to clean up the mess..but at the very least there was no need to discard prior work.

The lesson to be learned here is that all of the problems and difficulties could have been avoided through the use of a proper collaboration tool.

There are a few software solutions which allow for a complete management of the relationship, offer built in back up functionality and are, by their very nature, ideal to generate the documentation needed so that a new person coming in can get up to speed.

We use Active Collab (https://www.activecollab.com/) but there are obviously other tools available.

At the end of the day it does not matter which tool is being used..the important thing is that something is being used. Email and Excel won't do it..and the above is the story of one CEO who learned this the hard way.







How One Company Overspent On Its Outsourcing By 500 % ...The Dirty Truth Every CEO Should Know

Quite a while ago ago I talked to a company which was looking to kick off a bigger software project. They never went ahead with it and it was just another deal which did not bear fruit. Nothing unusual about it.

What makes it newsworthy though is that the CEO of the company reached out a few months ago and asked if we were to able to pick up the maintenance and service for the software they had developed.

Obviously a pretty easy thing to do. We priced it out, arranged for the delivery of the software (source code) and got to work. As is customary in those situations we  had a few developers read through the code with the goal to familiarize ourselves with the code and the functionality.

As part of the code review we found some developer comments (once again...nothing unusual). What made it a bit unusual was that burred in the code were clear references as to which company had actually written the code.

This is where things got interesting. Below is a quasi recap of the the conversation I had with the CEO, our client.


Steve: So....when XYZ (company name embedded in the code) developed the API they... 
CEO Interrupts me: Who is XYZ ?
Steve: The guys who developed the code
CEO: No..they aren't
Steve....(pause...does not say anything)
CEO: What makes you say that ?
Steve: Well..there are clear references in the code that they are the author of the software you delivered 
CEO: What ?...I don't understand...we had it written by XXX


The CEO (our client) then took it upon himself to get to the bottom of the issue. Did not take him to long to find out as to what had happened.

The company which he had contracted with to develop the software had outsourced the entire development to a provider in India.

The CEO was rather flabbergasted that this was possible. He had paid premium pricing (his words) assuming that the product was going to be developed onshore in the US. Doing the math by using our rates he figured he had spent about 250k more than what he should have paid.

Obviously 250k can be a lot or very little money for a corporation. In this case the company is privately owned and the CEO happens to be the majority shareholder. Company is doing well...so money was (or is)  not the issue.

The issue for the CEO was simply that he felt he had been taken advantage off...led to believe that it was an onshore development when in reality all of the work (or vast majority) was done offshore.

And this brings us to the dirty truth every CEO should know.

A lot of software development billed at domestic developer pricing is parsed out to providers offshore.

Decision makers should be aware that not in every case what is sold as a domestic development is actually developed domestically.

There is obviously a certain added comfort level for a US company to deal with a US based software development company. The CEO/Decision Maker might feel more comfortable...but the truth of the matter is that the company  might not be exactly getting what it has paid for.



 

India Is Still The 800 Pound Gorilla In IT Outsourcing...

India might have lost its leadership in call centers to the Philippines...but it certainly does not show any signs of slowing down when it comes to ITO (IT Outsourcing).

There is certainly strength in raw numbers. With a population of almost a Billion people India is basically the only place in the world where a major company can set up with the goal to hire a 1000 software engineers and not running into problems as to pricing and general availability of talent.

The building of technology centers where a few thousand engineers can be supervised  under one roof has always been the one advantage none of India' competitors in the global outsourcing world can match.

India's National Association of Software and Service Companies (Nasscom) just announced that the sector increased employment by about 230,000 in 2015. Total employment for the sector now stands at about 35 Million.

By their own estimate the Indian BPM sector (Business Process Management) has now captured approximately 56 % of the total global market for IT related outsourcing services.

These are huge numbers. If you consider that the entire population of the Philippines is only about 98 million and India employs just in ITO 35 Million...it really shows that there is strength in raw numbers.

Of course, only few companies really have a need to hire hundred's of developers and for most companies there are other places in the world to get their ITO done as good or perhaps even better than what India has to offer.

At the end of the day it only matters what your own outsourcing team is capable off...as such there is really no strategic advantage outside of sheer numbers India can offer.

Never the less though...the  numbers are impressive.

India's Nasscom Releases 2015 Revenue And Market Share Numbers




The Dirty Truth - Your Outsourcing Team Might Be To Young ?

One issue I  frequently discuss with corporations which have outsourcing relationships with other vendors is that they are often times not happy with the performance provided. There is not one single performance matrix which is leading corporations to that conclusion but rather this is often times an across the board assessment of the relationship. The attitude is that it works, albeit not great.

Some of the frequently mentioned  Key Performance Indicators which lead to that assessment are :

  • Development Sprints take to long to completion
  • Sprints are simplified by reducing the number of sub tasks
  • Q&A takes to long
  • Average time for bug fixes  

I am often times amazed that the prevailing mindset seems to  be that this is just "fine"  and  lesser performance is to be expected when outsourcing. After all...pricing is low enough that it does still make economic sense.  (and I am sure that is true for a lot of outsourcing relationships).

Let me perfectly clear...I am the first one to admit that there is a productivity gap between an onshore and offshore software developer.

What is important to realize though is that with familiarity the productivity gap will start shrinking right away. The actual gap remaining after a month or two month is subject to debate...in my opinion it is not uncommon that the gap will be eliminated completely, but as I said...it is subject to debate.

As such the question needs to be looked at why the feeling is so often that the quality of the work is just not great. In my experience and when discussing the outsourcing strategy I usually learn that in situations like the ones described above the outsourcing vendor is looked upon as a cost center.

The most important factor in negotiating any outsourcing deal is most often the hourly rate or team rate being charged. Corporations will negotiate to get the lowest rate to realize the most savings.

The strategy does of course makes sense to the corporation...but the flip side of the coin is that it does then lead to shortcoming in the composition of the development team.

A low rate will lead to a team which is predominately staffed with junior developers, supervised by a few senior guys. The problem with that approach is that the Junior developers are afraid of the power wall...they lack the authority and confidence to challenge their immediate superiors or anyone from the client side.

Consequently the back and forth which ultimately results in a more productive and informed process is lacking.

Of course not every corporation is going to willingly spend more money on its offshore development team to change the mix up of the team. It might be a good investment though...just exchanging one or two junior developers with mid-level developers might create the bridge the team needs to overcome the power wall, both internally and externally.

If the budget is set in stone another option is to exchange 3 junior against 2 mid level developers (given the team size allows for it). It should be cost neutral  but it is my experience that the change in team dynamic will boost productivity and improve the overall KPI's despite the reduction in team size.

















Who Knew...Jamaica Is Becoming A Major BPO Hub

Of course,  by pure numbers Jamaica  lags the traditional outsourcing destinations like the Philippines and India. Never the less...the country has steadily increased its footprint in the BPO sector. It is estimated that the country will be home to about 20,000 ICT BPO jobs by the end of 2016.

Obviously 20,000 is not a big number when you compare it to the main outsourcing centers in the world. Given a total population of about 2.7 Mio though  the government is realizing that the BPO sector is worth to be promoted. At the given growth rate of 20 % the sector will employ about 1 % of its population by 2018/2019.

Jamaica's inroads into the global BPO industry are driven by an advantage none of the traditional outsourcing destinations can match. It shares the same time zone as Chicago (CST), therefor collaboration throughout the work day is seamless.

Jamaica's predominant language is English....another advantage why US BPO companies like to establish a presence there.

The local salary structure makes it highly feasible to outsource technology talent. The median salary in the Jamaican IT industry is about 150k Jamaican Dollars (about US- $ 1,220). The rate is therefore comparable (and even lower)  to what has to  be paid for local talent in India or the Philippines.

One issue is the relative small size of the Jamaican labor market. It is clear that with increased demand for IT staff local salaries are sure to rise. Given that the BPO industry is notoriously price sensitive it seems likely that the strategic advantages Jamaica enjoys will be buffered by the disadvantage of  increases in salaries in the BPO sector.  

Never the less, for the time being Jamaica might be a good place to establish a BPO center.



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.




Does The Cloud Reduce The Demand For Outsourcing..or doesn't it?

One of the effects of the rise of the cloud is that vast parts of roles traditionally filled by outsourcing companies are falling away. Simply put...there is no need (or a diminished one) for DBA and Systems Architects. The hardware side is basically eliminated. The article below makes the point though that there is a partial offset because of the need to develop middle ware which sits between the client and the cloud.

I can attest to that...just among our client we see that the issue of how to manage various cloud solutions and properly integrate them into an enterprise becomes more and more pressing. I also feel that the technical solutions are becoming more ambitious since there is no longer a hardware limitation which would have created a bottleneck in the old, pre-cloud days.

Does the cloud eliminate or create outsourcing/BPO jobs