SOP: Developer Task Pickup & Execution Ritual

Purpose

To standardize how developers pick up and execute tasks from the backlog, ensuring consistent workflow, traceability, and faster delivery without blockers.

Scope

• Applies to all developers working on features, bugs, spikes, or chores.
• Used by Developers, Tech Leads, and PMs.
• Covers task pickup → execution → daily rituals → status updates.

Objectives

• Ensure no task is started without clarity and readiness.
• Keep developers aligned with sprint goals.
• Provide a repeatable execution ritual that avoids delays.

Step-by-Step Process

Step 1 – Pre-Pickup Validation

• Confirm task meets Definition of Ready (DoR) from grooming (EPIC 3 – Doc 2).
• Ticket must have:
  • Clear title & description.
  • Acceptance criteria.
  • Linked designs/API contracts (if applicable).
  • Estimate & priority.
• If missing info → raise in backlog channel before pickup.

Step 2 – Announce Task Pickup

• Move task in PM tool → “In Progress”.
• Post pickup note in dev channel:
  • Ticket ID & link.
  • Short summary of scope.
  • Dependencies (if any).

Example Slack update:

Picking up DEV-145: Add export to CSV in dashboard.  
Depends on API contract #ADR-12. ETA: 2 days.

Step 3 – Execution Ritual

1. Create branch → follow branching strategy (EPIC 3 – Doc 3).
2. Example: feature/DEV-145-export-csv.
3. Daily Dev Ritual (per task until completion):
   • Morning standup: confirm task status.
   • Update ticket with latest progress.
   • Push code daily (never hold local >24h).
   • Run unit tests locally before pushing.
   • Document blockers in ticket.

Step 4 – Mid-Task Sync (Optional)

• For tasks >2 days, do a mid-task sync with buddy/lead.
• Share:
  • What’s done so far.
  • Risks or unknowns.
  • Plan for completion.

Step 5 – Completion Ritual

• Verify locally: build + unit/integration tests.
• Push branch → create PR with template.
• Update ticket to “Code Review” status.
• Notify reviewers in channel.
• Attach Dev→QA handoff notes (if complete).

Step 6 – Post-Completion Update

• After merge:
  • Move ticket to “Ready for QA”.
  • Confirm build deployed to staging.
  • Post short summary:
  • DEV-145 merged to develop.
  • Feature flag: export_csv.
  • Available in staging build #202.

Roles & Responsibilities

Governance

• DoR Rule: No task starts until DoR checklist is satisfied.
• Work-in-Progress Limit: Devs may not hold >2 tasks simultaneously.
• Daily Update Rule: Tickets must reflect progress daily.
• Escalation: If blocked >1 day → escalate to Lead/PM.