Role: Business Systems Analyst (BSA)
Tools: Microsoft Copilot, Azure DevOps, Salesforce, Gainsight
Domain: Cloud Migration · Customer Success Operations · Cross-functional Program Management
Status: Phase 2 ongoing — target delivery in FY27 Q1
Time saved: ~3–4 days of planning condensed into a single focused session
Dynamic roadmap demonstrating Agile project timeline, designed with Claude.ai
How Copilot Changed the Planning Process
I fed Copilot the project context and constraints explicitly — not a generic prompt, but the specific business situation, team bandwidth realities, and sequencing logic. From there, it generated a structured work breakdown that I could validate, adjust, and refine rather than construct from scratch.
The difference: instead of spending three days building the structure, I spent one session building the structure and the rest of my time on judgment — validating sub-phases against actual DataOps capacity, stress-testing the sequencing against the dev-light constraint, and framing the work breakdown so CS Leadership and DataOps could review it in their own language.
Both stakeholder groups approved the agile roadmap and actionable ADO board on first review. No revision loops.
<aside> 💡
What Copilot contributed:
Rapid structured breakdown · User Story language · ADO-ready formatting · Speed
What I contributed:
Business context · Constraint logic · Stakeholder framing · Every decision reviewed and owned
</aside>
What I’d Do Differently
Involve DataOps earlier in Phase 1. Some assumptions about available QuickSight metrics had to be corrected mid-discovery. Earlier DataOps presence in the audit would have sharpened the scope before work began.