Welcome!

Microservices Expo Authors: Pat Romanski, Derek Weeks, Liz McMillan, AppNeta Blog, Carmen Gonzalez

Related Topics: Java IoT, Microservices Expo, Machine Learning

Java IoT: Article

Agile Adoption – Crossing the Chasm

Why is it so difficult to switch to agile process from waterfall?

Everybody acknowledges that IT has to plays a key role in any new service or product design. Therefore, IT needs to align with business and be flexible to changing business needs. It is a question of how to be agile rather than should we be agile. Then, why is there such a gulf between the people who evangelize agile processes and those who look at them with great suspicion?

Any application is built to satisfy a business goal. The process has two major steps where the step one is to define the application behavior which will help in meeting the business goal and the step two is to translate the application behavior to a working application. The definition of the application behavior is the requirement specification and it is the link between business and IT.

Business - IT

In the waterfall methodology, development starts after the requirement is frozen. It is assumed that if business users can unambiguously and comprehensively specify the application behavior, IT can build the application satisfying the stated behavior. All the management practices based on waterfall methodology is build around this assumption. However, in most real life project we find that one of the following things have happen.

  • The stated behavior as understood by the business is different from the understanding of IT
  • The stated behavior is a sub-optimal solution for the given business goal
  • The business goal has changed

As a result the final application does not meet the business goal. Then it becomes a blame game between business and IT, where business claims that "this is not what I wanted" and IT claims that "I have delivered as per your signed-off requirement". Since there is a gap between desired application and what is stated in the requirement, it is concluded that the root cause of the failure is improper requirement definition. In the next project more rigorous process is applied to make the requirement definition more comprehensive and as early in the lifecycle as possible. In spite of all these rigor, one of the most frequently cited reason for project failure is improper requirement management.

In current business context, is it possible to freeze requirement?

If we go back in time, most IT applications were written to automate internal processes. The emphasis was on adopting industry best practices. Vast majority of the user were internal to the organization and they had to adopt to the application interface rather than the application interface being tailored for the user needs. Times have changed and many of the IT applications are an integral part of the product or service offering. Significant part of the users are external to the organization. The focus has shifted from following the best practices to having innovative offering. The new motto is usability and user centric design. Though there are guidelines and principle available on how to design such application, in practice it involves many iterations where many idea needs to be tried before a workable solution is arrived at. Sometimes, applications may have to be modified very late in the development cycle. In such cases, though the requirement is driven by a business goal, business users are not always sure about how the system should behave. It is necessary to try out the application before taking decision on its suitability. To this we can add the changing business goal arising out of change in the environment.

If all these points are added up, it becomes clear that requirements will change.

This has led to the realization that we need agile processes which works when requirements are constantly changing rather than spending time and energy on freezing requirement. As a result agile processes were born. The key principle behind any agile processes is to have a mechanism where the users can try out the application as it is being built and give feedback so that:

  1. Gap in understanding is reduced
  2. Sub-optimal solution can be improved
  3. Application can be realigned to any change in business goal

It is easier to adopt agile methodology in letter than in spirit. An iterative development process becomes ineffective, unless user feedback is used to change and fine tune the application behavior. This may involve introduction of new features, discarding features and reprioritization of features. It is not always easy to reorient an organization entrenched in waterfall development. Not only it is necessity to change mind-set of the people involved, it is also imperative to modify some the key management practices.

Funding: How Is the Project Sanctioned?
Normal process of budgeting involves calculating return on investment, which in turn, requires both investment and the return on it to be quantified. Even when the requirement is clearly defined, arriving at an accurate effort estimate is an error prone exercise. When requirement is expected to change during the life of the project, it becomes almost impossible to have an accurate estimate up front. This becomes a hazardous exercise and in practice the estimate gets tuned to make the ROI look good. Once sanctioned, the budget becomes frozen and it acts as a great disincentive to allow flexibility in changing requirement mid way. The way out of this situation is to have a method of incremental funding of project. Initially funds can be made available for first few iterations and this sanction can be based on a reasonable accurate estimation. The scope of the project and the fund required can get progressively fine tuned. With incremental funding, it also becomes easier to detect unviable project much earlier in the lifecycle.

Interaction: Do Stakeholders Trust Each Other?
Change in requirement involves rework and it implies discarding work already done. IT has to trust that a specific change suggested by business is needed and could not be specified earlier. Similarly, a feature may look simple from outside but may involve considerable amount of programming effort. Business has to trust the effort estimate made IT. Both IT and business has to believe that understanding is progressive and any gap in understanding is neither deliberate nor because of incompetence or carelessness of the other party. It can be achieved by having transparency from both side. IT needs to establish a method of estimation and make it transparent. Similarly, business needs to share the business plan and explain the need for any change. Any change will involve unplanned effort, more effort than what is feasible within a given time frame. Feature will have to be re-prioritized and and the revised plan should have joint ownership.

Defect: What Is a Defect?
Standard method of measuring defect is to:

  1. Define and freeze the requirement
  2. Derive test cases from the requirement
  3. Use the test cases to test the software
  4. Measure the number of test cases that has failed

Zero defect software means all the identified test cases are passed. This does not in any way indicate that the software meet the business needs. Since, test cases can only be identified for the explicitly documented requirement, we need to move beyond that and reorient how defect is defined. Therefore, regardless of presence of any explicit test case, a defect is when the application ...

  • ... crashes
  • ... behaves in an illogical manner
  • ... does not behave in the manner expected by the user

