Welcome!

Microservices Expo Authors: Stackify Blog, Automic Blog, Simon Hill, Pat Romanski, Liz McMillan

Related Topics: Microservices Expo, Java IoT

Microservices Expo: Article

Five Questions You Need to Ask Before You Outsource an Agile Project

Why do you want to do the project in an Agile mode?

If you think that the following points are an oversimplification of a very complex subject of outsourcing agile project – you will be right and I agree with you.

However, I think these questions are a good starting point for your research before you actually go ahead and outsource an agile project.

1. Why do you want to do the project in an Agile mode?
Here are three possible reasons for wanting to do an outsourced project in agile way. Take your pick:

(A) You are already engaged in outsourcing and have established a good working relationship with the outsourced vendor. You have tried agile way of working internally and it has worked for you. You want to extend it to outsourced projects.

(B) You want to outsource a new project because you do not have internal bandwidth to either work on the requirement or on the development. You expect that outsourcing will help you overcome the bandwidth limitation and agile methodology will help you to evolve the requirements through multiple iterations.

(C) You do all your projects in an agile and to achieve immediate cost saving you plan to outsource some piece of work. So, it is natural for you to choose agile way of executing the project.

If you have chosen (A) then you then you have a good chance of success. The primary criteria for success of agile are trust and good communication and you seem to have both in place.

If you have chosen (C) then you may pull it off but you need to scale your expectation down on the immediate cost saving potential. It takes time, effort & energy to build relationship – initially that is going to be an overhead.

However, if you have chosen (B) then …

As it is, agile is communication intensive. When you bring in outsiders the communication load becomes more. So, if you are not in a position to devote time to understand what you need and create the stories, if you are not in a position to spend time to clarify doubts and answer questions as and when required, if you do not have time to meticulously review the deliverables of every iteration – your project will be doomed.

You should either understand agile well or you should understand outsourcing well before you try agile outsourcing.

2. Do you want to outsource just this project or are you looking for a partner?
This question is relevant only if you do not already have an outsourcing partner.

Agile without trust does not work.

Trust gets established between individuals and not between organizations. There is no substitute for an initial face to face interaction. At the start of the project key people from both sides should together at the same location and work together for a reasonable amount of time. One month would be ideal. If you want to optimize on cost, you should still have at least one week of working together.

Agile without a mechanism for smooth and effective communication does not work.

Setting up effective communication channel, be it dedicated communication link, be it video conferencing facility, be it necessary tooling infrastructure all require investment.

To establish these takes time … and effort … and energy. Doing it for just one project may not give you sufficient return on the investment that you make to get the whole think working.

Therefore, take a long term view and look for a partner who can help you with multiple projects.

3. What type of commercial model you should look at?
There are three alternatives – either one or a combination can work for you.

(A) You can have a Time & Material (T&M) contract where you agree on the rate for different people will different levels of experience and expertise and pay the vendor according to how much time they spend on your project. Though this is the simplest mechanism all the risks are with you and the vendor has no incentive to work more efficiently.

(B) The second alternative is to have a Fixed Price contract where you define the scope of the project in sufficient detail and agree to pay a fixed price for it. This runs counter to the basic philosophy of agile where you actively encourage requirements to evolve and change. Therefore, for fixed price to work you need to have a mechanism to compensate the vendor for changed requirement and rework, which you may do in a T&M basis. However, you need to keep in mind that what is a change and what is within scope can become a very controversial topic.

(C) The third commercial model can be based on some objective measure of the amount of work done. People have tried many different methods of sizing like using Story Point or Function Point. Each has its own advantages and disadvantages. The one I like is MK-II Function Point (this and this). It gives a good basis for calculating incremental effort. However, it does not cover effort required for rework, refactoring and impact of technological change.

I do not think there is one best method of structuring a commercial model. However, a good approach is to sign a Master Services Agreement (MSA) which specifies the overall terms and conditions including rate but does not get into specifics of a project. The scope of work can be outlined through a Statement of Work (SOW) which can include high level product backlog.

You may have to try out different model – combination of models – and see which one is best for you. Starting point would be to create a flexible MSA.

4. What payment term should you have?
Since Agile is iterative and there is emphasis on continuously delivery of “potentially shippable product”, you need to pay either at the end of each iteration or you need to pay at the end of a pre-agreed time period like at the end of the month.

