SA&D—encompassing requirements, design, and project approach—has always been complex and challenging. But at least there once was a single, standard approach: plan driven. Plan-driven (e.g., traditional SDLC or “waterfall”) prescribes detailed, up-front requirements and linear, one-activity-at-a-time project execution. That changed in the mid-1990s when, given unacceptably high project failure rates, agile emerged as a key alternative, radically different from plan driven. Agile (e.g., eXtreme Programming, Scrum) defers detailed requirements and executes activities iteratively. In reality, many projects integrate elements of plan-driven and agile into a hybrid model. This complicates SA&D, requiring knowing how to: • Do everything in multiple ways • Choose the optimal approach This workshop cuts through the confusion with concepts, frameworks, and exercises helping you learn: • Essence of plan-driven vs. agile vs. hybrid o Two key dimensions: Requirements analysis and software construction o Underlying project assumptions: Impacting the value of plan-driven vs. agile vs. hybrid o Systems development process framework: Illustrating a unified understanding of each approach • How to choose the optimal approach o Key project characteristics: Using an extended “home grounds model” describing circumstances ideal for each approach o Radar chart tool: Analyzing each project in terms of functional requirements, non-functional requirements, and team characteristics, which point to the best approach