In the ever-evolving world of digital, data and cyber-physical systems, software teams constantly face the challenge of implementing significant changes, whether product pivots or major tech infrastructure modernizations. These teams, often well-versed in Agile and DevOps methodologies and using ticketing systems like Jira, operate efficiently within their established norms. However, when faced with large-scale changes that require re-engineering or replacing interfaces, they may encounter problems that go beyond "business as usual."  Using a scenario-based approach, we will explore the types of problems that emerge, the underlying causal system, and then discuss when and how to introduce fit-for-use Systems Engineering capability to ensure project success and business value.

In the context of frequently-occurring scenarios of team and workflow dynamics when facing large-scale software product changes, we will discuss:

• A pattern of pain points, direct and root causes spanning interconnected role, process and technical challenges

• A causal model to show when “business as usual” misses key early activities

• About a decision guide to help software teams recognize when to add systems engineering and architectural capabilities