[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-245346-105":53,"doc-detail-245346-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","capturing-model-based-risk-management-in-an-agile-scrum-environment-technical-report-3343","Capturing Model-based Risk Management in an Agile Scrum Environment - Technical Report 3343","","This technical report presents a reusable approach for managing risk using model-based systems engineering (MBSE) within an agile Scrum environment. It addresses how to model risk with MBSE and integrate MBSE-driven risk management into agile workflows. The method follows four core steps: identifying risks or opportunities, analyzing impacts, developing mitigation or enhancement tasks, and embedding continuous risk monitoring into daily processes. A Unified Architecture Framework (UAF) template, data schema, and entry forms support consistent, transparent, and organic risk definition and communication throughout development.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/capturing-model-based-risk-management-in-an-agile-scrum-environment-technical-report-3343/245346/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/capturing-model-based-risk-management-in-an-agile-scrum-environment-technical-report-3343/245346.png","ImageObject",442,249,{"name":88,"@type":89},"Jake","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-20","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What problem does the report address in agile Scrum software development?","Question",{"text":108,"@type":109},"Agile development helps manage some risks, but software work remains complex and error-prone. The report asks how to better manage risk by using MBSE in an agile environment.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What four steps does the proposed risk management approach follow?",{"text":113,"@type":109},"The approach covers: identifying risks or opportunities; analyzing risks and impacts; responding with mitigation or enhancement tasks; and integrating risk monitoring and management into daily processes.",{"name":115,"@type":106,"acceptedAnswer":116},"How does the Unified Architecture Framework (UAF) support the MBSE risk approach?",{"text":117,"@type":109},"The report uses UAF to develop a reusable template for representing risk in an MBSE model, including the supporting data schema and entry forms to keep risk defined and communicated consistently.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},245346,1789227732,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":125,"read_time":140},962084928904,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","TECHNICAL REPORT 3343 April 2024  \nCapturing Model-based Risk Management in an Agile Scrum Environment  \nFrancesca V. Mirabile Parker C. Suggs  \nJeff H. Waters  \nNIWC Pacific  \nApproved for public release. Distribution is unlimited.  \nThis page is intentionally blank.  \nTECHNICAL REPORT 3343 APRIL 2024  \nCapturing Model-based Risk Management in an Agile Scrum Environment  \nFrancesca V. Mirabile Parker C. Suggs  \nJeff H. Waters  \nNIWC Pacific  \nApproved for public release. Distribution is unlimited.  \nAdministrative Notes:  \nThis report was approved through the Release of Scientific and Technical Information (RSTI) process in July 2023 and formally published in the Defense Technical Information Center (DTIC) in April 2024.  \nADMINISTRATIVE INFORMATION  \nThe work described in this report was performed by the Command & Control (C2) Technology and Experimentation Division (specifically Branch Codes 53629 and 53622) of the Command & Control and Enterprise Engineering (C2E2) Department , Naval Information Warfare Center (NIWC) Pacific, San Diego, CA.  \nReleased by  \nEmily Nguyen, Division Head Command & Control (C2) Technology and Experimentation  \nUnder authority of  \nScott Crellin, Department Head Command & Control and Enterprise Engineering (C2E2)  \nACKNOWLEDGMENTS  \nWe would like to acknowledge the support of our colleagues and the leadership in our branches, division, and department.  \nThis is a work of the United States Government and , therefore, is not copyrighted. This work may be copied and disseminated without restriction. The citation of trade names and names of manufacturers is not to be construed as official government endorsement or approval of commercial products or services referenced in this report.  \nEditor: MGK  \nEXECUTIVE SUMMARY  \nThis paper describes a reusable approach for managing risk based on model-based systems engineering (MBSE) in a modern agile scrum environment. Software systems are often built with agile teams based on short sprints of user-defined tasks, with continuous customer feedback incorporated. Although the agile process is intended to address some forms of risk, software development is complex and error-prone. Can we do better? Many forward-thinking organizations develop models of systems to focus on simpler representations to design and test concepts before expending the time and cost of building the system. How do we model risk with MBSE? How do we integrate MBSE risk management with agile risk management?  \nThe authors address these questions based on key principles of risk management, agile , and model-based software environments to derive an integrated approach that is simple, reusable, practical, and organic. The approach addresses four key steps of risk management:  \n1. Identifying the risk or opportunity.  \n2. Analyzing the risk and its impacts.  \n3. Responding by developing mitigation or enhancement tasks.  \n4. Integrating risk monitoring and management into daily processes.  \nUsing the Unified Architecture Framework (UAF), the authors develop a reusable template for representing risk in an MBSE model. This report presents the template , the design of the data schema and entry forms , and a process for using them. The goal is to ensure that risk is defined, communicated , and managed organically and seamlessly during the entire development process.  \nThe authors present the approach in the following sections:  \n• Section 1 – Introduction and Definitions: Defining Risk, Opportunity, MBSE, and Agile  \n• Section 2 – Principles of MBSE-Driven Risk Management in an Agile Scrum Environment: Identifying guideposts of consistency and truth to inform the approach  \n• Section 3 – Approach Solution: A template and schema for defining and representing risk in an MBSE environment  \n• Section 4 – Integrating Risk Management into Agile Scrum Process: How the template fits into and can drive the Agile Process  \n• Section 5 – Conclusion  \nKeywords: Risk Management, Agile, Model-Based System Engineer","cbCaiaLEg3FwWeEf","https://ap.wps.com/l/cbCaiaLEg3FwWeEf","pdf",941636,38,"English","# Executive Summary\n# Acronyms\n# 1. Introduction and Definitions\n## 1.1 Introduction\n## 1.2 Risk\n## 1.3 Opportunity\n## 1.4 Model-Based Systems Engineering\n## 1.5 Agile and Scrum\n# 2. Principles of MBSE-Driven Risk Management in an Agile Scrum Environment\n# 3. Approach Solution\n## Approach Solution","[{\"question\":\"What problem does the report address in agile Scrum software development?\",\"answer\":\"Agile development helps manage some risks, but software work remains complex and error-prone. The report asks how to better manage risk by using MBSE in an agile environment.\"},{\"question\":\"What four steps does the proposed risk management approach follow?\",\"answer\":\"The approach covers: identifying risks or opportunities; analyzing risks and impacts; responding with mitigation or enhancement tasks; and integrating risk monitoring and management into daily processes.\"},{\"question\":\"How does the Unified Architecture Framework (UAF) support the MBSE risk approach?\",\"answer\":\"The report uses UAF to develop a reusable template for representing risk in an MBSE model, including the supporting data schema and entry forms to keep risk defined and communicated consistently.\"}]","Capturing Model-based Risk Management in an Agile Scrum Environment - Technical Report 3343 | PDF",13]