PMI-ACP Certification: Planning and Monitoring Iterations

About this course

Planning and Monitoring Iterations on an Agile Project Welcome! This is the fifth course out of eight of the Agile PMI-ACP (Agile Certified Practitioner) Certification Program. This part is on Planning and Monitoring Iterations on an Agile Project. An iteration planning meeting In an agile project, planning occurs before each iteration starts. An iteration planning meeting should typically last for one or two hours per week included in an iteration, and should include the product owner, agile project manager, or Scrum Master, and the development team. During iteration planning, the participants adjust the priorities of user stories and estimate the development team's velocity. They then develop an iteration goal, select user stories, break the stories down into tasks, and estimate the tasks. The three key outputs of an iteration planning meeting are the iteration goal, an iteration backlog, and an iteration schedule. Creating an iteration backlog
 During iteration planning, an agile project team follows three steps to create an iteration backlog. First the team splits any overly large user stories into multiple, smaller stories. Each story should be independent, negotiable, valuable, estimable, small, and testable. Next the team breaks each user story down into development tasks. Each task should be specific, measurable, achievable, relevant, and time-boxed.  Finally the team estimates the effort required to complete each task, generally using ideal hours. Calculating the buffer To help ensure that an agile project will be completed on time, you can use various types of buffers – including feature, project, feeding, and resource buffers.