Basics that prevent chaos: scope, sequencing, risk, and execution.
Scope
What is in and out of the project; prevents hidden expectations.
MVP
Minimum viable product: smallest version that tests value with real users.
Definition of Done
A checklist that must be true before work counts as finished.
Critical path
Longest chain of dependent tasks; it determines the project duration.
Risk register
Top risks with likelihood, impact, and mitigation/owner.
Requirements
What users need; capture as user stories or jobs-to-be-done.
Constraints
Hard limits (time, budget, tech, legal) that shape solution space.
Assumptions
Beliefs you are treating as true; track and validate them early.
Dependencies
Work blocked by other work; map them to prevent hidden delays.
Milestone
A meaningful checkpoint with a measurable outcome.
Work breakdown structure
Split work into smaller deliverables until tasks are estimable.
Estimation
A forecast, not a promise; update as you learn.
Buffer
Extra time/capacity reserved for uncertainty and rework.
Stakeholder
Anyone affected who can influence success; align expectations early.
RACI
Roles: Responsible, Accountable, Consulted, Informed (clarifies ownership).
Acceptance criteria
Observable conditions that define success for a requirement.
Change control
A way to assess and approve scope changes without chaos.
Prioritization (MoSCoW)
Must/Should/Could/Won't; forces explicit trade-offs.
Incremental delivery
Ship small slices to learn and reduce integration risk.
Feedback loop
Regular user/stakeholder feedback prevents building the wrong thing.
Retrospective
Review what happened, why, and what to change next iteration.
Success metrics
Define how you will measure success (usage, revenue, time saved, error rate).
Rollback plan
How to revert safely if a release causes problems.
Communication plan
Who needs updates, how often, and in what format.