I make sure what gets built is what was asked for needed.

Statistics Canada, the national statistics agency · 2018 – 2020

Collection Management Portal

Critical epics and features for a core system of Canada’s 2021 Census of Population, used by more than 20 million users.

I led elaboration meetings with stakeholders to define scope, objectives and success criteria, then translated business requirements into epics, features, user stories, use cases and acceptance criteria, documented in Confluence within a Behaviour-Driven Development model.

After presenting the finished epics and features to management, I led the hand-off sessions that improved the development team’s understanding and accelerated implementation.

Statistics Canada, Systems Integration Authority · 2020 – 2021

Two systems, one agreement

The integration analysis between two major systems, ahead of the 2021 Census.

I planned and moderated working sessions with both teams to find where the systems met and to understand each side’s existing process flows. The result was a BPMN model pinpointing the integration points, and an Interface Control Document that captured the agreed process and helped bring both teams to agreement.

Statistics Canada, Business Relationship Management · 2021 – 2022

A route to funding

An envisioning process flow that gave teams a structured way to bring new project ideas to management, and a better chance of securing funding.

I designed the flow in Enterprise Architect. Alongside it, I gathered and documented requirements for upcoming projects in the envisioning phase, preparing them to be presented to management.

Department of National Defence, CHRO · 2025 – present

Rebuilding how a team delivers

A new BA and UX team, and a move from waterfall to agile, team-based delivery.

When I joined, I led a team of 12 developers and there were no business analysts. Each BRD went to a single developer, who chased the detail with clients, designed the interface and built the application alone. To begin with, I did the business analysis myself.

Then I created a BA and UX team and hired its analysts and designers. I defined how it works, from BRD review and weekly elaboration sessions with clients through to release planning and change management, and designed the standard templates for its product requirements documents (PRDs), which are structured as epics and features. BRDs are now broken into epics, so developers start building as soon as the first one is ready, while requirements and design for the next run in parallel in biweekly sprints.

Today I lead that team across six initiatives at once. Clients see progress and design options every week, and in an illustrative three-release example the same work finishes about four months sooner.

Department of National Defence, CHRO · 2025 – present

From document to backlog

An AI agent that turns epic and feature documents into linked Azure DevOps work items.

Once an epic or feature document was written, the work items behind it still had to be created in Azure DevOps by hand.

I built and launched an agent in Microsoft Copilot Studio that generates them directly from the documents the team already writes: the epic, its features, and the product backlog items and bugs beneath them, each linked to its parent. It replaced manual work item creation.