Click here to close now.


Microservices Expo Authors: Liz McMillan, Elizabeth White, Pat Romanski, Yeshim Deniz, Lori MacVittie

Related Topics: Microservices Expo, Java IoT, Industrial IoT, ColdFusion, Microsoft Cloud, IoT User Interface

Microservices Expo: Article

Finding the Right Blend: Sometimes Pure Agile Isn’t the Way to Go

Agile project managers need to remind their stakeholders & teams that agility is the very opposite of rigidity & inflexibility

Only a fraction of organizations will migrate to Agile methods completely and for all projects. The reality is, many types of projects are not well suited for Agile approaches for a variety of reasons. Some organizations run multiple projects across many departments and corporate entities, many of which may not have the inclination or resources to manage in an Agile manner. Others have made significant investments in traditional or proprietary methodologies and are not prepared to simply abandon them. Further, many companies are global, with development resources located around the world, in different time zones, with varying local corporate cultures and working styles.

For all of these reasons, Agile project managers need to be prepared to work in cooperation with non-Agile project managers, teams that employ traditional methods, and organizations that have resources scattered around the globe.

How the Blended Approach Works
Agile adoption doesn't need to be an all-or-nothing, either-or scenario. The very incremental, iterative concepts that Agile project managers (PMs) apply to their projects can also be applied to Agile adoption. For instance, teams that are migrating to Agile methods can adopt certain elements, such as user stories in place of requirements definition, and incremental, rather than "big-bang" planning, as ways to ease into the Agile migration. While these incremental methods will not offer all of the advantages of the total Agile environment, they have the advantage of being less disruptive to existing approaches and offer "proof points" to reassure managers and teams that these methods can deliver the expected results.

Where Agile Fits
There are a number of areas where the Agile method can fit into a non-Agile project. Remember that the success of Agile methods revolves around the customer and the team. It is really about collaborating on all levels of the project. When they work in concert with one another, the project deliverables are much easier to complete. In your Waterfall or non-Agile project, look for places where you can easily adopt the top four key Agile methods:

  • Iterative delivery of customer value
  • Early and frequent customer feedback
  • Working in highly collaborative, multifunctional teams
  • Continuous inspection and adaptation

The preceding methods are based on the Agile Manifesto's value statement. The focus of the Manifesto is on the following:

  • Individuals and interactions
  • Working software
  • Customer collaboration
  • Responding to change

Take a look at your Waterfall project and identify where you can leverage the power of customer involvement. Typically, you will be able to modify your Communication Plan, Stakeholder Management Plan and Risk Management Plans with an Agile approach. This proactive approach will allow you to ensure that impediments, which delay delivery of product, are managed and eliminated.

Proof Points
Because Agile methods focus on the customer, team, iterative delivery, and continuous adaptation or change, it is recommended that Waterfall-focused organizations begin to test the waters of Agile by using "proof points." Proof points are areas within a Waterfall project where you can "prove" the power of Agile elements. Not only will this help move the project forward, but it also highlights the value of the Agile methodology and helps an organization transition from using 100% Waterfall approaches to Agile methods.

Good opportunities to show proof points are within the planning, requirements and team communications areas of a project.

  • Start by approaching the work on a project by not only planning the entire project, but also planning the specifics of how a certain work package can be delivered.
  • Implement the practice of user stories to define the requirements differently.
  • Leverage the power of daily stand-up meetings (five to 10 minute meetings in which everyone stands to keep things brief). This allows the project team members the opportunity to share work progress and possible obstacles that may lead to challenges in completing the work package.
  • Use daily stand-up meetings to empower the team members to have open communication, while supporting each other to eliminate impediments.

These areas begin to shift an organization's mindset on how projects can be delivered differently. They offer the opportunity for organizations to embrace Agile while in the comfort of traditional project management.

Not One Size Fits All
It's important to recognize that Agile project management is not a one-size-fits-all philosophy. In fact, a foundational concept of Agile is the idea that every project should be considered as a unique entity, and PMs must make determinations for each unique effort regarding the amount of documentation, process rigor and management oversight required. This adaptive approach to project management also enables the ability to interweave elements of traditional project management into an Agile approach.

