Conventional Planning

Project planning as the baseline approach, completely human-driven. This encompasses defining project scope (goals, deliverables, success criteria), resource planning (team structure, timelines, budgets), and work organization (epics, milestones, roadmaps).

You can plan using different approaches depending on your context: traditional waterfall (detailed upfront planning), iterative/agile methods (continuous adaptation), or hybrid approaches. Each has its place depending on project constraints, industry regulations, and team dynamics.

Common Approach Today: Iterative Planning

The most common practice in software development today emphasizes short-term cycles and continuous adaptation. Teams plan in sprints or iterations (typically 1-6 weeks), allowing them to incorporate real feedback and adjust course quickly. The key is creating just enough plan to start, then evolving it based on what you learn.

This approach includes:

• Short-term planning cycles

  • Sprint planning (1-4 weeks)
  • Iteration planning (2-6 weeks)
  • Release planning with flexible scope

• Feedback loops from other phases

  • Analysis: Validate requirements through stakeholder discovery
  • Design: Test feasibility with architecture spikes
  • Coding: Learn from MVPs, prototypes, and proof-of-concepts

• Continuous adaptation

  • Adjust priorities based on user feedback
  • Refine scope as you discover new information
  • Embrace uncertainty instead of fighting it

• Validation and alignment

  • Regular planning reviews with stakeholders
  • Feasibility and capacity checks
  • Team alignment meetings

See the Resources section below for recommended books and guides on planning practices.