Welcome!

Microservices Expo Authors: Pat Romanski, Elizabeth White, Liz McMillan, Charles Araujo, Flint Brenton

Related Topics: Microservices Expo

Microservices Expo: Blog Feed Post

ROI - Is It Always Required for a Software Project?

The danger of misclassification is to doom a project to failure even before you have started

Can you think of an instance where a software project had to completed on schedule and the measure of ROI was of secondary importance? When a piece of software is part of a larger initiative the ROI becomes less important and the fallout of any delay may far outweigh the investment on the software.

Latest trend in agile and lean methodologies is to weigh every feature in the scale of “measurable business value” before acting on it. This approach, for some type of projects, may be redundant or even counter productive. In my opinion, software projects can be classified into 5 types - ROI, 7th-Habit, O-Ring, Hype-Cycle & Build-to-Flip.

Let's look at the characteristic of each type of projects and what makes each of them successful. I have also added how agile methodologies can aid the success. The danger of misclassification is to doom a project to be failure even before you have started.

ROI Projects

There is a class of software projects where delivering business value is the key. The measure of value need to be quantifiable and can typically be:

  • Cost saving
  • Revenue generation
  • Customer satisfaction
  • Cycle-time reduction

If I spend “X” dollars I will get “Y” benefit = measurable value delivered to business.

Approval Process: Follow a variant of the following 4-step process:

  1. Identify and quantify business benefit
  2. Translate into software requirement
  3. Estimate – time and money required
  4. Obtain approval based on cost benefit analysis – the analysis may be absolute or relative to other projects

Pitfall: To get the project approved, the benefit may be (consciously or unconsciously) overstated. Alternately cost may be understated or impact of critical technical challenges not fully understood.

How agile can help:

Fail early – This is where use of agile methodology can be of great help. Used properly, it can identify, early in the project lifecycle, if the projected cost-benefit analysis is realistic. If it is not then the project can be allowed to fail early thereby saving considerable expense and heartache.

Incremental value – If the project is such that it will be feasible to make phased releases either to a small community of users or with subset of business critical features, then adopting agile methodology will allow value to be realized even before the completion of the project.

7th-Habit Projects

The seventh habit (see 7 Habits of Highly Effective People by Stephen R. Covey) is “Sharpening the Saw” or about renewal.

These are already running applications and have to be re-written for one of the following reasons:

  • Technology obsolescence – either hardware or software
  • Problem of maintainability – lack of people or unwieldy code base
  • Integration challenge

The applications would have been in use for a long period of time. Though the UI may be archaic, most users will be reluctant to switch to anything different. For such project, value will be intangible and it will be difficult to quantify. The renewed version of the product will normally will need to replicate the functionality of the existing application with some enhancements thrown in.

In the airline industry, majority of the ticketing runs on IBM mainframe and the application is developed using TPF which is a second generation language. IBM has declared that support for TPF is going to be withdrawn and it is to be replaced by z/TPF.

Approval Process: Ask the following questions:

  1. Can we afford to do it?
  2. Can we afford NOT to do it?
  3. Is there any alternate way of satisfying the business need?
  4. Is this application still relevant?

Pitfall: The project will be deemed successful only if users find the version at least as reliable and useful as the old system. The biggest risk is to miss out on the key feature, functionality or usability issue. This may happen when key users are unwilling to spend enough time or knowledge of specific feature is lost and is only available as code.

How agile can help: One of the challenges in using agile methodology for such project is the reluctance of users to contribute time and effort. If no major enhancements are planned then the developers are expected to study the existing system and derive the requirement. However, if the user interface is being revamped, then iterative refinement with constant user feedback can make or break the project.

O-Ring Projects

On January 28, 1986, when Space Shuttle Challenger broke apart 73 seconds into its flight, leading to the deaths of its seven crew members. Disintegration of the entire vehicle began after an O-ring seal in its right solid rocket booster (SRB) failed at liftoff. It had lost its elasticity because of the unusually cold outside temperature.

Sometimes, software becomes an O-Ring in a large infrastructure project or new product release. In such cases, quality and on-time-completion becomes so much more important than any other parameter. 100% budget overrun may be an acceptable tradeoff to either prevent a bug or to avoid short delay.

When you are planning to open a new terminal building in an airport like Heathrow Terminal 5, software will be a small (cost wise) but important component in it. However, it will be at least as critical as any other component or equipment. The complete software has to be ready in time and has to function flawlessly. Even few days delay may lead to revenue loss in excess of the cost of the software. Also, any quality problem can damage the image of the organization.

Approval Process: Since such project will be a component of a larger project, there will be no separate approval process. However, following questions need to be asked:

  1. What to make – what to buy?
  2. How much to automate?
  3. Is the scope too ambitious?
  4. How much premium can be paid to reduce risk?

Pitfall: The biggest pitfall is to underestimate the complexity and technical challenge especially integration challenge. Many of these will surface only towards the end of the project when the deadline pressure will be at its peak.

