![\"Adopting](\"https:\/\/www.jamasoftware.com\/media\/2022\/02\/2022-02-10-v2-mbse-challenging-status-quo.jpg\")
<\/p>\n<\/p>\n
<\/p>\n
This blog contains excerpts from a whitepaper titled, The Comprehensive Guide to Successfully Adopting MBSE<\/a><\/strong>, written by Lou Wheatcraft.\u00a0<\/em><\/p>\n For product development teams to successfully implement a practice such as model-based systems engineering (MBSE), it requires the willingness of an organization to perhaps change processes and even tooling. Often, companies choose to stay with the status quo, but at what cost? Here’s a look at how adopting MBSE might help your teams, and the cost of not adopting MBSE<\/a>.<\/p>\n Understand the Need to Move for Change\u00a0<\/strong><\/p>\n For the MBSE Implementation Project Team to be successful, management must recognize the need to change. How can management be convinced? Three words \u2013 RETURN ON INVESTMENT (ROI)!<\/p>\n Think about these questions:\u00a0<\/strong><\/p>\n The ROI argument usually works with management especially when they can be convinced that by investing in a data-centric practice of SE tailored to the organization\u2019s needs, the overall product development process, product quality, time to market, and profitability can be improved as discussed previously.<\/p>\n To entice anyone \u2014 especially an entire organization \u2014 to make a change, proving ROI<\/a> on the resource investment is key. Here are some key points to consider:<\/p>\n A good process is not one that is something people have to do in addition to their job, rather it is one that helps people do their job more effectively. \u2013 LOU WHEATCRAFT<\/p><\/blockquote>\n To get buy in from the product development teams, the MBSE Implementation Project Team must:<\/p>\n The MBSE Implementation Project Team\u2019s mission statement will be something like: \u201cImprove our product development processes by adopting MBSE within the organization by moving from a document-centric to a data-centric practice of systems engineering.\u201d<\/strong> <\/em>Along with this mission statement, they will need to define a set of specific goals and objectives along with measures of success. Once defined, they will need to get agreement from management on these goals, objectives, and measures.<\/p>\n Project success is dependent on having a high-level, C-suite project champion and getting management buy in. A major challenge for the project will be convincing management and other key stakeholders that it is time for adopting MBSE and moving from a document-centric to a data-centric practice of SE and knocking down the walls of resistance. Some common reasons for them not wanting to move to a data-centric practice of SE include:<\/p>\n Sound familiar? Often the pushback can be attributed to a lack of understanding the risks associated with the current state of the organization, understanding the benefits of moving toward a more data-centric practice of SE, and what level of SE capability is appropriate for the organization.<\/p>\n To inspire a shift from a document-centric to a data-centric practice of SE in your organization, it\u2019s vital to show both teams and management the value and expected ROI in doing so. Moving away from a current way of doing things isn\u2019t always an easy road, but the risks of staying with the status quo are often great\u2014and the rewards for changing processes and culture are often even greater.<\/p>\n An organization will be successful in practicing SE from a data-centric perspective when it is considered to be the \u201cgold standard\u201d for system development within the organization. However, the road to success is long \u2014 it takes very strong, unwavering leadership and experience to get this done right. It is human nature to try to push back and say that it isn\u2019t possible, but it is.<\/p>\n
\nAdopting MBSE: Challenging the Status Quo in Product Development<\/h2>\n
What is the Risk of Staying with the Status Quo?<\/h3>\n
\n
What is the ROI of Adopting MBSE?<\/h3>\n
\n
Combating Opposition to Change<\/h3>\n
\nRELATED: <\/strong>Traceable MBSE\u2122 in Jama Connect\u00ae<\/sup>: Quickstart Guide<\/a><\/span><\/span><\/h4>\n
\nGet Team Buy-In<\/h3>\n
\n
\nRELATED: <\/strong>Jama Connect for Traceable MBSE\u2122<\/a><\/span><\/span><\/h4>\n
\nGet Management Buy-In<\/h3>\n
\n
\nRELATED: <\/strong>Dexcom Achieves 60% Systems Engineering Efficiency Improvement with Jama Connect<\/a><\/span><\/span><\/h4>\n
\nAdopting MBSE: The Road to Success<\/h3>\n