There's no reason why an Agile approach cannot have a Gantt chart if managers or stakeholders request one - as long as it's made clear that the chart will only schedule out as far as the iteration or release currently being built. The knowledge areas, process areas and artifacts of traditional project management are still applicable in an Agile environment, as long as they are adapted to the core concepts of incremental, iterative design and change readiness. Agile methods are called "adaptive" for a reason. Agile project managers need to remind their stakeholders and teams that agility is the very opposite of rigidity and inflexibility. Both the substantive and human elements of change must be considered, and the transition should be made to an Agile environment that is appropriate to the culture and practices of an organization.

More Stories By Nancy Y. Nee

Nancy Y. Nee, PMP, CBAP, CSM, Vice President, Global Product Strategy, ESI International, guides clients in the development and implementation of learning programs customized to their specific needs. Her solutions reflect the insight of almost two decades of PM and BA experience in healthcare, information technology, financial services and energy.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@MicroservicesExpo Stories
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Between the compelling mockups and specs produced by analysts, and resulting applications built by developers, there exists a gulf where projects fail, costs spiral, and applications disappoint. Methodologies like Agile attempt to address this with intensified communication, with partial success but many limitations. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, will present a revolutionary model enabled by new technologies. Learn how busine...
With containerization using Docker, the orchestration of containers using Kubernetes, the self-service model for provisioning your projects and applications and the workflows we built in OpenShift is the best in class Platform as a Service that enables introducing DevOps into your organization with ease. In his session at DevOps Summit, Veer Muchandi, PaaS evangelist with RedHat, will provide a deep dive overview of OpenShift v3 and demonstrate how it helps with DevOps.
JFrog has announced a powerful technology for managing software packages from development into production. JFrog Artifactory 4 represents disruptive innovation in its groundbreaking ability to help development and DevOps teams deliver increasingly complex solutions on ever-shorter deadlines across multiple platforms JFrog Artifactory 4 establishes a new category – the Universal Artifact Repository – that reflects JFrog's unique commitment to enable faster software releases through the first pla...
SYS-CON Events announced today that Dyn, the worldwide leader in Internet Performance, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Dyn is a cloud-based Internet Performance company. Dyn helps companies monitor, control, and optimize online infrastructure for an exceptional end-user experience. Through a world-class network and unrivaled, objective intelligence into Internet condit...
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attende...
The APN DevOps Competency highlights APN Partners who demonstrate deep capabilities delivering continuous integration, continuous delivery, and configuration management. They help customers transform their business to be more efficient and agile by leveraging the AWS platform and DevOps principles.
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at @DevOpsSummit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
IT data is typically silo'd by the various tools in place. Unifying all the log, metric and event data in one analytics platform stops finger pointing and provides the end-to-end correlation. Logs, metrics and custom event data can be joined to tell the holistic story of your software and operations. For example, users can correlate code deploys to system performance to application error codes.
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
Internet of Things (IoT) will be a hybrid ecosystem of diverse devices and sensors collaborating with operational and enterprise systems to create the next big application. In their session at @ThingsExpo, Bramh Gupta, founder and CEO of, and Fred Yatzeck, principal architect leading product development at, discussed how choosing the right middleware and integration strategy from the get-go will enable IoT solution developers to adapt and grow with the industry, while at th...
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at, and Tomer Levy, co-founder and CEO of, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the archi...
“All our customers are looking at the cloud ecosystem as an important part of their overall product strategy. Some see it evolve as a multi-cloud / hybrid cloud strategy, while others are embracing all forms of cloud offerings like PaaS, IaaS and SaaS in their solutions,” noted Suhas Joshi, Vice President – Technology, at Harbinger Group, in this exclusive Q&A with Cloud Expo Conference Chair Roger Strukhoff.
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.
Saviynt Inc. has announced the availability of the next release of Saviynt for AWS. The comprehensive security and compliance solution provides a Command-and-Control center to gain visibility into risks in AWS, enforce real-time protection of critical workloads as well as data and automate access life-cycle governance. The solution enables AWS customers to meet their compliance mandates such as ITAR, SOX, PCI, etc. by including an extensive risk and controls library to detect known threats and b...
Clearly the way forward is to move to cloud be it bare metal, VMs or containers. One aspect of the current public clouds that is slowing this cloud migration is cloud lock-in. Every cloud vendor is trying to make it very difficult to move out once a customer has chosen their cloud. In his session at 17th Cloud Expo, Naveen Nimmu, CEO of Clouber, Inc., will advocate that making the inter-cloud migration as simple as changing airlines would help the entire industry to quickly adopt the cloud wit...
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction....