Scrum and delivery
I was Scrum Master for DevHawks, a six-person student team, on a client website redesign: sprints in Jira, client communication, and a usability audit.
Scrum Master for a six-person team that shipped a client’s site redesign.
Ran sprints in Jira, handled client communication, and led a usability audit of the service pages for Woodland Country Manor.
How I run a sprint
1
Discovery & Product Backlog
Partner with Product Owners and users to translate high-level business goals into structured Epics and INVEST-compliant User Stories with concrete Acceptance Criteria.
- Uses:
- Jira / Confluence, User Story Mapping, Acceptance Criteria
- Produces:
- Prioritized Product Backlog
2
Sprint Planning & Estimation
Facilitate Sprint Planning ceremonies. Guide cross-functional developers through Planning Poker estimations, establish Sprint Goals, and commit to realistic team capacity.
- Uses:
- Planning Poker, Team Capacity Planner, Sprint Goal Alignment
- Produces:
- Committed Sprint Backlog
3
Sprint Execution & Blockers
Host daily 15-minute Standups to track progress against the Sprint Burndown chart. Proactively shield the engineering team from outside noise and resolve technical blockers.
- Uses:
- Daily Standup, Burndown Chart, Blocker Removal Matrix
- Produces:
- Steady Sprint Velocity
4
Sprint Review & Demo
Demonstrate potentially shippable product increments to key stakeholders. Gather feedback, validate against Definition of Done (DoD), and update backlog priorities.
- Uses:
- Stakeholder Demo, Definition of Done Checklist, Feedback Logs
- Produces:
- Validated Product Increment
5
Sprint Retrospective
Lead team Retrospectives using Start/Stop/Continue frameworks to surface team friction points, implement actionable process improvements, and elevate team morale.
- Uses:
- Retrospective Board, Action Item Tracker, Continuous Improvement
- Produces:
- Actionable Team Retro Plan