How agile can help: Since, such project require a big bang release, what value agile can bring is not immediately obvious. However, for such project early mitigation of technical risk may be critical. Tackling them in an agile manner early in the project lifecycle can greatly increase the chances of success.

Hype-Cycle Projects

Hype-cycle is a term promoted by Gartner to provide pointers to how new technology adoption happens. Every technology goes through a “Peak of Inflated Expectations” where everybody jumps into the bandwagon. People want to cash in on the early mover advantage and time becomes of essence.

For such software projects, “being there” as quickly as possible is major driver. Though, cost and quality cannot be ignored, but they take a back seat.

With the release of iPhone from Apple, it became important for organization to release an iPhone application to the market. Scenario one is when you want to be the first and be perceived as the leader. Scenario two is when your competitor has already released such an application and you need to follow suit lest you be perceived as a laggard organization. It is the same story with Facebook applications.

The story of Cloud Computing or SOA is little different – there you are afraid that you may be missing out on something important. Therefore you want to try it out. In all these instances it is difficult to quantify measurable business value which is realistic. It is important to be there as quickly as possible.

Approval Process: Ideally such projects need to be driven by an evangelist. It will be a discretionary spending and money may either come from technology budget or marketing budget. The decision making is unlikely to be logical and based on figures – it will be a right-brain decision.

Pitfall: Normally, chances of failure for such projects will always be high. However, not responding to changing scenario fast enough can lower the chance of success to almost zero.

How agile can help: Since the area is new, the requirement needs to emerge and change during the course of the project. For such projects, it is difficult to envisage any methodology other than Agile.

Build-to-Flip Projects

The term build-to-flip was coined by Jim Collins, the co-author of Build to Last. If you have an innovative idea, you start a company, create a prototype, get VC funding and build your idea to a level where you have sufficient user base to sell the whole venture. Significant percentages of such ventures are purely software projects. Alternately, software would be a major component in the development effort.

Build-to-flip projects have some similarity with hype-cycle project but have its own unique characteristics. The innovator will start with an idea but in most cases it will not be fully formed. Whole plan needs to be flexible and the product needs to morph based on the feedback, likes and dislikes of the early adopters. The innovator needs to be sensitive to unintended usage of the idea. In addition, the early adopters will also become the beta testers. Quality may not be the most critical factor. Twitter, for example, used to crash quiet frequently in the initial days. That did not prevent it from being one of the biggest successes of recent times. Rolling the right features out as soon as possible may be the key to success.

Approval Process: You need an idea which can grow big. You need to sell the concept to a funding agency, probably a VC. If you succeed then you are on.

Pitfall: Not everybody is Steve Jobs – you may not be able to create an iPod or an iPhone in the first attempt. You will need to iterate and listen to early adopters. Not doing so quickly enough is a sure road to failure.

How agile can help: Not only will agile development is mandatory, agile deployment is also critical. Option of continuous deployment is also worth examining – here is a nice example.

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
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. H...
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
The taxi industry never saw Uber coming. Startups are a threat to incumbents like never before, and a major enabler for startups is that they are instantly “cloud ready.” If innovation moves at the pace of IT, then your company is in trouble. Why? Because your data center will not keep up with frenetic pace AWS, Microsoft and Google are rolling out new capabilities. In his session at 20th Cloud Expo, Don Browning, VP of Cloud Architecture at Turner, posited that disruption is inevitable for comp...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
"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...
Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
Containers are rapidly finding their way into enterprise data centers, but change is difficult. How do enterprises transform their architecture with technologies like containers without losing the reliable components of their current solutions? In his session at @DevOpsSummit at 21st Cloud Expo, Tony Campbell, Director, Educational Services at CoreOS, will explore the challenges organizations are facing today as they move to containers and go over how Kubernetes applications can deploy with lega...
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 ...
Learn how to solve the problem of keeping files in sync between multiple Docker containers. In his session at 16th Cloud Expo, Aaron Brongersma, Senior Infrastructure Engineer at Modulus, discussed using rsync, GlusterFS, EBS and Bit Torrent Sync. He broke down the tools that are needed to help create a seamless user experience. In the end, can we have an environment where we can easily move Docker containers, servers, and volumes without impacting our applications? He shared his results so yo...
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
Enterprise architects are increasingly adopting multi-cloud strategies as they seek to utilize existing data center assets, leverage the advantages of cloud computing and avoid cloud vendor lock-in. This requires a globally aware traffic management strategy that can monitor infrastructure health across data centers and end-user experience globally, while responding to control changes and system specification at the speed of today’s DevOps teams. In his session at 20th Cloud Expo, Josh Gray, Chie...
Kubernetes is a new and revolutionary open-sourced system for managing containers across multiple hosts in a cluster. Ansible is a simple IT automation tool for just about any requirement for reproducible environments. In his session at @DevOpsSummit at 18th Cloud Expo, Patrick Galbraith, a principal engineer at HPE, discussed how to build a fully functional Kubernetes cluster on a number of virtual machines or bare-metal hosts. Also included will be a brief demonstration of running a Galera MyS...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
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...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, 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.
In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals – as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.