How to apply agile and hybrid management in Owner’s Engineering to control RFIs, submittals, interfaces, decisions, WIP, lookahead, and implementation follow-up.
Check it out!
Applying agile and hybrid management in Owner’s Engineering means organizing technical oversight of the project so that RFIs, submittals, interfaces, deviations, pending items, and decisions can be handled quickly without weakening governance, traceability, or the owner’s technical authority. Owner’s Engineering continues to operate with formal approval criteria, evidence, records, and responsibilities; what changes is how the workflow is prioritized, prepared, and monitored.
During implementation, Owner’s Engineering operates in an environment of high operational variability. Documents arrive at different cadences, construction fronts create new constraints, suppliers request clarifications, incompatibilities appear in the field, and technical decisions may affect schedule, cost, quality, and commissioning. Handling everything only through weekly meetings and long lists of pending items tends to increase the time between problem identification and the required decision.
A hybrid approach combines formal governance where control must be preserved with adaptive practices in day-to-day flow: prioritization by criticality, visual management, work-in-progress limits, short-term planning, frequent review cycles, and rapid escalation. The objective is not to turn Owner’s Engineering into Scrum, but to make the owner’s technical representation more responsive without losing independence, control, or decision history.
Where Agility Fits in Owner’s Engineering
The broader concept of Owner’s Engineering involves technical representation of the owner’s interests throughout the project. Depending on the contract, it may include design review, oversight, interface management, submittal review, supplier follow-up, inspections, commissioning, documentation, and acceptance.
The need for adaptation arises because these demands do not arrive linearly. In the same week, the team may receive a design revision, an RFI blocking a work front, a deviation request, equipment documentation, a nonconformity, and a test package for approval.
The management method needs to distinguish three dimensions:
- technical criticality: risk to safety, performance, compliance, or asset integrity;
- time criticality: impact on the critical path, procurement, mobilization, testing, or work-front release;
- required authority: decision by the contractor, designer, OE, client, Technical Authority, or sponsor.
When these dimensions are explicit, the team stops working only on a first-in, first-out basis.
The study by Demir and Theis on Agile Design Management in construction projects is particularly useful as an adaptation reference: the authors identify that directly transferring Scrum from software to construction design is not appropriate and propose adapting iterative principles to the project’s actual structure. The same caution applies to Owner’s Engineering.
What Must Remain Formal
Agility does not reduce the obligation to document technical decisions. Some elements need to remain under explicit governance.
Approvals and Technical Authority
The team must know who can review, recommend, approve, or reject each type of document and decision. A visual board can show the flow, but it does not replace the responsibility matrix.
Requirements Management
Contractual, standards, safety, performance, and operational requirements must remain traceable. Relevant changes cannot occur merely through backlog reprioritization.
Change Control
Changes affecting the baseline, scope, cost, schedule, configuration, or requirements need to follow the applicable formal process. Agile flow may reduce analysis time; it does not eliminate Change Control.
Evidence and Acceptance
Inspections, tests, punch lists, quality documents, commissioning records, and acceptance need to remain linked to the criteria that demonstrate compliance.
Owner Independence
Owner’s Engineering should not confuse collaboration with transfer of responsibility. Working in an integrated manner with contractors and suppliers does not mean giving up the independence needed to technically assess deliverables, deviations, and risks.
How to Organize the Flow of RFIs, Submittals, and Decisions
Are RFIs, submittals, and decisions accumulating in queues while work fronts wait for responses?
The first practical gain of an adaptive approach is making the flow visible.
An operational structure can separate items into states such as:
- received and awaiting triage;
- awaiting input information;
- ready for analysis;
- under technical analysis;
- awaiting interface or specialist;
- awaiting owner decision;
- response issued;
- implementation verification;
- closed.
The representation should reflect the actual process. Creating generic columns such as “to do / doing / done” may hide the very queues that OE needs to control.
Classes of Service
Not every item should have the same priority. One possible classification includes:
| Class | Example | Expected treatment |
| critical blockage | RFI blocks the critical path or a safe condition | immediate response and escalation |
| needed-by date | submittal must be approved before procurement | milestone-driven priority |
| normal flow | document review with no immediate impact | controlled queue |
| improvement/opportunity | optimization with no critical risk or schedule impact | treatment according to capacity |
The important point is that priority should follow a known rule. Otherwise, every requester will try to classify their demand as urgent.
WIP and Aging: Control the Queue Before Controlling Delay
A team may appear busy and still complete very little. This happens when many documents and pending items are opened simultaneously and remain under analysis for long periods.
The Work in Progress — WIP shows how many items are active in each stage. The aging shows how long an item has remained open. Together, they help identify bottlenecks before the problem appears as consolidated schedule delay.
Examples of warning signs:
- twenty submittals under review by two specialists;
- RFIs awaiting an owner decision for several days;
- documents repeatedly returning due to missing information;
- open punch items without a closure owner;
- test package awaiting validation while the commissioning team is already mobilized.
Limiting WIP does not mean refusing work. It means preventing the organization from starting more analyses than it can complete with quality.
Integration with the Schedule and Rolling Wave Planning
Is technical oversight disconnected from the schedule, interfaces, and needed-by dates for procurement and field activities?
The operational board does not replace the integrated schedule. Owner’s Engineering needs to connect each demand to the date by which its response is needed for the project.
The Rolling Wave Planning is especially useful because it allows the near-term horizon to be detailed with greater precision while maintaining visibility of future packages.
For OE, a short-term wave may include:
- submittals that need approval;
- RFIs blocking work fronts;
- planned inspections;
- hold points and witness points;
- documents needed for testing;
- procurement releases;
- interface decisions;
- punch items conditioning energization or acceptance.
The question shifts from “what is open?” to “what needs to be resolved before the next work front?”.
Interface Management as a Technical Backlog
Interfaces are a recurring source of delay because they are often scattered across meeting minutes, emails, drawings, and separate lists.
The Interface Management in Engineering Projects provides the formal structure for identifying responsibilities, connection points, and changes. The adaptive layer can turn open interfaces into a prioritizable workflow.
An interface item should record, where applicable:
- systems or disciplines involved;
- interface owner;
- party responsible for input information;
- required decision;
- needed-by date;
- potential impact;
- associated document or ICD;
- status;
- closure evidence.
The backlog does not replace the interface matrix. It operationalizes the work needed to close it.
Not Every Interface Requires Permanent Collaboration
Owner’s Engineering needs to integrate designers, contractors, suppliers, operations, and the owner, but integration does not mean placing everyone in intensive collaboration all the time. In large projects, this design creates excessive meetings, specialist overload, and decisions that depend on too many people.
Team Topologies, developed for software and technology organizations, distinguishes interaction modes according to the nature of the boundary: close collaboration for discovery, consumption of a well-defined capability through a stable interface, and temporary facilitation to develop capability or remove impediments. Construction team archetypes should not be transplanted literally, but the logic of interaction modes is useful for Owner’s Engineering.
A new interface among an automation system, process equipment, and electrical systems may require frequent workshops until protocol, signals, power supply, interlocks, and responsibilities are stabilized. After that, interaction should migrate to interface documents, vendor data, submittals, and controlled acceptance criteria. Maintaining the same level of collaboration after the boundary is defined consumes capacity without necessarily reducing risk.
There are also facilitation situations: the Owner’s Engineer can bring specialists together, structure a matrix, clarify criteria, or organize a decision so the parties can resolve a gap. This differs from permanently assuming the contractor’s operational responsibility.
Good interface governance, therefore, should record not only who interacts with whombut also what intensity of interaction is needed now and what condition allows that intensity to be reduced. This change of mode helps preserve owner independence and specialist capacity throughout the project.
Cadences for Coordination and Decision-Making
Hybrid management uses cadences proportional to the type of decision.
Operational Synchronization
It may occur daily or several times per week during critical periods. The focus is impediments, priority, and flow, not a complete status report.
Weekly Integration Meeting
It consolidates lookahead, interfaces, critical RFIs, submittals, constraints, and short-term risks.
Governance Meeting
It addresses relevant changes, baseline deviations, critical risks, owner decisions, and contractual matters. Its frequency may be biweekly or monthly, or it may occur by exception.
Gate or Milestone Review
Before energization, start-up, commissioning, handover, or transition between stages, the team verifies maturity and objective evidence.
Separating these cadences prevents an operational meeting from becoming a contractual decision forum and prevents the executive committee from being consumed by details that should have been resolved at the technical level.
Useful Metrics for Hybrid Owner’s Engineering
Flow metrics can complement traditional indicators.
| Metric | What it shows | Example of OE application |
| throughput | items completed per period | RFIs answered per week |
| cycle time | time between the start and completion of analysis | technical submittal-review time |
| lead time | total time from request to response | RFI from receipt to closure |
| WIP | simultaneously active items | documents under review |
| aging | age of open items | interfaces not yet closed |
| rework rate | items returning to the flow | resubmitted submittals |
These metrics need to be interpreted critically. Answering twenty simple RFIs is not necessarily better than resolving three interfaces that release the critical path. Quantity should be combined with impact and quality.
How to Handle Changes without Losing Agility
Implementation inevitably produces changes. The problem is not the existence of change, but the inability to distinguish clarification, correction, optimization, and baseline change.
A mature triage can distinguish:
- clarification without a requirement change;
- correction to meet an existing requirement;
- solution change within the defined technical authority;
- change affecting controlled configuration;
- contractual or baseline change;
- temporary deviation requiring approval and subsequent regularization.
Simple items can follow a fast track. Higher-impact changes require technical, schedule, cost, risk, and interface analysis, plus formal approval.
Agility lies in routing each request quickly to the correct level of governance, not in eliminating governance levels.
Application in Commissioning and Acceptance
Commissioning concentrates a high volume of pending items, tests, documents, and decisions. It is an environment where visual management and prioritization can create significant value.
OE can organize the flow by systems and subsystems, connecting:
- test prerequisites;
- approved documentation;
- completed inspections;
- punch list;
- utility availability;
- required team and supplier;
- test procedure;
- result evidence;
- acceptance criteria.
An item should advance only when its essential constraints have been removed. This discipline brings short-term planning closer to the logic of Definition of Ready, without requiring formal adoption of Scrum.
How to Implement the Approach
- Map the actual flows. Identify how RFIs, submittals, decisions, inspections, and pending items enter and leave the process.
- Define classes and priorities. Establish technical and time criteria, not merely declared urgency.
- Separate flow governance. Record which items require Change Control, specific authority, or formal evidence.
- Create visual management. Represent actual states, queues, and owners.
- Establish WIP and aging. Control excessive work and aging items.
- Integrate with the schedule. Link requests to needed-by dates and milestones.
- Define cadences. Separate operational synchronization, integration, and governance.
- Measure and review. Adjust the process based on bottlenecks, rework, and decision times.
Common Errors
Turning OE into a Task Center
Owner’s Engineering exists to technically protect the owner’s interests. Managing cards without critical analysis diminishes its role.
Responding Quickly without Closing Interfaces
An isolated response may resolve an RFI and create an incompatibility in another discipline. Speed needs to be systemic.
Using the Backlog as a Substitute for Documentation
The backlog controls work; formal documents record requirements, decisions, and configuration.
Treating Every Pending Item as Top Priority
Without classes of service, the flow loses predictability and real urgencies stop being visible.
Measuring Only Quantity
Throughput without quality or criticality can encourage superficial item closure.
Final Considerations
Agile and hybrid management makes Owner’s Engineering more efficient when applied to the flow of information, analysis, and decision-making, not when it attempts to make flexible what needs to remain formal.
The owner continues to need governance, technical authority, evidence, traceability, and change control. Adaptive practices help reduce queues, anticipate constraints, prioritize what actually threatens the project, and shorten the time between problem and decision.
The combination is particularly suitable for multidisciplinary projects, brownfield environments, implementation, commissioning, and contexts with a high volume of interfaces. In these situations, Owner’s Engineering can operate more responsively without giving up the independence that justifies its role.
Do you need to structure owner governance, responsibilities, and decision criteria before increasing flow speed?
Learn about A3A Engenharia’s Ongoing Engineering Consulting Services
Technical References
[1] PROJECT MANAGEMENT INSTITUTE. Agile Practice Guide — Second Edition. Newtown Square: PMI, 2026. Available at: https://www.pmi.org/standards/agile.
[2] DEMIR, S. T.; THEIS, P. Agile Design Management — The Application of Scrum in the Design Phase of Construction Projects. In: Proceedings of the 24th Annual Conference of the International Group for Lean Construction. Boston, 2016. Available at: https://iglc.net/.
[3] PROJECT MANAGEMENT INSTITUTE. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Eighth Edition. Newtown Square: PMI, 2025. Available at: https://www.pmi.org/standards/pmbok.
[4] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 21502:2020 — Project, programme and portfolio management — Guidance on project management. Geneva: ISO, 2020. Available at: https://www.iso.org/standard/74947.html.
[5] SKELTON, Matthew; PAIS, Manuel. Team Topologies: Organizing Business and Technology Teams for Fast Flow. Portland: IT Revolution Press, 2019.
Frequently Asked Questions
Yes. Adaptive practices are useful for RFIs, submittals, interfaces, pending items, short-term planning, and decision cycles. Approvals, requirements, changes, and formal evidence remain under technical governance.
No. Scrum is a specific framework. Owner’s Engineering can use visual management, prioritization, WIP, aging, Rolling Wave, and short cadences without adopting Scrum in full.
Priority should consider technical criticality, schedule impact, number of dependent interfaces, needed-by date, risk, and required authority, not merely order of arrival.
The interface matrix formally records connection points and responsibilities. The backlog can operationalize actions needed to close interfaces, but it does not replace the formal record.
Throughput, cycle time, lead time, WIP, aging, and rework rate can reveal queues and response times. They should be combined with criticality, quality, and project impact.
By quickly classifying each request according to its nature and routing relevant changes for impact analysis and formal approval, while clarifications and simple corrections follow a faster flow.
Complementary Technical Materials
Related Solutions
Related Services
Main Content on the Topic
- Agile and Hybrid Management of Engineering Projects
- Project Planning with Rolling Wave Planning
- Owner’s Engineering: Technical Governance for Engineering Construction
