{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T04:13:16Z","timestamp":1750219996529,"version":"3.41.0"},"reference-count":28,"publisher":"Association for Computing Machinery (ACM)","issue":"6","license":[{"start":{"date-parts":[[2022,12,31]],"date-time":"2022-12-31T00:00:00Z","timestamp":1672444800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2022,12,31]]},"abstract":"<jats:p>This article examines three tools in the system acquisitions toolbox that can work to expedite development and procurement while mitigating programmatic risk: OSS, open standards, and the Agile\/Scrum software development processes are all powerful additions to the DoD acquisition program management toolbox.<\/jats:p>","DOI":"10.1145\/3576027","type":"journal-article","created":{"date-parts":[[2023,2,9]],"date-time":"2023-02-09T23:05:39Z","timestamp":1675983939000},"page":"58-79","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":2,"title":["Three-part Harmony for Program Managers Who Just Don't Get It, Yet"],"prefix":"10.1145","volume":"20","author":[{"given":"Guenever","family":"Aldrich","sequence":"first","affiliation":[{"name":"The Aerospace Corporation"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Danny","family":"Tsang","sequence":"additional","affiliation":[{"name":"The Aerospace Corporation"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Jason","family":"McKenney","sequence":"additional","affiliation":[{"name":"The Aerospace Corporation"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2023,2,9]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"Apache Software Foundation. 2004. Apache license version 2.0; https:\/\/www.apache.org\/licenses\/LICENSE-2.0."},{"key":"e_1_2_1_2_1","unstructured":"Beck K. Beedle M. van Bennekum A. Cockburn A. Cunningham W. Fowler M. Martin R. C. Mellor S. Thomas D. Grenning J. Highsmith J. Hunt A. Jeffries J. Kern J. Marick B. Schwaber K. Sutherland J. The Agile Manifesto. Agile Alliance; https:\/\/www.agilealliance.org\/agile101\/the-agile-manifesto\/."},{"volume-title":"Cybersecurity supply chain risk management practices for systems and organizations. U.S. Department of Commerce","author":"Boyens J.","key":"e_1_2_1_3_1","unstructured":"Boyens, J., Smith, A., Bartol, N., Winkler, K., Holbrook, A., Fallon, M. 2022. Cybersecurity supply chain risk management practices for systems and organizations. U.S. Department of Commerce, National Institute of Standards and Technology. NIST SP.800-161rl; https:\/\/nvlpubs.nist.gov\/nistpubs\/SpecialPublications\/NIST.SP.800-161r1.pdf."},{"key":"e_1_2_1_4_1","volume-title":"DoD's cyber strategy of past year outlined before Congress. DoD News. Department of Defense","author":"Cronk T. M.","year":"2020","unstructured":"Cronk, T. M. 2020. DoD's cyber strategy of past year outlined before Congress. DoD News. Department of Defense; https:\/\/www.defense.gov\/News\/News-Stories\/Article\/Article\/2103843\/dods-cyber-strategy-of-past-year-outlined-before-congress\/#:~:text=The%202018%20Defense%20Department%20cyber,official%20said%20on%20Capitol%20Hill."},{"key":"e_1_2_1_5_1","unstructured":"Drumond C. What is scrum? Atlassian; https:\/\/www.atlassian.com\/agile\/scrum#:~:text=Scrum%20is%20a%20framework%20that and%20losses%20to%20continuously%20improve."},{"key":"e_1_2_1_6_1","unstructured":"Francino Y. 2015. What is collaboration and why is it important to Agile methodologies? TechTarget; https:\/\/www.techtarget.com\/searchsoftwarequality\/answer\/What-is-collaboration-and-why-is-it-important-to-Agile-methodologies."},{"key":"e_1_2_1_7_1","unstructured":"Free Software Foundation Europe. Open standards; https:\/\/fsfe.org\/freesoftware\/standards\/def.en.html."},{"key":"e_1_2_1_8_1","unstructured":"GNU Operating System. 2007. GNU General Public License; https:\/\/www.gnu.org\/licenses\/gpl-3.0.html."},{"key":"e_1_2_1_9_1","unstructured":"Google. Contributing to Protocol Buffers. GitHub; https:\/\/github.com\/protocolbuffers\/protobuf\/blob\/master\/CONTRIBUTING.md."},{"volume-title":"Standards and Public Policy","author":"Greenstein S.","key":"e_1_2_1_10_1","unstructured":"Greenstein, S., Stango, V. 2007. Standards and Public Policy. New York, NY: Cambridge University Press."},{"key":"e_1_2_1_11_1","unstructured":"International Telecommunication Union Telecommunication Standardization Sector. Definition of \"Open Standards\"; https:\/\/www.itu.int\/en\/ITU-T\/ipr\/Pages\/open.aspx."},{"key":"e_1_2_1_12_1","unstructured":"Morris J. 2016. Which license should I use? MIT vs. Apache vs. GPL. Exygy; https:\/\/www.exygy.com\/blog\/which-license-should-i-use-mit-vs-apache-vs-gpl."},{"key":"e_1_2_1_13_1","unstructured":"Open Source Initiative. The MIT license; https:\/\/opensource.org\/licenses\/MIT."},{"key":"e_1_2_1_14_1","unstructured":"Open Source Initiative. Open standards requirement for software; https:\/\/opensource.org\/osr."},{"key":"e_1_2_1_15_1","unstructured":"Open Source Initiative. The 3-clause BSD license; https:\/\/opensource.org\/licenses\/BSD-3-Clause."},{"key":"e_1_2_1_16_1","unstructured":"OpenStand. 2014. 5 reasons open standards are essential to application development; https:\/\/open-stand.org\/5-reasons-open-standards-are-essential-to-application-development\/."},{"key":"e_1_2_1_17_1","unstructured":"OpenStand. Principles; https:\/\/open-stand.org\/about-us\/principles\/."},{"key":"e_1_2_1_18_1","unstructured":"Radigan D. Story points and estimation. Atlassian; https:\/\/www.atlassian.com\/agile\/project-management\/estimation."},{"key":"e_1_2_1_19_1","unstructured":"Rahman J. 2021. So what does a scrum master do? scrum.org; https:\/\/www.scrum.org\/resources\/blog\/so-what-does-scrum-master-do."},{"volume-title":"Efficient XML Interchange (EXI) format 1.0","author":"Schneider J.","key":"e_1_2_1_20_1","unstructured":"Schneider, J., Kamiya, T., Peinter, D., Kyusakov, R. 2014. Efficient XML Interchange (EXI) format 1.0 (second edition); https:\/\/www.w3.org\/TR\/exi."},{"key":"e_1_2_1_21_1","unstructured":"Sherman J. B. 2022. Software development and open source software. Memorandum for senior Pentagon leadership. Department of Defense; https:\/\/dodcio.defense.gov\/portals\/0\/documents\/library\/softwaredev-opensource.pdf."},{"volume-title":"Efficient XML interchange vs. Protocol Buffers for universal command and control","author":"Tsang D.","key":"e_1_2_1_22_1","unstructured":"Tsang, D., Aldrich, G. 2022. Efficient XML interchange vs. Protocol Buffers for universal command and control. The Aerospace Corporation."},{"key":"e_1_2_1_23_1","volume-title":"Information Technology Laboratory.","author":"U.S. Department of Commerce","year":"2022","unstructured":"U.S. Department of Commerce, National Institute of Standards and Technology, Information Technology Laboratory. 2022. Cybersecurity Supply Chain Risk Management (C-SCRM); https:\/\/csrc.nist.gov\/Projects\/cyber-supply-chain-risk-management."},{"key":"e_1_2_1_24_1","unstructured":"U.S. Department of Defense Undersecretary of Defense Research and Engineering Advanced Capabilities. Modular Open Systems Approach; https:\/\/ac.cto.mil\/mosa\/."},{"key":"e_1_2_1_25_1","unstructured":"U.S. Department of Defense. 2019. DOD supply chain material management policy. Office of the Under Secretary of Defense for Acquisition and Sustainment."},{"key":"e_1_2_1_26_1","volume-title":"Chief Information Officer","author":"U.S. Department of Defense","year":"2021","unstructured":"U.S. Department of Defense, Chief Information Officer. 2021. DoD open-source software FAQ; https:\/\/dodcio.defense.gov\/open-source-software-faq\/."},{"key":"e_1_2_1_27_1","volume-title":"Department of Defense Software Modernization","author":"U.S. Department of Defense. 2022.","year":"2022","unstructured":"U.S. Department of Defense. 2022. Department of Defense Software Modernization; https:\/\/media.defense.gov\/2022\/Feb\/03\/2002932833\/-1\/-1\/1\/department-of-defense-software-modernization-strategy.pdf."},{"key":"e_1_2_1_28_1","unstructured":"Wikipedia. Open Standard; https:\/\/en.wikipedia.org\/wiki\/Open_standard."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3576027","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3576027","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,17]],"date-time":"2025-06-17T17:49:39Z","timestamp":1750182579000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3576027"}},"subtitle":["Open-source software, open standards, and agile software development"],"short-title":[],"issued":{"date-parts":[[2022,12,31]]},"references-count":28,"journal-issue":{"issue":"6","published-print":{"date-parts":[[2022,12,31]]}},"alternative-id":["10.1145\/3576027"],"URL":"https:\/\/doi.org\/10.1145\/3576027","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2022,12,31]]},"assertion":[{"value":"2023-02-09","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}