Build delivery plan - product and sprint levels

Owned by Katsiaryna_Subach
Last updated: Jan 17, 2022 by Aleksandr Bogush
1 min read



  1. Sprint level - identify what stories should be taken by development team first to organize work in parallel without dependencies, or complete complex tasks first which might consume significant QA effort, and resolve some blockers from backlog.

  2. Product level - make sure to build delivery by preparing baseline first and only after 1-2 sprints resuming development of Frontend (as an example) with integration moving forward, i.e. ideally baseline and "on top" features should not go into the same sprint

  3. Product & Sprint level - create delivery plan based on dependencies on other parties or/and teams, i.e. create joint sessions to define interconnections beforehand or organize program increment planning to make iterative cross planning with the whole product team.

  4. When building delivery plan include QA work as obligatory step in product development, i.e. each feature should have QA task. Overall, each development activity requires QA verification. If it's complex project/product don't forget to plan UAT and IFT stages