Before a software team starts delivery, it needs agreement on how work will move from idea to launch. A working model is that blueprint: the methodology, processes, and recurring activities the team will use to plan, collaborate, and deliver. Defining it helps people stay aligned while working toward a high-quality result. section 10.1.3
Choose a foundation that fits the work:
- Agile emphasizes iterative development, flexible planning, customer collaboration, and continuous improvement. section 10.1.3
- Scrum organizes work into sprints and uses stand-ups, planning, reviews, and retrospectives to support communication and adaptation. section 10.1.3
- Kanban visualizes work as it moves through a process and limits work in progress to improve flow. section 10.1.3
A framework alone does not settle who owns each decision or requirement. Clarify responsibilities with stakeholders and seek their agreement; a RACI chart can make ownership visible. As a kickoff check, ask: Does everyone know how work will be managed and who is responsible for what? section 10.1.3
