This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.

View e-Privacy Directive Documents

You have declined cookies. This decision can be reversed.

You have allowed cookies to be placed on your computer. This decision can be reversed.

To Dos

sdPP Element Description

To Dos:

  • Size of each team from 5 to 9 people.
  • Dedication of the team full time.
  • Meetings begin promptly on time.
  • They punish people who are late to a meeting.
  • Daily meetings are held in the same location and same time every day.
  • Planning meetings will last no longer than 8 hours.
  • It should minimize the number of goals / requirements that the team works simultaneously.
  • requirements will be completed first to give more value to the customer.
  • The team should have some criteria agreed on the implementation process of the task.
  • Requirements not be considered completed another requirement planning.
  • For Sprint planning is necessary to have available working capacity of the team.
  • The organization has some potential resources to carry out the sprint.
  • Whenever possible, the product owner must have worked previously with the team already. Thus its previous estimate of how much of the product backlog may develop in the sprint will be quite tight.
  • The team has a knowledge of the technologies, business and product enough to make estimates based on "expert judgment", and to understand the concepts of business that exposes the product owner.
  • Provide the necessary licenses to work on computers.
  • Provide rooms prepared for working with agile methodologies.

Not to Dos:

  • Laying the daily meeting attendees.
  • Change the objectives / requirements of the current iteration.
  • Solve problems in daily meetings.
  • Show the customer requirements that are not finalized.
  • The duration of a daily meeting did not exceed 15 min.
  • The Daily Scrum is not for problem solving and team members only, Scrum Master and Product Owner can talk.
In the sdPP model, a set of “to-dos” is given with recommendations based on the best practices and lessons learned. This “to-dos” list tries to establish the tacit knowledge based on experience about the methodologies, reference frameworks and best practices. A “to-do” is neither an activity nor a part of the workflow (i.e. “work in pairs” cannot be an activity).
Copyright © 2017 Diego Martín. All Rights Reserved.