by Sal Chavez
The term “standard operating procedure” was first recorded in the mid-20th century. According to Britannica.com, a standard operating procedure – also called standing operating procedure – is “a set of written guidelines or instructions for completing a routine task designed to increase performance, improve efficiency, and ensure quality through systemic homogenization.” An Army.mil article emphasizes the benefits of SOPs, which “can vastly reduce workload by garnering efficiency in operations.” The Army also provides guidance for developing effective SOPs, where “standardization provides common, tested procedures for executing specific tasks whether maintenance, administrative, operational or many others following the best practices of the specific unit and mission."
SOPs are meant to guide step-by-step behaviors so that individuals and teams follow the best practices of those who came before them. However, just as the software development world has moved from a Waterfall-first approach to more Agile methodologies, it may be time to rethink SOPs, as well. In an environment where significant software development program costs are escalating due to rigid change control procedures, some dev teams are aiming to replace their long, detailed SOPs with shorter “Desk Guide” volumes. Desk Guides document best practice approaches, rather than detailed steps. A move to Desk Guides to implement Agile methodologies may be the answer to reducing time to production and lowering costs.
A move to Desk Guides to implement Agile methodologies may be the answer to reducing time to production and lowering costs.
As one example, we are leading one defense client’s system engineering organization through a conversion of their traditional Waterfall-centric SOPs to Desk Guides for implementing Agile methodologies from the SE perspective. The objective is to provide information and guidance that delivers the promise and flexibility of the Agile methodology.
SOPs tended to be specific to Waterfall process groups, requiring a separate SOP for each. Desk Guides generally keep program and project requirements to a minimum, so they are useful to a broader set of groups.
SOPs tended to be specific to Waterfall process groups, requiring a separate SOP for each. Desk Guides generally keep program and project requirements to a minimum, so they are useful to a broader set of groups.
The challenge, of course, is balancing fiduciary responsibility and timely delivery of a product. Reducing the number of requirements (and SOP documents) in favor of implementing an Agile methodology can increase a federal agency’s ability to introduce change – and can increase the risk of unintended project scope growth. Desk Guides provide quick references designed to encourage best practices for managing changes and deliverables in an Agile project.
REFERENCES
Britannica | SOP Definition | https://www.britannica.com/topic/standard-operating-procedure
U.S. Army | Standard Operating Procedures: This is the way we’ve always done it. | https://www.army.mil/article/238732/standard_operating_procedures_this_is_the_way_weve_always_done_it