The Software Project Audit

The audit is a fixed-price investigation of one software project: the people, the process, and the technology. I interview everyone from the sponsor to the newest developer, look at the code and the infrastructure, and trace each complaint back to its actual cause.

You get a written report that ranks the problems by damage, explains the root cause of each, and lays out fixes detailed enough for your team to act on without me.

This is a good fit if you:

• Have a project that is late, over budget, unstable, or all three.
• Are a non-technical owner or executive who can't tell whether the team's explanations hold up.
• Are thinking about replacing a vendor or a team and want an independent opinion first.
• Have a team of about twenty people or fewer. Larger or multi-team projects get a custom plan.

This is not a good fit if you:

• Want a report that confirms what you've already decided.
• Aren't willing to change how the team works. Most fixes are process fixes.
• Need someone to write the code this month. That's a Fractional CTO engagement, and it usually starts with this audit.

AI Software Audit, for development teams

Contrary to the hype, AI isn't replacing software engineers any time soon. But a developer working with AI assistance can be up to twice as productive on the right tasks [1], and most teams are nowhere near that because nobody has looked at which tasks those are.

This audit maps your development process, finds the steps where AI tooling pays off, picks the specific tools, and leaves you with a written AI policy so the team knows what's allowed, what's reviewed, and what never leaves the building.

I use these tools every day on my own projects, so the recommendations come from what works in practice, not from a vendor's benchmark.

If your project is also late or unstable, start with the Software Project Audit above. This one works best on a team that already ships reliably and wants to ship faster.

Small 'a' agile

My recommendations are guaranteed not to include typical consulting buzzwords like “Scrum” or “Sprint.”

I follow the original definition of Agile Software Development, with processes based on unconventional wisdom derived from decades of real world experience.

The fixes I recommend are ones I've used on my own projects. If a process wouldn't survive contact with a real deadline, it doesn't go in the report.

Decades of Experience

I founded Syllogistic Software in 2003 and have spent my entire career building software and managing software projects.

I have a Bachelor of Mathematics in Computer Science from the University of Waterloo, a business degree, and a Project Management Professional (PMP®) certification. That combination is what lets me bridge the gap between technical considerations and business fundamentals.

I still write code every week. That means when I recommend a fix, I know what it will take to actually ship it.