Welcome!

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.


Latest Stories
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
Only Adobe gives everyone - from emerging artists to global brands - everything they need to design and deliver exceptional digital experiences. Adobe Systems Incorporated develops, markets, and supports computer software products and technologies. The Company's products allow users to express and use information across all print and electronic media. The Company's Digital Media segment provides tools and solutions that enable individuals, small and medium businesses and enterprises to cre...
Hackers took three days to identify and exploit a known vulnerability in Equifax’s web applications. I will share new data that reveals why three days (at most) is the new normal for DevSecOps teams to move new business /security requirements from design into production. This session aims to enlighten DevOps teams, security and development professionals by sharing results from the 4th annual State of the Software Supply Chain Report -- a blend of public and proprietary data with expert researc...
Your job is mostly boring. Many of the IT operations tasks you perform on a day-to-day basis are repetitive and dull. Utilizing automation can improve your work life, automating away the drudgery and embracing the passion for technology that got you started in the first place. In this presentation, I'll talk about what automation is, and how to approach implementing it in the context of IT Operations. Ned will discuss keys to success in the long term and include practical real-world examples. Ge...
ClaySys Technologies is one of the leading application platform products in the ‘No-code' or ‘Metadata Driven' software business application development space. The company was founded to create a modern technology platform that addressed the core pain points related to the traditional software application development architecture. The founding team of ClaySys Technologies come from a legacy of creating and developing line of business software applications for large enterprise clients around the ...
Organize your corporate travel faster, at lower cost. Hotailors is a next-gen AI-powered travel platform. What is Hotailors? Hotailors is a platform for organising business travels that grants access to the best real-time offers from 2.000.000+ hotels and 700+ airlines in the whole world. Thanks to our solution you can plan, book & expense business trips in less than 5 minutes. Accordingly to your travel policy, budget limits and cashless for your employees. With our reporting, int...
Crosscode Panoptics Automated Enterprise Architecture Software. Application Discovery and Dependency Mapping. Automatically generate a powerful enterprise-wide map of your organization's IT assets down to the code level. Enterprise Impact Assessment. Automatically analyze the impact, to every asset in the enterprise down to the code level. Automated IT Governance Software. Create rules and alerts based on code level insights, including security issues, to automate governance. Enterpr...
DevOpsSUMMIT at CloudEXPO, to be held June 25-26, 2019 at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real results. Am...
The benefits of automated cloud deployments for speed, reliability and security are undeniable. The cornerstone of this approach, immutable deployment, promotes the idea of continuously rolling safe, stable images instead of trying to keep up with managing a fixed pool of virtual or physical machines. In this talk, we'll explore the immutable infrastructure pattern and how to use continuous deployment and continuous integration (CI/CD) process to build and manage server images for any platfo...
ICC is a computer systems integrator and server manufacturing company focused on developing products and product appliances to meet a wide range of computational needs for many industries. Their solutions provide benefits across many environments, such as datacenter deployment, HPC, workstations, storage networks and standalone server installations. ICC has been in business for over 23 years and their phenomenal range of clients include multinational corporations, universities, and small busines...
The current environment of Continuous Disruption requires companies to transform how they work and how they engineer their products. Transformations are notoriously hard to execute, yet many companies have succeeded. What can we learn from them? Can we produce a blueprint for a transformation? This presentation will cover several distinct approaches that companies take to achieve transformation. Each approach utilizes different levers and comes with its own advantages, tradeoffs, costs, risks, a...
This session describes how Professional Services organisations can deliver within Technology-as-a-Service (IaaS) constructs, in private and public enterprise cloud scenarios. See how professional services can be packaged and funded by IaaS cash flows, based upon consumption of technology services. Learn how significant, IT infrastructure transformations can be funded through OPEX spending models with multi-year As-a-Services based contracts. Understand how the automation of repeatable services c...
This sixteen (16) hour course provides an introduction to DevOps, the cultural and professional movement that stresses communication, collaboration, integration and automation in order to improve the flow of work between software developers and IT operations professionals. Improved workflows will result in an improved ability to design, develop, deploy and operate software and services faster.
Enterprises are universally struggling to understand where the new tools and methodologies of DevOps fit into their organizations, and are universally making the same mistakes. These mistakes are not unavoidable, and in fact, avoiding them gifts an organization with sustained competitive advantage, just like it did for Japanese Manufacturing Post WWII.
Most modern computer languages embed a lot of metadata in their application. We show how this goldmine of data from a runtime environment like production or staging can be used to increase profits. Adi conceptualized the Crosscode platform after spending over 25 years working for large enterprise companies like HP, Cisco, IBM, UHG and personally experiencing the challenges that prevent companies from quickly making changes to their technology, due to the complexity of their enterprise. An accomp...