Checklist: Project Setup Readiness Checklist (Dev Perspective)

Purpose

To ensure all essential components of a project are in place and accessible before developers begin active work.

This prevents wasted cycles, blocked tasks, and inconsistent environments.


Checklist Structure

Section 1 – Repository & Codebase

ItemStatusNotes
Project repo created (GitHub/GitLab/Bitbucket)⬜Repo link:
Repo has README with setup instructions⬜Must include stack, env setup
.gitignore configured⬜Prevents committing secrets/node_modules/builds
Branching strategy documented (Doc: Git Strategy)⬜feature/*, develop, main
Sample commit & PR tested⬜Ensures CI/CD triggers

Section 2 – Environment Setup

ItemStatusNotes
.env.example file present⬜Contains placeholders for API keys, DB creds
Local build runs without errors⬜Run npm run dev or equivalent
Docker/DB setup tested⬜Containers spin up successfully
Default dev account provided⬜Username/password documented
Test API endpoint verified⬜/health or equivalent

Section 3 – Access & Tools

ItemStatusNotes
Repo access granted to all devs⬜Verify permissions
PM tool (Jira/ClickUp/Linear) configured⬜Backlog visible
CI/CD tool linked to repo⬜Build pipeline passes
Staging environment accessible⬜URL + credentials provided
Secrets manager configured (Vault/1Password)⬜Tokens not shared via chat

Section 4 – Documentation & Guidelines

ItemStatusNotes
System architecture diagram available⬜High-level overview
API contract/specification shared⬜Postman/Swagger file
Coding standards documented⬜ESLint/Prettier/Style guides
Dev–QA Handoff process documented⬜SOP link
Security guidelines shared⬜RBAC, access policy

Section 5 – Team Setup

ItemStatusNotes
Project lead assigned⬜Name/contact:
Tech buddy assigned (for new devs)⬜Name/contact:
QA lead assigned⬜Name/contact:
Slack/Teams channel created⬜Channel link:
First sprint backlog ready⬜At least 1 sprint planned

Usage Notes

  • Must be completed before the sprint start.
  • Devs/Leads own the checkmarks, PM/Lead validates readiness.
  • Any missing item must have a Jira ticket created before kickoff.

Outcome

  • Ensures developers never start work in a half-ready environment.
  • Reduces delays caused by missing access, env configs, or unclear guidelines.
  • Provides an audit trail of readiness for retros.