Why do software bugs happen?

I feel what’s interesting is answering the question “Why do software bugs happen?” You could come up with a list of answers. Then overtime with this experience you can start moving from calling out issues (a bad thing *is* happening right now) to a risk (a bad thing *might* happen, so let’s get a mitigation plan in place). So moving from a reactive approach (raising issues) to a proactive approach (raising risks).

So for example, here are a few of my answers on why software bugs arise: Design flaws, neglecting real user scenarios, unrealistic development timeframes, gaps (such as the classic “non functionals” not discussed earlier) or excessive reliance on test automaton.

Then with this understanding of why software bugs happen I can move from reactive to proactive by exploring what I can do to proactively raise risks.

Design flaws — Review the design before we start building.

Neglecting real user scenarios — Understand user needs and wants by creating a persona set.

Unrealistic development timeframe — call out a risk with development timeframes.

Gaps — Discuss non functional requirements early

Excessive reliance on test automation — Ensure there is that balance between exploratory and test automation.

Overall super interesting in doing this type of exercise in exploring your thinking about making the shift from raising issues to risks.