{"id":8102049,"date":"2025-11-12T12:47:30","date_gmt":"2025-11-12T20:47:30","guid":{"rendered":"https:\/\/agilealliance.org\/?p=8102049"},"modified":"2026-02-23T12:50:57","modified_gmt":"2026-02-23T20:50:57","slug":"case-study-applying-agile-in-hardware-software-systems","status":"publish","type":"post","link":"https:\/\/agilealliance.org\/case-study-applying-agile-in-hardware-software-systems\/","title":{"rendered":"Case Study: Applying Agile in Hardware-Software Systems"},"content":{"rendered":"\n<p><em>This Agile case study is drawn from the Agile Experience Report<\/em>\u00a0\u201c<em><a href=\"https:\/\/agilealliance.org\/resources\/experience-reports\/navigating-mobile-robotics-development-delivery-using-agile\/\" title=\"\">Navigating Mobile Robotics Development &amp; Delivery Using Agile<\/a><\/em>\u201d\u00a0<em>written by Kanika Sharma<\/em>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p>A global mobile robotics and automation manufacturer, producing Automated Guided Vehicles (AGVs) for industries such as logistics, healthcare, and automotive manufacturing, faced delivery delays and collaboration challenges across software, mechanical, and electrical teams. The organization implemented Agile principles and values to improve transparency, responsiveness, and cross-functional coordination in developing complex, safety-critical systems.<\/p>\n\n\n\n<p>Applying Agile ways of working within software and supervisory control teams led to measurable business outcomes and stronger alignment across departments.<\/p>\n\n\n\n<p><strong>Key results included:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>95 percent increase in transparency between teams and stakeholders<\/li>\n\n\n\n<li>80 percent reduction in late-stage layout change rework<\/li>\n\n\n\n<li>20 percent faster resolution of customer issues<\/li>\n\n\n\n<li>Improved collaboration across software, system engineering, and support functions<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">The challenge<\/h2>\n\n\n\n<p>The company built AGVs that combined complex software, hardware, and safety systems. Delivery timelines were impacted by slow feedback loops and siloed working practices. Layout changes from customers arrived late in the process, creating costly rework cycles. Project managers and system engineers were accustomed to detailed planning and control, making the shift toward iterative delivery difficult. Software teams, meanwhile, struggled with constant customer support interruptions that disrupted planned development work.<\/p>\n\n\n\n<p>These challenges reflected a gap between the organization\u2019s processes and Agile values, such as&nbsp;<strong>customer collaboration over contract negotiation<\/strong>&nbsp;and&nbsp;<strong>responding to change over following a plan<\/strong>. A new approach was required to create faster learning cycles and better cross-team communication.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The approach<\/h2>\n\n\n\n<p>The transformation began within the software and supervisory systems teams. The focus was to apply Agile practices that aligned with the company\u2019s safety and regulatory environment while building trust with other departments. Agile values guided the shift:&nbsp;<strong>individuals and interactions over processes and tools<\/strong>, and&nbsp;<strong>working software over comprehensive documentation<\/strong>.<\/p>\n\n\n\n<p><strong>Key Agile practices introduced included:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Adoption of Scrum in software development, with iterative sprint cycles and regular reviews<\/li>\n\n\n\n<li>Setting aside 20 percent of sprint capacity for customer issues to balance responsiveness with planned work<\/li>\n\n\n\n<li>Lean Coffee sessions and Agile coaching to engage non-software departments and surface shared pain points<\/li>\n\n\n\n<li>Shifting from team-based to product-based demos to encourage shared ownership and transparency<\/li>\n\n\n\n<li>Introducing Scrum of Scrums meetings to improve coordination between supervisory and vehicle software teams<\/li>\n<\/ul>\n\n\n\n<p>These practices embodied principles such as&nbsp;<strong>frequent collaboration between business and developers<\/strong>&nbsp;and&nbsp;<strong>delivering value early and continuously<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Implementation and iteration<\/h2>\n\n\n\n<p>Agile implementation was incremental and guided by continuous feedback. The team began by mapping stakeholders and identifying dependencies. Small, low-risk experiments like new sprint reporting formats built credibility and created transparency that other departments valued.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Stakeholder mapping:<\/strong>\u00a0Informal conversations identified blockers and influencers who shaped collaboration<\/li>\n\n\n\n<li><strong>Sprint reports:<\/strong>\u00a0Clear visual summaries replaced ad hoc updates and built trust with project managers<\/li>\n\n\n\n<li><strong>Cross-Team demos:<\/strong>\u00a0Combined reviews improved understanding of shared goals and reduced duplication<\/li>\n\n\n\n<li><strong>Customer issue triage:<\/strong>\u00a0A structured intake process improved SLA compliance and reduced firefighting<\/li>\n\n\n\n<li><strong>Scrum of Scrums:<\/strong>\u00a0Coordination between teams cut delivery blockers in half within months<\/li>\n<\/ul>\n\n\n\n<p>Each change followed the Agile principle of&nbsp;<strong>reflecting and adapting regularly<\/strong>&nbsp;to improve effectiveness.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Results and impact<\/h2>\n\n\n\n<p>Measured outcomes included the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Transparency improved by 95 percent, as measured through internal stakeholder surveys<\/li>\n\n\n\n<li>Late-stage layout change rework was reduced by 80 percent within six to eight months<\/li>\n\n\n\n<li>Medium-priority customer issues resolved 20 percent faster<\/li>\n\n\n\n<li>Cross-team blockers resolved 50 percent faster following Scrum of Scrums adoption<\/li>\n\n\n\n<li>Post-deployment AGV disruptions reduced by 85 percent after site worker training<\/li>\n<\/ul>\n\n\n\n<p>Customer satisfaction and internal predictability improved significantly. Teams began to see Agile not as a process to follow but as a way to deliver value continuously and collaborate effectively across disciplines.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Lessons learned<\/h2>\n\n\n\n<p>The organization\u2019s experience highlighted that Agile transformation in complex, regulated environments succeeds when guided by principles rather than rigid frameworks. The following lessons show how specific Agile principles and values came to life in practice.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Adapt Agile practices to context<\/strong><br>(Principle #9: \u201cContinuous attention to technical excellence and good design enhances agility\u201d)<br>Tailoring Scrum to accommodate hardware and safety dependencies allowed Agile to work effectively within domain constraints.<\/li>\n\n\n\n<li><strong>Start with small, visible changes<\/strong><br>(Principle #10: \u201cSimplicity\u2014the art of maximizing the amount of work not done\u2014is essential\u201d)<br>Incremental shifts, such as introducing sprint reports and shared demos, built confidence and demonstrated value quickly.<\/li>\n\n\n\n<li><strong>Prioritize collaboration over compliance<\/strong><br>(Manifesto Value: \u201cIndividuals and interactions over processes and tools\u201d)<br>Informal engagement, workshops, and open communication created alignment where formal mandates had failed.<\/li>\n\n\n\n<li><strong>Respond to change with structure, not chaos<\/strong><br>(Manifesto Value: \u201cResponding to change over following a plan\u201d)<br>The dedicated customer issue process turned unplanned requests into managed, predictable work streams.<\/li>\n\n\n\n<li><strong>Promote collective ownership and learning<\/strong><br>(Principle #12: \u201cAt regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly\u201d)<br>Teams continuously adjusted sprint structures and communication practices based on feedback and results.<\/li>\n<\/ul>\n\n\n\n<p>Through these lessons, the company demonstrated that Agile values and principles can thrive even in hardware-software co-development environments when applied thoughtfully and with respect for domain realities.<\/p>\n\n\n\n<p><em>Read the original Agile Experience Report<\/em>\u00a0\u201c<em><a href=\"https:\/\/agilealliance.org\/resources\/experience-reports\/navigating-mobile-robotics-development-delivery-using-agile\/\" title=\"\">Navigating Mobile Robotics Development &amp; Delivery Using Agile<\/a><\/em>\u201d\u00a0<em>written by Kanika Sharma<\/em>.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A global robotics manufacturer applied Agile principles to improve delivery speed, cross-functional collaboration, and responsiveness in the development of complex, safety-critical Automated Guided Vehicles.<\/p>\n","protected":false},"author":8033092,"featured_media":8102078,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_tec_requires_first_save":true,"_EventAllDay":false,"_EventTimezone":"","_EventStartDate":"","_EventEndDate":"","_EventStartDateUTC":"","_EventEndDateUTC":"","_EventShowMap":false,"_EventShowMapLink":false,"_EventURL":"","_EventCost":"","_EventCostDescription":"","_EventCurrencySymbol":"","_EventCurrencyCode":"","_EventCurrencyPosition":"","_EventDateTimeSeparator":"","_EventTimeRangeSeparator":"","_EventOrganizerID":[],"_EventVenueID":[],"_OrganizerEmail":"","_OrganizerPhone":"","_OrganizerWebsite":"","_VenueAddress":"","_VenueCity":"","_VenueCountry":"","_VenueProvince":"","_VenueState":"","_VenueZip":"","_VenuePhone":"","_VenueURL":"","_VenueStateProvince":"","_VenueLat":"","_VenueLng":"","_VenueShowMap":false,"_VenueShowMapLink":false,"_tribe_blocks_recurrence_rules":"","_tribe_blocks_recurrence_description":"","_tribe_blocks_recurrence_exclusions":"","ep_exclude_from_search":false,"_jf_limit_responses":"","footnotes":""},"categories":[908],"tags":[2184],"content_source":[],"class_list":["post-8102049","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-process","tag-success-story"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8102049","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/8033092"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8102049"}],"version-history":[{"count":5,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8102049\/revisions"}],"predecessor-version":[{"id":8104710,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8102049\/revisions\/8104710"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8102078"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8102049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8102049"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8102049"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8102049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}