Shift left - Rethinking the development cycle
From a Business Analyst (BA) perspective, shifting left can have huge value. “We’re like the glue that sticks the team together, and we need to make sure everyone has enough information to keep them going,” Matt says. But if the team works in isolation and doesn’t have exposure to why and what they’re building early on, information can become lost or diluted. “You’d get to the end of a project and plenty of important conversations would have been lost along the way, and each would move you slightly further off course and you’d only pick up the issues when the Quality Analysis (QA) came in,” Matt continues. “So, for me as a BA, this allows everyone to get on the same page, see the big picture and cut out any assumptions before we even start development,” he concludes.
At Zühlke, the shift left approach shows up in the way developers are brought in early, so they can hear directly from the client what they want and how they expect the features to work. That big picture view means the team can start thinking about the solution from the outset. They are involved throughout the whole lifecycle so they gain more context and understanding, and ultimately more ability to innovate and trial when it gets to the development stage. “In this industry we need to be able to fail fast, learn from it and move on and if we have Quality Analysis happening earlier and earlier in the process, we’re able to do this,” Matt says.