About
Not a resume. A record of what got built.
Twenty-five years in software delivery: two decades of hands-on development underneath a decade of product ownership, project management and team leadership. National election infrastructure, government transparency portals, enterprise platforms, gaming titles, e-learning systems, and AI-driven products for regulated environments.
The pattern across all of it is the same: domains where correctness is not negotiable, deadlines that cannot move, and requirements that shape the build rather than decorate it. Specifications are written personally, close enough to the technical detail that engineering never has to reverse-engineer intent from a ticket.
How the work gets done
Requirements & Specification
Discovery and grooming run directly with stakeholders. Specifications and user stories written with acceptance criteria and edge cases handled up front, not discovered mid-sprint.
Systems Analysis & Design
UML class, use-case and sequence diagrams. Database structure, relationships and data types proposed as part of the spec, not left for engineering to guess.
Delivery
Scrum, Kanban and SAFe in practice — sprint planning, backlog ownership, cross-team dependencies, release readiness and UAT.
Stakeholder & Risk
Single point of accountability to leadership and clients. Risks tracked with probability, cost and an owner — not just logged and forgotten.