Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Elizabeth White, Mehdi Daoudi, Yeshim Deniz

Related Topics: @DevOpsSummit, Microservices Expo, Containers Expo Blog

@DevOpsSummit: Blog Post

Applying Agile Approaches to Traditional Processes | @DevOpsSummit #Scrum #Agile #DevOps

Agile approaches are valuable in controlling uncertainty because they constrain the complexity that stems from it

Beyond Software Development: Applying Agile Approaches to Traditional Processes

While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted.

Agile approaches are valuable in controlling uncertainty because they constrain the complexity that stems from it. For example, iterative cycles place a limit on how far planning can go and how much work can be taken on at one time. What if those same constraints could help control a different kind of complexity -- the type that undermines classic plan-driven projects?

Followers of Lean production are familiar with the idea that limiting work in progress ("WIP") allows a system to operate with a steady flow of work, thereby increasing its overall efficiency and effectiveness. The goals of Lean are galvanized further by Agile practices, because any technique that limits WIP should prove to be valuable, especially in situations where the sheer magnitude of work in progress is the primary source of complexity.

The work of Simon Orrell pays testament to that. His clients' use of Scrum in major engineering projects has been effective in managing complexity by controlling and limiting WIP. Embedded inside a traditionally managed waterfall project, practices such as multi-disciplinary teams, iterative cycles and backlog grooming provide natural constraints on WIP and a framework in which to prioritize and work collaboratively.

While plan-driven projects may have little margin for error or tolerance for change, that does not place them at odds with Agile, which provides a useful set of tools for managing problems in the predictive domain, though perhaps unexpectedly considering their origins.

Agile in Software Development
Software development has confounded traditional planning and management systems due to the high level of ambiguity involved in the work. Uncertainty abounds for many reasons:

  1. We have incomplete information about markets, customers and requirements.
  2. We need to accommodate constantly changing needs and desires.
  3. The product's design is difficult to nail down.
  4. We're not sure about the best software architecture.
  5. We don't know how long it will to take to build.

Without a method to manage the ambiguity and uncertainty, waste pervades. Many of us have lived through software projects that "finish," only to find that the result is not even what the customer asked for.

Agile approaches have been very effective because they break up work and provide a structure within which it is acceptable to fail. In software, the emphasis is on using practices like iterative cycles, and continuous feedback loops serve to control and constrain risks from ambiguity - if a feature was not executed correctly, we can't get too far along

Project Management in Engineering
Traditional engineering projects, on the other hand, have few of the same uncertainty risks that software development projects face:

  1. We have very precise understanding of the finished product.
  2. The customer knows exactly what they need.
  3. Designs are based largely on precedent.
  4. We can create very clear architecture plans to build from.
  5. We know how long it should take to build.

Rather, many of the challenges in engineering projects stem from the sheer magnitude of the work being performed. The problem here is not the planning, it is the coordinating, i.e., ensuring that the work from each stage meshes with the work in the next. The size and complexity of the project means that there are a vast number of dependant tasks that need to be performed across a very broad range of activities.

Work is typically assigned by a project manager to highly specialized teams, and each of those will kick off their own set of tasks. A large amount of work across many problem domains is therefore started at once, and it can remain open indefinitely. Teams may not be able to share information or resources, and lack the benefit of system level visibility to make decisions and use information and resources effectively.

Cascading failure is also a huge risk. Knowing every detail about what work needs to be performed does not help us recover when something fails. In other words, there is an extreme problem with WIP overload. Some of the symptoms include:

  1. Very long running tasks
  2. Large number of handoffs
  3. Domino effect when dependencies are misaligned
  4. Team silos and lack of knowledge integration
  5. Difficulty focusing on what is important

The fifth problem is probably the most damning. We've all been in this situation: Faced with such a staggering amount of work, how do you determine what needs to be done right now? How do you prioritize a work item when everyone is telling you that their work item is urgent? And how do you manage your work effectively when you don't have insight into what's happening at the system level? This is where Agile shines.

Applying Agile in Engineering Projects
Orrell's success in applying Scrum to execute the engineering phase for a natural gas processing plant demonstrated the effectiveness in using Agile to control WIP complexity. This played out in several ways:

1. With a multidisciplinary, matrixed team of operational specialists, WIP can be managed by consensus. Team members are provided with the opportunity to understand and manage their work at a system level, not at just a functional level. Cross-functional knowledge could be integrated and shared.

