ComSen: Because Common Sense Isn't So Common in Software Development

Let's cut through the noise. After weeks of having Agile methodologies crammed down my throat, the absurdity of it all hit me—not in some epiphany under a waterfall, but amidst yet another marathon meeting that felt more like a ritual dance around the Agile totem than actual productive work. My team is small; we can make decisions over a cup of coffee. Yet here we are, bound by a framework designed for armies, not squads.

Hence, ComSen was born—not in a moment of divine inspiration, but from sheer frustration and, frankly, a bit of defiance. ComSen, short for Common Sense, is my shot across the bow at the one-size-fits-all methodologies that dominate today's software development landscape.

Why ComSen? Because in the realm of software development, common sense seems to have taken a backseat:

• People over Process: We've somehow forgotten that at the end of the day, it's people who deliver projects, not the processes or tools we obsess over.
• Learning from the Mess: The industry acts as if failure is a plague to be avoided at all costs. I say, let's embrace it. Failures are gold mines for learning, not something to be swept under the Agile rug.
• Choice and Autonomy Matter: The notion that everyone should march in lockstep, fascinated by the same tasks, is ludicrous. Passion drives performance, not participation trophies for attending stand-ups.
• Flexibility Isn't Up for Debate: Believing that a strict framework can suit the ever-changing demands of software development is unrealistic. Being adaptable isn't just an extra perk; it's absolutely fundamental.
• Streamlined Decision-Making: Cut through the bureaucratic red tape. Decisions should be swift, informed, and not bogged down by endless consensus-building. Efficiency doesn’t stem from everyone having a say on everything, but from leveraging insights and moving quickly.
• Experimentation Over Perfection: The fetishisation of the perfect process has killed more projects than a straightforward "try and see" attitude ever will. Innovation comes from doing, breaking, and learning—not from planning ad nauseam.
• Redefining Productivity and Task Management: Overloading sprints to appear ultra-productive or padding out tasks to fill time doesn’t just mislead—it harms. It's a practice that too often leads to team burnout without genuinely advancing our projects.
• Acknowledging the Real Pace of Work: Workflows vary—some tasks zip by, while others crawl. Yet, this natural rhythm is seldom acknowledged. We don't need to label every slow phase as a failure or every quick completion as a monumental success. It's about recognizing and respecting the actual pace of productive work.
• Adapting Without Blame: Let's aim for a strategy that genuinely reflects our capacity and allows for growth based on real feedback. Understanding what's behind delays or what can realistically be accelerated helps us improve without resorting to finger-pointing. It’s about making informed, supportive adjustments to how we plan and execute our tasks.
• Simplicity Above All: In a world addicted to complexity, ComSen is the intervention. It’s about making things as simple as they can be (but no simpler), to cut through the noise and actually get things done.

I’m not presenting ComSen as the holy grail of software development. It’s an alternative for those of us skeptical about the cult of methodology that’s taken over sensible project management. It’s for those who believe that, maybe, just maybe, applying a bit of common sense could lead to better results than any by-the-book Agile sprint ever could.

In the end, ComSen isn’t about rejecting all structured approaches outright. It’s about questioning whether those structures serve us or we serve them. It’s about finding a path that respects the intelligence, creativity, and indeed, the common sense of the people doing the work.

https://github.com/iqm0/comsen