365Connect — a Microsoft 365 product, owned end to end

Problem

Turn ad-hoc SharePoint and Microsoft 365 development work into 365Connect: a maintained product with its own roadmap, architecture, and delivery process — not one-off work rebuilt for every client.

My role

• Lead developer and product owner: roadmap planning, architecture, feature development, and technical documentation.
• Mentored other developers contributing to the product.

Approach

• Set the technical architecture across SPFx, Azure Functions, and Microsoft Graph integrations.
• Introduced a structured feature-delivery pipeline in Azure DevOps (backlog, sprints, releases) to replace ad-hoc delivery.
• Maintained technical documentation so the product could be extended by other developers, not just the original author.

Outcome

• 365Connect runs as an ongoing Microsoft 365 product with a maintained roadmap, rather than bespoke client work.
• The Azure DevOps delivery workflow introduced for this product improved delivery consistency and documentation quality.