2. Scrum ceremonies such as daily stand-up, sprint planning and retrospectives provide continuous insight into how the project is performing and how the teams could make better decisions about what to work on. Progress could be determined empirically and objectively. Teams were able to truly know the state of their work with each iteration. With this information, focus could be maintained on understanding and completing high-priority items in the backlog.

3. Team members pulled tasks from a backlog groomed and refined by the project manager and the cross-discipline team. Backlog items were created out of traditional project artifacts -- schedule progress, roadblocks to deliverables in the schedule, risks from the risk log, process requirements, infrastructure requirements and so on. Techniques such as mind-mapping were used to discover blockers and knowledge gaps so the team could work together to determine how to solve them.

4. The product increment for each sprint included iterating on the 3D model of the plant that was to be built, and completing specific deliverables like engineering drawings, procurement contracts and purchase orders needed for construction to begin.

The result was a new way of working that allows for delivery ahead of schedule, under budget and with less stress for everyone involved.

By building out a backlog from project artifacts and using a multidisciplinary, iterative approach to prioritization, a natural structure for controlling WIP emerges and the complexity of large projects can be reduced.

Moving Towards Co-existence
As we head towards a world where predictive project management techniques and Agile approaches are used together, there will be several key obstacles to overcome:

1. When Agile teams grow and become distributed they need to adopt their own artifact-based collaboration tools to manage their work. In doing so they will need to find ways to integrate their tools with existing processes and make their work visible to all stakeholders in the organization. Without these tools and integrations, work will get bogged down with meetings, spreadsheets, documents and manual processes.

2. Similarly, as the methodology is scaled out to include all phases of a project, there will be cultural and organizational issues to deal with - the same issues as when scaling Agile in software organizations: increased complexity, reduced visibility and resistance to the agile mindset, and so on.

3. Probably the largest obstacle will be convincing people to use Agile approaches in the first place. Getting the buy-in at the executive level to manage the delivery of expensive and significant projects like factories and plants in new ways could prove to be difficult.

Nevertheless, having seen that Agile approaches such as Scrum have value not just in reducing uncertainty from the unknown, but also in coping with unmanageability from too many knowns, we need to continue moving forward with understanding how to integrate plan-driven projects with Agile practices in the world outside software.

As Orrell noted in Agile Coaching: Wisdom from Practitioners, "the success of organizations, their products, and projects lies in their teams and how they work together." To that end, the coexistence of plan-based and Agile projects offers a wealth of new opportunities to improve and evolve our organizations.

More Stories By John Rauser

John Rauser is the IT Manager at Tasktop Technologies, a global enterprise software company. He also serves as VP Operations at the board of the Project Management Institute - Canadian West Coast Chapter, providing leadership and expertise on technology issues. He has a passion for discussing the business impacts of technology and analyzing strategies for managing IT.

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.


Microservices Articles
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
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...
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound e...
If your cloud deployment is on AWS with predictable workloads, Reserved Instances (RIs) can provide your business substantial savings compared to pay-as-you-go, on-demand services alone. Continuous monitoring of cloud usage and active management of Elastic Compute Cloud (EC2), Relational Database Service (RDS) and ElastiCache through RIs will optimize performance. Learn how you can purchase and apply the right Reserved Instances for optimum utilization and increased ROI.
TCP (Transmission Control Protocol) is a common and reliable transmission protocol on the Internet. TCP was introduced in the 70s by Stanford University for US Defense to establish connectivity between distributed systems to maintain a backup of defense information. At the time, TCP was introduced to communicate amongst a selected set of devices for a smaller dataset over shorter distances. As the Internet evolved, however, the number of applications and users, and the types of data accessed and...
Consumer-driven contracts are an essential part of a mature microservice testing portfolio enabling independent service deployments. In this presentation we'll provide an overview of the tools, patterns and pain points we've seen when implementing contract testing in large development organizations.
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 ...
You have great SaaS business app ideas. You want to turn your idea quickly into a functional and engaging proof of concept. You need to be able to modify it to meet customers' needs, and you need to deliver a complete and secure SaaS application. How could you achieve all the above and yet avoid unforeseen IT requirements that add unnecessary cost and complexity? You also want your app to be responsive in any device at any time. In his session at 19th Cloud Expo, Mark Allen, General Manager of...