Project Manager
Mission
Section titled “Mission”Keep delivery predictable and unblocked: coordinate the team, remove impediments, manage risk and schedule, and give stakeholders an honest picture of progress. At EmeSoft the PM also carries the Scrum Master facilitation duties.
Responsibilities
Section titled “Responsibilities”- Facilitate the Scrum ceremonies and protect the team’s focus and Sprint Goal.
- Remove impediments - anything blocking the team that isn’t theirs to fix.
- Track schedule, budget, scope, and risk; escalate early.
- Coordinate dependencies across teams, vendors, and environments.
- Produce status and risk reporting for stakeholders.
- Coach the team on the process and drive continuous improvement.
Inputs
Section titled “Inputs”| Input | From |
|---|---|
| Sprint plan & board state | Dev Team |
| Blockers & risks | Whole team |
| Priorities & deadlines | Stakeholders (Product Owner) |
| Velocity, burndown, cycle-time data | Tooling (Jira/Azure DevOps) |
Outputs
Section titled “Outputs”| Output | To |
|---|---|
| Status & risk reports | Stakeholders |
| Cleared blockers & decisions | Dev Team |
| Updated plan / forecast | Stakeholders (PO), team |
| Retro actions tracked to closure | Whole team |
AI tools & how we use them
Section titled “AI tools & how we use them”The PM uses AI mainly to see problems sooner and cut reporting time.
- Jira AI / Azure DevOps Copilot: auto-summarize sprint progress, flag stories at risk of spillover, and draft the burndown narrative. The PM validates and edits.
- Claude / ChatGPT (reporting & comms): turn raw board exports into a stakeholder status update, a risk register entry, or a crisp escalation email. Prompt pattern: “Here is the sprint export. Draft a 1-page status: progress vs Sprint Goal, top 3 risks, decisions needed.”
- AI meeting assistants (Copilot in Teams / Fireflies): transcribe and summarize meetings, extract action items with owners, and post them automatically.
- Predictive analytics (in Jira/ADO): forecast completion dates and highlight scope creep using historical velocity. Used as an early-warning signal, not a commitment.
Collaboration
Section titled “Collaboration”flowchart TB
PM[Project Manager]
PM -->|facilitates| CER[Ceremonies]
PM -->|clears| BLK[Blockers]
PM -->|reports to & aligns with| ST[Stakeholders / Product Owner]
PM -->|coordinates| TEAM[Dev Team]
ST -. owns 'what' .- PM
PM -. owns 'flow' .- ST
The PM and the stakeholders (as Product Owner) are partners: the stakeholders own what and why (value, priority), the PM owns flow and delivery (coordination, risk, schedule). The PM and BA together are the team’s interface to the stakeholders.
Definition of Done for this role
Section titled “Definition of Done for this role”- Ceremonies happen on cadence and stay within their timeboxes.
- Blockers are tracked and resolved or escalated within SLA.
- Stakeholders have a current, accurate view of status and risk.
- Retrospective actions from last sprint are closed or carried with a reason.