{"id":13171,"date":"2023-03-17T20:30:57","date_gmt":"2023-03-17T11:30:57","guid":{"rendered":"https:\/\/www.btc-embedded.jp\/?p=13171"},"modified":"2023-04-28T21:25:20","modified_gmt":"2023-04-28T12:25:20","slug":"why-requirements-are-so-important-for-your-project","status":"publish","type":"post","link":"https:\/\/www.btc-embedded.jp\/ja\/why-requirements-are-so-important-for-your-project\/","title":{"rendered":"Why requirements are so important for your project"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"13171\" class=\"elementor elementor-13171\" data-elementor-post-type=\"post\">\n\t\t\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-3b5f0493 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"3b5f0493\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-559a247a\" data-id=\"559a247a\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-a1ff07f elementor-widget elementor-widget-text-editor\" data-id=\"a1ff07f\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.20.0 - 26-03-2024 *\/\n.elementor-widget-text-editor.elementor-drop-cap-view-stacked .elementor-drop-cap{background-color:#69727d;color:#fff}.elementor-widget-text-editor.elementor-drop-cap-view-framed .elementor-drop-cap{color:#69727d;border:3px solid;background-color:transparent}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap{margin-top:8px}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap-letter{width:1em;height:1em}.elementor-widget-text-editor .elementor-drop-cap{float:left;text-align:center;line-height:1;font-size:50px}.elementor-widget-text-editor .elementor-drop-cap-letter{display:inline-block}<\/style>\t\t\t\t<p data-pm-slice=\"1 1 []\">&#8220;<em>What is the biggest challenge in projects?<\/em>&#8220;<\/p><p>I asked that question during a coffee break at the 2022 MathWorks Automotive Conference in Stuttgart; I will share the answer I got in a minute.<\/p><p>But first, what do you think the biggest challenge in embedded software development projects is? Quite often, we think that the biggest challenge might be one of:<\/p><ol><li><span data-contrast=\"auto\">A lack of time, because development cycles have been becoming shorter and shorter. And this definitely is a big challenge, but it can be effectively addressed by efficient workflow and automation processes.<\/span><span data-ccp-props=\"{&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/li><li><span class=\"NormalTextRun SCXW184383887 BCX4\">Money. Of course, you need to spend a lot of money <\/span><span class=\"NormalTextRun ContextualSpellingAndGrammarErrorV2Themed SCXW184383887 BCX4\">in<\/span><span class=\"NormalTextRun SCXW184383887 BCX4\"> your projects, and you <\/span><span class=\"NormalTextRun SCXW184383887 BCX4\">need to <\/span><span class=\"NormalTextRun SCXW184383887 BCX4\">keep an eye on the available resources to stay <\/span><span class=\"NormalTextRun SCXW184383887 BCX4\">with<\/span><span class=\"NormalTextRun SCXW184383887 BCX4\">in the defined budget<\/span><span class=\"NormalTextRun SCXW184383887 BCX4\">,<\/span><span class=\"NormalTextRun SCXW184383887 BCX4\"> but <\/span><span class=\"NormalTextRun SCXW184383887 BCX4\">this is still <\/span><span class=\"NormalTextRun SCXW184383887 BCX4\">not the biggest issue<\/span><span class=\"NormalTextRun SCXW184383887 BCX4\">.<\/span><\/li><li>A <span class=\"NormalTextRun SCXW39785519 BCX4\">shortage of skilled workers<\/span><span class=\"NormalTextRun SCXW39785519 BCX4\">,<\/span><span class=\"NormalTextRun SCXW39785519 BCX4\"> which <\/span><span class=\"NormalTextRun SCXW39785519 BCX4\">can <\/span><span class=\"NormalTextRun SCXW39785519 BCX4\">lead to projects being delayed.<\/span><\/li><\/ol><p>But none of them is the elephant in the room. The surprising answer I got at the conference was:<\/p><h3 style=\"text-align: center;\">&#8220;<em>missing requirements<\/em>&#8220;<\/h3><p>Missing requirements are the main reasons why projects fail and run out of budget and time. <span class=\"TextRun SCXW232085278 BCX4\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW232085278 BCX4\"> If\u202f<\/span><\/span><span style=\"text-decoration: underline;\"><span class=\"TextRun Underlined SCXW232085278 BCX4\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW232085278 BCX4\">what<\/span><\/span><\/span><span class=\"TextRun SCXW232085278 BCX4\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW232085278 BCX4\">\u202fto develop is unclear, <\/span><span class=\"NormalTextRun SCXW232085278 BCX4\">then too much<\/span><span class=\"NormalTextRun SCXW232085278 BCX4\"> additional effort is needed <\/span><span class=\"NormalTextRun SCXW232085278 BCX4\">while the project is running <\/span><span class=\"NormalTextRun SCXW232085278 BCX4\">to<\/span><span class=\"NormalTextRun SCXW232085278 BCX4\"> find that out and fix it<\/span><span class=\"NormalTextRun SCXW232085278 BCX4\">.<\/span><\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-2cb1475 elementor-widget elementor-widget-heading\" data-id=\"2cb1475\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.20.0 - 26-03-2024 *\/\n.elementor-heading-title{padding:0;margin:0;line-height:1}.elementor-widget-heading .elementor-heading-title[class*=elementor-size-]>a{color:inherit;font-size:inherit;line-height:inherit}.elementor-widget-heading .elementor-heading-title.elementor-size-small{font-size:15px}.elementor-widget-heading .elementor-heading-title.elementor-size-medium{font-size:19px}.elementor-widget-heading .elementor-heading-title.elementor-size-large{font-size:29px}.elementor-widget-heading .elementor-heading-title.elementor-size-xl{font-size:39px}.elementor-widget-heading .elementor-heading-title.elementor-size-xxl{font-size:59px}<\/style><h3 class=\"elementor-heading-title elementor-size-default\">But why does this happen?<\/h3>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-732d3d4 elementor-widget elementor-widget-text-editor\" data-id=\"732d3d4\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p>I think the answer is quite simple here. We love to <em>create<\/em> instead of <em>thinking<\/em> about how to create!<\/p><p data-pm-slice=\"1 1 []\">And in the Embedded Software world, tools like Simulink and Stateflow make it easy to start creating without any documented requirements. We can immediately press the \u201cPlay\u201d button to observe the behavior in a simulation, or even perform rapid prototyping with dedicated hardware tools like a dSPACE MicroAutoBox. <span class=\"TextRun SCXW56849477 BCX4\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW56849477 BCX4\">This means that, when the time comes to think about requirements, oftentimes they\u2019re viewed as just a documentation of what\u2019s already been done, rather than as a guideline for what to do, before doing it; <\/span><span class=\"NormalTextRun SCXW56849477 BCX4\">I\u2019ve even seen projects where the <\/span><span class=\"NormalTextRun SCXW56849477 BCX4\">submitted <\/span><span class=\"NormalTextRun SCXW56849477 BCX4\">requirements document was <\/span><span class=\"NormalTextRun SCXW56849477 BCX4\">just <\/span><span class=\"NormalTextRun SCXW56849477 BCX4\">a PDF <\/span><span class=\"NormalTextRun SCXW56849477 BCX4\">full of screenshots from Simulink!<\/span><\/span><span class=\"EOP SCXW56849477 BCX4\" data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p><p><span class=\"NormalTextRun SCXW69914997 BCX4\">And I know that <\/span><span class=\"NormalTextRun SCXW69914997 BCX4\">mentality is tempting<\/span><span class=\"NormalTextRun SCXW69914997 BCX4\">. <\/span><span class=\"NormalTextRun SCXW69914997 BCX4\">Even <\/span><span class=\"NormalTextRun SCXW69914997 BCX4\">for my little (electronic and 3D-printing) projects at home, I just start with a rough idea and then, without enough preparation, I<\/span><\/p><ul><li>gather the required components,<\/li><li>solder the parts on a board,<\/li><li>design enclosures with Fusion 360 or OnShape,<\/li><li>print them on my 3D printer,<\/li><li>write some code to tie everything together<\/li><\/ul><p>I just want to turn my idea into a reality as soon as possible. But for larger and safety-critical projects, is it really a good idea to neglect or skip the requirements engineering phase?<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-ffe7789 elementor-widget elementor-widget-heading\" data-id=\"ffe7789\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<h3 class=\"elementor-heading-title elementor-size-default\">What does research and science say about this phenomenon?<\/h3>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-24084d2 elementor-widget elementor-widget-text-editor\" data-id=\"24084d2\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p data-pm-slice=\"1 1 []\"><span class=\"TextRun SCXW228335986 BCX4\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW228335986 BCX4\">The short answer is that this <\/span><span class=\"NormalTextRun SCXW228335986 BCX4\">problem has been <\/span><span class=\"NormalTextRun SCXW228335986 BCX4\">well known <\/span><span class=\"NormalTextRun SCXW228335986 BCX4\">for over <\/span><span class=\"NormalTextRun SCXW228335986 BCX4\">40 years. Back in the early 1980s, Barry W. Boehm researched why software development projects fail. This gave rise to the Constructive Cost Model (COCOMO). <\/span><span class=\"NormalTextRun SCXW228335986 BCX4\">Then, i<\/span><span class=\"NormalTextRun SCXW228335986 BCX4\">n the early 2000s, the Constructive Systems Engineering Cost Model (COSYSMO) was developed from <\/span><span class=\"NormalTextRun SCXW228335986 BCX4\">COCOMO<\/span><span class=\"NormalTextRun SCXW228335986 BCX4\"> by Ricardo Valerdi and Boehm at the University of Southern California Center for Software Engineering.<\/span><\/span><span class=\"EOP SCXW228335986 BCX4\" data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-d90d852 elementor-widget elementor-widget-image\" data-id=\"d90d852\" data-element_type=\"widget\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.20.0 - 26-03-2024 *\/\n.elementor-widget-image{text-align:center}.elementor-widget-image a{display:inline-block}.elementor-widget-image a img[src$=\".svg\"]{width:48px}.elementor-widget-image img{vertical-align:middle;display:inline-block}<\/style>\t\t\t\t\t\t\t<figure class=\"wp-caption\">\n\t\t\t\t\t\t\t\t\t\t<img decoding=\"async\" src=\"https:\/\/www.btc-embedded.com\/wp-content\/uploads\/2023\/02\/COSYSMO_EMR.png\" title=\"\" alt=\"What is the biggest challenge in projects? - COSYSMO Table\" loading=\"lazy\" \/>\t\t\t\t\t\t\t\t\t\t\t<figcaption class=\"widget-image-caption wp-caption-text\">Rating Scales for COSYSMO Effort Multipliers<\/figcaption>\n\t\t\t\t\t\t\t\t\t\t<\/figure>\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-56fe7d4 elementor-widget elementor-widget-text-editor\" data-id=\"56fe7d4\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p>(Source: <a href=\"https:\/\/dspace.mit.edu\/bitstream\/handle\/1721.1\/83521\/JART_100301_Valerdi_Boehm_Genie_Logicel.pdf\" target=\"_blank\" rel=\"noopener\">https:\/\/dspace.mit.edu\/bitstream\/handle\/1721.1\/83521\/JART_100301_Valerdi_Boehm_Genie_Logicel.pdf)<\/a><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-235f3c8 elementor-widget elementor-widget-text-editor\" data-id=\"235f3c8\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p><span data-contrast=\"auto\">Long story short: The highest effort multiplier ratio (EMR) is allocated to requirements understanding and this has not changed until today. I even claim that due to today\u2019s project conditions, such as shorter release cycles and a higher demand on cost efficiency, this factor is even higher. A wrong understanding of the requirements and the resulting additional efforts have a more serious impact on the success of the projects today than they did even in the past.<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p><p><span data-contrast=\"auto\">But why do we still have missing or low quality requirements when we know how detrimental this is?<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p><p><span data-contrast=\"auto\">I think the main reason is the action-over-planning bias. I can promote my project much better to management and customers if I can demonstrate something early on. Due to the already mentioned general conditions in the projects, the action-over-planning behavior is further privileged by management. It gives the impression that someone has recognized a problem and also has a solution ready. This is a dangerous pitfall in projects; there have already been several inglorious examples of this in the automotive industry.<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-f4dea72 elementor-widget elementor-widget-heading\" data-id=\"f4dea72\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<h3 class=\"elementor-heading-title elementor-size-default\"><span style=\"color: var( --e-global-color-primary ); font-family: var( --e-global-typography-71433d6-font-family ), Sans-serif; font-size: var( --e-global-typography-71433d6-font-size ); font-style: var( --e-global-typography-71433d6-font-style ); font-weight: var( --e-global-typography-71433d6-font-weight ); letter-spacing: var( --e-global-typography-71433d6-letter-spacing ); text-transform: var( --e-global-typography-71433d6-text-transform ); word-spacing: var( --e-global-typography-71433d6-word-spacing ); background-color: var( --e-global-color-8c64e01 );\">How to address this biggest challenge in projects?<\/span><\/h3>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-6cdaf06 elementor-widget elementor-widget-text-editor\" data-id=\"6cdaf06\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p><span data-contrast=\"auto\">I think we can agree that we do not have a tool problem here. There are a lot of good requirements management tools on the market. As I pointed out before, the mindset in projects needs to be changed! We must overcome the \u201caction-over-planning bias.\u201d<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p><p><span data-contrast=\"auto\">Maybe managers should reward project leaders and members for focusing on good requirements and spending time on developing them. The consensus in the research on this topic and the experience of many projects proves that good and complete requirements are a necessary prerequisite for a successful project.<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p><p><span data-contrast=\"auto\">Maybe employees should show that the mistakes of past projects could have been avoided by better requirements management, and that the action-over-planning bias causes a lot of problems for the complex products we develop today.<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p><p>Also have a look at the article <a href=\"https:\/\/www.btc-embedded.com\/why-and-how-to-improve-requirements\/\" target=\"_blank\" rel=\"noopener\">Why and How to Improve Requirements<\/a>,\u00a0where Bernd Holzm\u00fcller (ITK Engineering) and I describe the origins of quality issues in requirements.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-ffdae69 elementor-widget elementor-widget-heading\" data-id=\"ffdae69\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<h3 class=\"elementor-heading-title elementor-size-default\">So far so good, but how is that supposed to work in agile projects?<\/h3>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7c64fc2 elementor-widget elementor-widget-text-editor\" data-id=\"7c64fc2\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p data-pm-slice=\"1 1 []\">Great!<\/p><p data-pm-slice=\"1 1 []\">One argument for why requirements are as they are today, is that we cannot provide detailed requirements in an agile project and that this would violate the <em>Manifesto for Agile Software Development<\/em>. Doesn&#8217;t it say &#8220;Working software over comprehensive documentation&#8221;?<\/p><p data-pm-slice=\"1 1 []\">Well, I think, we should clarify this argument. <span class=\"NormalTextRun SCXW262039922 BCX4\">The requirements situation in many projects, especially on <\/span><span class=\"NormalTextRun SCXW262039922 BCX4\">the <\/span><span class=\"NormalTextRun SCXW262039922 BCX4\">unit but <\/span><span class=\"NormalTextRun SCXW262039922 BCX4\">even on the <\/span><span class=\"NormalTextRun SCXW262039922 BCX4\">component level<\/span><span class=\"NormalTextRun SCXW262039922 BCX4\">,<\/span><span class=\"NormalTextRun SCXW262039922 BCX4\"> is often far from \u201ccomprehensive documentation\u201d. <\/span> \ud83d\ude09 <\/p><p><span data-contrast=\"auto\">I remember a project where the specification was a bound book that described all the requirements to the smallest detail. This is what is meant by comprehensive documentation, and it\u2019s too suffocating to allow for effective development and testing.\u202fIn contrast, though, it is also clear that it\u2019s impossible to develop or test against requirements that are missing altogether.\u202f<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p><p><span data-contrast=\"auto\">And one more short note: Please, please do not mix up detailed design requirements with functional requirements. Of course, you can write a test case that implements the same algorithm that the model\/code does as described in the detailed design. However, this test case just shows that the test tool calculates the same result as the model\/code, and therefore is just a back-to-back test. However, it does not answer the question of whether the functional behavior has been fulfilled.<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p><p><span data-contrast=\"auto\">Agile software development is not about developing against moving targets- it is about talking and setting the requirements for a specific part of the software right\u202f<\/span><i><span data-contrast=\"auto\">before<\/span><\/i><span data-contrast=\"auto\">\u202fthe development starts. The goal of the Sprint Planning is that each project participant is clear about what is to be developed in the next Sprint period, ambiguities are resolved, and there is a common understanding of what has been developed and tested at the end of the period.<\/span><span data-ccp-props=\"{&quot;134233118&quot;:true,&quot;201341983&quot;:2,&quot;335559740&quot;:390}\">\u00a0<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-5471b75 elementor-widget elementor-widget-heading\" data-id=\"5471b75\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<h3 class=\"elementor-heading-title elementor-size-default\">Conclusion<\/h3>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-2a01264 elementor-widget elementor-widget-text-editor\" data-id=\"2a01264\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p><span class=\"TextRun SCXW161511889 BCX4\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW161511889 BCX4\">Incomplete and missing requirements are part of today\u2019s projects. We have also learned that this is the highest project risk and that this is a problem of business culture. Also, agile development does not solve this issue. <\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">W<\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">e should<\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">n\u2019t<\/span> <span class=\"NormalTextRun SCXW161511889 BCX4\">ignore<\/span><span class=\"NormalTextRun SCXW161511889 BCX4\"> this knowledge <\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">for <\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">another four decades<\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">,<\/span><span class=\"NormalTextRun SCXW161511889 BCX4\"> but <\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">instead should <\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">start <\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">implementing change <\/span><span class=\"NormalTextRun SCXW161511889 BCX4\">today.<\/span><\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>&#8220;What is the biggest challenge in projects?&#8220; I asked that question during a coffee break at the 20 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":13172,"comment_status":"open","ping_status":"closed","sticky":false,"template":"elementor_theme","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[55,56,54],"product":[],"use_cases":[],"class_list":["post-13171","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-ci-cd","tag-cloud","tag-jenkins"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/posts\/13171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/comments?post=13171"}],"version-history":[{"count":1,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/posts\/13171\/revisions"}],"predecessor-version":[{"id":13185,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/posts\/13171\/revisions\/13185"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/media\/13172"}],"wp:attachment":[{"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/media?parent=13171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/categories?post=13171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/tags?post=13171"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/product?post=13171"},{"taxonomy":"use_cases","embeddable":true,"href":"https:\/\/www.btc-embedded.jp\/ja\/wp-json\/wp\/v2\/use_cases?post=13171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}