The responsibility of identifying and eliminating first and second category of defect is with developers. The third category can not be done by the developers alone and needs an active involvement of the user.

Success: How Is It Measured?
Traditionally, the goal of successful project management has been to the deliver the application on time, within budget and without defect. All project managers are brought up on the belief that the key to achieve this is to freeze requirement and minimize rework. However, when the planned application is a part of a major product or service release, the cost of failed application can be many time to cost of the application. Therefore it is necessary to shift the paradigm and measure success in terms of satisfying business needs. It can only be done by an agile methodology which interactively refines requirement by allowing the user to work with and feel the application on a regular basis. When we look at some of the most successful software company we find that it is better to deliver the right application even though it may be late, over budget or have some bugs than to deliver the wrong application within budget, on time and without defect. The likes of Microsoft, Apple and even Google has slipped on their promised delivery and the delivered software are also not free form problem. That has not stopped them from becoming the more successful than anybody else in what they choose to do.

Related Posts

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
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and containers together help companies achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of Dev...
True Story. Over the past few years, Fannie Mae transformed the way in which they delivered software. Deploys increased from 1,200/month to 15,000/month. At the same time, productivity increased by 28% while reducing costs by 30%. But, how did they do it? During the All Day DevOps conference, over 13,500 practitioners from around the world to learn from their peers in the industry. Barry Snyder, Senior Manager of DevOps at Fannie Mae, was one of 57 practitioners who shared his real world journe...
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Docker containers have brought great opportunities to shorten the deployment process through continuous integration and the delivery of applications and microservices. This applies equally to enterprise data centers as well as the cloud. In his session at 20th Cloud Expo, Jari Kolehmainen, founder and CTO of Kontena, will discuss solutions and benefits of a deeply integrated deployment pipeline using technologies such as container management platforms, Docker containers, and the drone.io Cl tool...
In his session at 19th Cloud Expo, Claude Remillard, Principal Program Manager in Developer Division at Microsoft, contrasted how his team used config as code and immutable patterns for continuous delivery of microservices and apps to the cloud. He showed how the immutable patterns helps developers do away with most of the complexity of config as code-enabling scenarios such as rollback, zero downtime upgrades with far greater simplicity. He also demoed building immutable pipelines in the cloud ...
Internet of @ThingsExpo, taking place June 6-8, 2017 at the Javits Center in New York City, New York, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @ThingsExpo New York Call for Papers is now open.
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed ...
As 2016 approaches its end, the time to prepare for the year ahead is now! Following our own advice, we sat down with three XebiaLabs thought leaders–Andrew Phillips, Tim Buntel, and TJ Randall–and asked what they think the future has in store for the DevOps world. In 2017, we’ll see a new wave of “next gen platform” projects focused on container orchestration frameworks such as Kubernetes, and re-tooled PaaS platforms such as OpenShift or Cloud Foundry. Acceptance of the need for a cross-machi...
When building DevOps or continuous delivery practices you can learn a great deal from others. What choices did they make, what practices did they put in place, and how did they connect the dots? At Sonatype, we pulled together a set of 21 reference architectures for folks building continuous delivery and DevOps practices using Docker. Why? After 3,000 DevOps professionals attended our webinar on "Continuous Integration using Docker" discussing just one reference architecture example, we recogn...
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...
The proper isolation of resources is essential for multi-tenant environments. The traditional approach to isolate resources is, however, rather heavyweight. In his session at 18th Cloud Expo, Igor Drobiazko, co-founder of elastic.io, drew upon his own experience with operating a Docker container-based infrastructure on a large scale and present a lightweight solution for resource isolation using microservices. He also discussed the implementation of microservices in data and application integrat...
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at Logz.io, will explore the value of Kibana 4 for log analysis and will give a real live, hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He will examine three use cases: IT operations, business intelligence, and security and compliance. This is a hands-on session that will require participants to bring their own laptops, and we will provide the rest.
"We're bringing out a new application monitoring system to the DevOps space. It manages large enterprise applications that are distributed throughout a node in many enterprises and we manage them as one collective," explained Kevin Barnes, President of eCube Systems, in this SYS-CON.tv interview at DevOps at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
As the race for the presidency heats up, IT leaders would do well to recall the famous catchphrase from Bill Clinton’s successful 1992 campaign against George H. W. Bush: “It’s the economy, stupid.” That catchphrase is important, because IT economics are important. Especially when it comes to cloud. Application performance management (APM) for the cloud may turn out to be as much about those economics as it is about customer experience.
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long developm...
Updating DevOps to the latest production data slows down your development cycle. Probably it is due to slow, inefficient conventional storage and associated copy data management practices. In his session at @DevOpsSummit at 20th Cloud Expo, Dhiraj Sehgal, in Product and Solution at Tintri, will talk about DevOps and cloud-focused storage to update hundreds of child VMs (different flavors) with updates from a master VM in minutes, saving hours or even days in each development cycle. He will also...
The 20th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held June 6-8, 2017, at the Javits Center in New York City, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit your speaking proposal ...
@DevOpsSummit taking place June 6-8, 2017 at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @DevOpsSummit at Cloud Expo New York Call for Papers is now open.