How does SWOT analysis fit into an Agile and Scrum framework?

All answers to this question.

Use sticky notes! It’s the most "Agile" way to do a SWOT—quick, visual, and easy to pivot as the project evolves.

   Answered 2024-06-23 by Karen Phillips

• I love that, Karen. Visual aids like Miro or physical boards make SWOT much more collaborative and less like a chore for the developers.

     Commented 2024-06-24 by Michael Stevens

Would you recommend doing a SWOT for the entire product or just for the internal team's performance?

   Answered 2024-06-25 by Mark Peterson

• Mark, you should ideally do both but keep them separate. A "Product SWOT" helps with the Product Vision, while a "Team SWOT" is perfect for process improvement during Retrospectives. Just make sure the team doesn't feel like the "Weaknesses" section is a performance review; keep it focused on the system, not the person.

     Commented 2024-06-27 by Steven Harris

In Agile, SWOT should be a living document, not a 50-page report. Many high-performing Scrum teams use a "Micro-SWOT" during the Retrospective to analyze the last Sprint. For example, in a 2024 project, we identified our "Strength" as fast code reviews but our "Weakness" as poor documentation. This led to an immediate "Opportunity" to automate doc generation in the next Sprint. By keeping the analysis focused only on the current work cycle, it stays relevant and actionable without violating the "Individuals and interactions over processes" principle.

   Answered 2024-12-10 by Susan Anderson