If you decide to pay at the end of each iteration then you need to decide if you will enforce a mechanism of accepting the delivery of iteration. You need to decide what you will do if there are bugs or other forms of deficiencies found. You have 3 choices:

(A) You accept the fact that some amount of defects are inevitable and expect that those defects will be fixed in the next iteration and go ahead and make the payment anyway – this is not a very good idea.

(B) You set a threshold of defect and create a separate sprint to close those defects and accept the iteration only after all the defects are closed – this may upset your sprint planning.

(C) You do not your sprint plan but expect the vendor to correct the defects in addition to whatever is expected to completed in the sprint and release the payment only after all the defects are closed – this will put additional load on the team but will force them to deliver better quality product.

There is one more point which you need to keep in mind. One of the benefits of agile is to fail early rather than fail late.

So you need to have a clause in the contract of project termination midway if you realize that you are not going to get the business benefit originally envisaged.

5. Are you sure the vendor understands your definition of “done”?
One of the principles behind agile manifesto says “Working software is the primary measure of progress”.

However, in an enterprise context is that enough? Would the same set of people who have developed the code going to maintain it for years to come? Is there a requirement to follow any organizational coding standard and guidelines? Do you have any architectural standards that are practiced? Is the application usable? What about performance under real life load? Does it have to integrate with other pieces of software?

So, you need to have a clear definition of what is done. Here is an indicative list of points that your definition should take into account:

  • How you are going to test the delivery?
  • How much documentation is required?
  • Is there any architectural or design standard that needs to be followed?
  • Do you have a coding standard and code review guideline?
  • Do you need to have a Usability testing done?
  • What are the integration needs and how will you test it?
  • How are you going to measure performance under load?
  • Who is responsible for fixing issues while deploying in preproduction and production?

Not having a mutually agreed and a clearly written down definition of “Done” is one of the source of future potential dispute.

Finally…
There is no clear definition of what Agile Methodology means. So you need to thrash out any difference in understanding between you and the vendor. You may find it difficult to adhere to some of the points mentioned in the Agile Manifesto but do keep in mind the 3 important elements which makes Agile agile:

  1. Iterative development and regular delivery of working code
  2. Self-organizing team and emerging design
  3. Direct communication and immediate interaction

More Stories By Udayan Banerjee

Udayan Banerjee is CTO at NIIT Technologies Ltd, an IT industry veteran with more than 30 years' experience. He blogs at http://setandbma.wordpress.com.
The blog focuses on emerging technologies like cloud computing, mobile computing, social media aka web 2.0 etc. It also contains stuff about agile methodology and trends in architecture. It is a world view seen through the lens of a software service provider based out of Bangalore and serving clients across the world. The focus is mostly on...

  • Keep the hype out and project a realistic picture
  • Uncover trends not very apparent
  • Draw conclusion from real life experience
  • Point out fallacy & discrepancy when I see them
  • Talk about trends which I find interesting
Google

@MicroservicesExpo Stories
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
Digital transformation has changed the way users interact with the world, and the traditional healthcare experience no longer meets rising consumer expectations. Enterprise Health Clouds (EHCs) are designed to easily and securely deliver the smart and engaging digital health experience that patients expect today, while ensuring the compliance and data integration that care providers require. Jikku Venkat
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
DevOps promotes continuous improvement through a culture of collaboration. But in real terms, how do you: Integrate activities across diverse teams and services? Make objective decisions with system-wide visibility? Use feedback loops to enable learning and improvement? With technology insights and real-world examples, in his general session at @DevOpsSummit, at 21st Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, explored how leading organizations use data-driven DevOps to close th...
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
"We are an integrator of carrier ethernet and bandwidth to get people to connect to the cloud, to the SaaS providers, and the IaaS providers all on ethernet," explained Paul Mako, CEO & CTO of Massive Networks, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
From our perspective as consumers, perhaps the best thing about digital transformation is how consumerization is making technology so much easier to use. Sure, our television remote controls still have too many buttons, and I have yet to figure out the digital display in my Honda, but all in all, tech is getting easier for everybody. Within companies – even very large ones – the consumerization of technology is gradually taking hold as well. There are now simple mobile apps for a wide range of ...