Most Read This Week
From the Blogosphere
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
By: John Rauser
Dec. 14, 2017 04:00 PM
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
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
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:
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
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
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.
Reader Feedback: Page 1 of 1
Subscribe to the World's Most Powerful Newsletters
Today's Top Reads