Microservices Expo Authors: Pat Romanski, Liz McMillan, Kareen Kircher, Andreas Grabner, Roger Strukhoff

Related Topics: Java IoT, Microservices Expo, IoT User Interface

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

@MicroservicesExpo Stories
SYS-CON Events announced today that Tintri Inc., a leading producer of VM-aware storage (VAS) for virtualization and cloud environments, will present at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Tintri VM-aware storage is the simplest for virtualized applications and cloud. Organizations including GE, Toyota, United Healthcare, NASA and 6 of the Fortune 15 have said “No to LUNs.” With Tintri they manag...
SYS-CON Events announced today that eCube Systems, the leading provider of modern development tools and best practices for Continuous Integration on OpenVMS, will exhibit at SYS-CON's @DevOpsSummit at Cloud Expo New York, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. eCube Systems offers a family of middleware products and development tools that maximize return on technology investment by leveraging existing technical equity to meet evolving business needs. ...
All clouds are not equal. To succeed in a DevOps context, organizations should plan to develop/deploy apps across a choice of on-premise and public clouds simultaneously depending on the business needs. This is where the concept of the Lean Cloud comes in - resting on the idea that you often need to relocate your app modules over their life cycles for both innovation and operational efficiency in the cloud. In his session at @DevOpsSummit at19th Cloud Expo, Valentin (Val) Bercovici, CTO of So...
Apache Hadoop is a key technology for gaining business insights from your Big Data, but the penetration into enterprises is shockingly low. In fact, Apache Hadoop and Big Data proponents recognize that this technology has not yet achieved its game-changing business potential. In his session at 19th Cloud Expo, John Mertic, director of program management for ODPi at The Linux Foundation, will explain why this is, how we can work together as an open data community to increase adoption, and the i...
operations aren’t merging to become one discipline. Nor is operations simply going away. Rather, DevOps is leading software development and operations – together with other practices such as security – to collaborate and coexist with less overhead and conflict than in the past. In his session at @DevOpsSummit at 19th Cloud Expo, Gordon Haff, Red Hat Technology Evangelist, will discuss what modern operational practices look like in a world in which applications are more loosely coupled, are deve...
DevOps is a term that comes full of controversy. A lot of people are on the bandwagon, while others are waiting for the term to jump the shark, and eventually go back to business as usual. Regardless of where you are along the specturm of loving or hating the term DevOps, one thing is certain. More and more people are using it to describe a system administrator who uses scripts, or tools like, Chef, Puppet or Ansible, in order to provision infrastructure. There is also usually an expectation of...
DevOps is speeding towards the IT world like a freight train and the hype around it is deafening. There is no reason to be afraid of this change as it is the natural reaction to the agile movement that revolutionized development just a few years ago. By definition, DevOps is the natural alignment of IT performance to business profitability. The relevance of this has yet to be quantified but it has been suggested that the route to the CEO’s chair will come from the IT leaders that successfully ma...
As we enter the final week before the 19th International Cloud Expo | @ThingsExpo in Santa Clara, CA, it's time for me to reflect on six big topics that will be important during the show. Hybrid Cloud This general-purpose term seems to provide a comfort zone for many enterprise IT managers. It sounds reassuring to be able to work with one of the major public-cloud providers like AWS or Microsoft Azure while still maintaining an on-site presence.
The best way to leverage your Cloud Expo presence as a sponsor and exhibitor is to plan your news announcements around our events. The press covering Cloud Expo and @ThingsExpo will have access to these releases and will amplify your news announcements. More than two dozen Cloud companies either set deals at our shows or have announced their mergers and acquisitions at Cloud Expo. Product announcements during our show provide your company with the most reach through our targeted audiences.
This is a no-hype, pragmatic post about why I think you should consider architecting your next project the way SOA and/or microservices suggest. No matter if it’s a greenfield approach or if you’re in dire need of refactoring. Please note: considering still keeps open the option of not taking that approach. After reading this, you will have a better idea about whether building multiple small components instead of a single, large component makes sense for your project. This post assumes that you...
As software becomes more and more complex, we, as software developers, have been splitting up our code into smaller and smaller components. This is also true for the environment in which we run our code: going from bare metal, to VMs to the modern-day Cloud Native world of containers, schedulers and microservices. While we have figured out how to run containerized applications in the cloud using schedulers, we've yet to come up with a good solution to bridge the gap between getting your conta...
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 @...
DevOps theory promotes a culture of continuous improvement built on collaboration, empowerment, systems thinking, and feedback loops. But how do you collaborate effectively across the traditional silos? How can you make decisions without system-wide visibility? How can you see the whole system when it is spread across teams and locations? How do you close feedback loops across teams and activities delivering complex multi-tier, cloud, container, serverless, and/or API-based services?
SYS-CON Events announced today that SoftNet Solutions will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. SoftNet Solutions specializes in Enterprise Solutions for Hadoop and Big Data. It offers customers the most open, robust, and value-conscious portfolio of solutions, services, and tools for the shortest route to success with Big Data. The unique differentiator is the ability to architect and ...
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 session at @DevOpsSummit 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will show how customers are able to achieve a level of transparency that enables everyon...
Today every business relies on software to drive the innovation necessary for a competitive edge in the Application Economy. This is why collaboration between development and operations, or DevOps, has become IT’s number one priority. Whether you are in Dev or Ops, understanding how to implement a DevOps strategy can deliver faster development cycles, improved software quality, reduced deployment times and overall better experiences for your customers.
At its core DevOps is all about collaboration. The lines of communication must be opened and it takes some effort to ensure that they stay that way. It’s easy to pay lip service to trends and talk about implementing new methodologies, but without action, real benefits cannot be realized. Success requires planning, advocates empowered to effect change, and, of course, the right tooling. To bring about a cultural shift it’s important to share challenges. In simple terms, ensuring that everyone k...
What do dependency resolution, situational awareness, and superheroes have in common? Meet Chris Corriere, a DevOps/Software Engineer at Autotrader, speaking on creative ways to maximize usage of all of the above. Mark Miller, Community Advocate and senior storyteller at Sonatype, caught up with Chris to learn more about what his team is up to.
SYS-CON Events announced today that Super Micro Computer, Inc., a global leader in Embedded and IoT solutions, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 7-9, 2017, at the Javits Center in New York City, NY. Supermicro (NASDAQ: SMCI), the leading innovator in high-performance, high-efficiency server technology, is a premier provider of advanced server Building Block Solutions® for Data Center, Cloud Computing, Enterprise IT, Hadoop/Big Data, HPC and ...
@DevOpsSummit has been named the ‘Top DevOps Influencer' by iTrend. iTrend processes millions of conversations, tweets, interactions, news articles, press releases, blog posts - and extract meaning form them and analyzes mobile and desktop software platforms used to communicate, various metadata (such as geo location), and automation tools. In overall placement, @DevOpsSummit ranked as the number one ‘DevOps Influencer' followed by @CloudExpo at third, and @MicroservicesE at 24th.