Welcome!

Microservices Expo Authors: Pat Romanski, Liz McMillan, Elizabeth White, Mehdi Daoudi, Flint Brenton

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
With the rise of DevOps, containers are at the brink of becoming a pervasive technology in Enterprise IT to accelerate application delivery for the business. When it comes to adopting containers in the enterprise, security is the highest adoption barrier. Is your organization ready to address the security risks with containers for your DevOps environment? In his session at @DevOpsSummit at 21st Cloud Expo, Chris Van Tuin, Chief Technologist, NA West at Red Hat, will discuss: The top security r...
DevOps at Cloud Expo – being held October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real r...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
The last two years has seen discussions about cloud computing evolve from the public / private / hybrid split to the reality that most enterprises will be creating a complex, multi-cloud strategy. Companies are wary of committing all of their resources to a single cloud, and instead are choosing to spread the risk – and the benefits – of cloud computing across multiple providers and internal infrastructures, as they follow their business needs. Will this approach be successful? How large is the ...
21st International Cloud Expo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Me...
Many organizations adopt DevOps to reduce cycle times and deliver software faster; some take on DevOps to drive higher quality and better end-user experience; others look to DevOps for a clearer line-of-sight to customers to drive better business impacts. In truth, these three foundations go together. In this power panel at @DevOpsSummit 21st Cloud Expo, moderated by DevOps Conference Co-Chair Andi Mann, industry experts will discuss how leading organizations build application success from all...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
‘Trend’ is a pretty common business term, but its definition tends to vary by industry. In performance monitoring, trend, or trend shift, is a key metric that is used to indicate change. Change is inevitable. Today’s websites must frequently update and change to keep up with competition and attract new users, but such changes can have a negative impact on the user experience if not managed properly. The dynamic nature of the Internet makes it necessary to constantly monitor different metrics. O...
Today companies are looking to achieve cloud-first digital agility to reduce time-to-market, optimize utilization of resources, and rapidly deliver disruptive business solutions. However, leveraging the benefits of cloud deployments can be complicated for companies with extensive legacy computing environments. In his session at 21st Cloud Expo, Craig Sproule, founder and CEO of Metavine, will outline the challenges enterprises face in migrating legacy solutions to the cloud. He will also prese...
Enterprises are moving to the cloud faster than most of us in security expected. CIOs are going from 0 to 100 in cloud adoption and leaving security teams in the dust. Once cloud is part of an enterprise stack, it’s unclear who has responsibility for the protection of applications, services, and data. When cloud breaches occur, whether active compromise or a publicly accessible database, the blame must fall on both service providers and users. In his session at 21st Cloud Expo, Ben Johnson, C...
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...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
The nature of the technology business is forward-thinking. It focuses on the future and what’s coming next. Innovations and creativity in our world of software development strive to improve the status quo and increase customer satisfaction through speed and increased connectivity. Yet, while it's exciting to see enterprises embrace new ways of thinking and advance their processes with cutting edge technology, it rarely happens rapidly or even simultaneously across all industries.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
"When we talk about cloud without compromise what we're talking about is that when people think about 'I need the flexibility of the cloud' - it's the ability to create applications and run them in a cloud environment that's far more flexible,” explained Matthew Finnie, CTO of Interoute, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
One of the biggest challenges with adopting a DevOps mentality is: new applications are easily adapted to cloud-native, microservice-based, or containerized architectures - they can be built for them - but old applications need complex refactoring. On the other hand, these new technologies can require relearning or adapting new, oftentimes more complex, methodologies and tools to be ready for production. In his general session at @DevOpsSummit at 20th Cloud Expo, Chris Brown, Solutions Marketi...
Leading companies, from the Global Fortune 500 to the smallest companies, are adopting hybrid cloud as the path to business advantage. Hybrid cloud depends on cloud services and on-premises infrastructure working in unison. Successful implementations require new levels of data mobility, enabled by an automated and seamless flow across on-premises and cloud resources. In his general session at 21st Cloud Expo, Greg Tevis, an IBM Storage Software Technical Strategist and Customer Solution Architec...
Most of the time there is a lot of work involved to move to the cloud, and most of that isn't really related to AWS or Azure or Google Cloud. Before we talk about public cloud vendors and DevOps tools, there are usually several technical and non-technical challenges that are connected to it and that every company needs to solve to move to the cloud. In his session at 21st Cloud Expo, Stefano Bellasio, CEO and founder of Cloud Academy Inc., will discuss what the tools, disciplines, and cultural...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...