• Bug Backlog
• Product Backlog
• Sprint 1
• Sprint 2
• Wiki

Sprint planning meeting

Please document here topics to the Sprint planning meeting

• Time boxed (8 h)

• Input: Product Backlog

• Output: Sprint Backlog

• Divided into two additional time boxes of 4 h:

  • The Product Owner presents the Product Backlog and the priorities to the team and explains the Sprint Goal, to which the team must agree. Together, they prioritize the topics from the Product Backlog which the team will take care of in the next sprint. The team commits to the discussed delivery.
  • The team plans autonomously (without the Product Owner) in detail and breaks down the tasks from the discussed requirements to consolidate a Sprint Backlog.

Daily Scrum meeting

Please document here topics to the Daily Scrum meeting

• Short, daily status meeting of the team.
• Time boxed (max. 15 min).
• Stand-up meeting to discuss the following topics from the Task board.
  • What do I plan to do until the next Daily Scrum?
  • What has blocked my work (Impediments)?
• Scrum Master moderates and notes down Sprint Impediments.
• Product Owner may participate may participate in order to stay informed.

Sprint Review meeting

Please document here topics to the Sprint Review meeting

• Time boxed (4 h).
• A maximum of one hour of preparation time per person.
• The team shows the product owner and other interested persons what has been achieved in this sprint.
• Important: no dummies and no PowerPoint! Just finished product functionality (Increments) should be demonstrated.
• Feedback from Product Owner, stakeholders and others is desired and will be included in further work.
• Based on the demonstrated functionalities, the Product Owner decides to go live with this increment or to develop it further. This possibility allows an early ROI.

Sprint Retrospective

Please document here topics to the Sprint Retrospective meeting

• Time boxed (3 h).
• After Sprint Review, will be moderated by Scrum Master.
• The team discusses the sprint: what went well, what needs to be improved to be more productive for the next sprint or even have more fun.

Sprint planning meeting

Please document here topics to the Sprint planning meeting

• Time boxed (8 h)

• Input: Product Backlog

• Output: Sprint Backlog

• Divided into two additional time boxes of 4 h:

  • The Product Owner presents the Product Backlog and the priorities to the team and explains the Sprint Goal, to which the team must agree. Together, they prioritize the topics from the Product Backlog which the team will take care of in the next sprint. The team commits to the discussed delivery.
  • The team plans autonomously (without the Product Owner) in detail and breaks down the tasks from the discussed requirements to consolidate a Sprint Backlog.

Daily Scrum meeting

Please document here topics to the Daily Scrum meeting

• Short, daily status meeting of the team.
• Time boxed (max. 15 min).
• Stand-up meeting to discuss the following topics from the Task board.
  • What do I plan to do until the next Daily Scrum?
  • What has blocked my work (Impediments)?
• Scrum Master moderates and notes down Sprint Impediments.
• Product Owner may participate may participate in order to stay informed.

Sprint Review meeting

Please document here topics to the Sprint Review meeting

• Time boxed (4 h).
• A maximum of one hour of preparation time per person.
• The team shows the product owner and other interested persons what has been achieved in this sprint.
• Important: no dummies and no PowerPoint! Just finished product functionality (Increments) should be demonstrated.
• Feedback from Product Owner, stakeholders and others is desired and will be included in further work.
• Based on the demonstrated functionalities, the Product Owner decides to go live with this increment or to develop it further. This possibility allows an early ROI.

Sprint Retrospective

Please document here topics to the Sprint Retrospective meeting

• Time boxed (3 h).
• After Sprint Review, will be moderated by Scrum Master.
• The team discusses the sprint: what went well, what needs to be improved to be more productive for the next sprint or even have more fun.

Sprint planning meeting

Please document here topics to the Sprint planning meeting

• Time boxed (8 h)

• Input: Product Backlog

• Output: Sprint Backlog

• Divided into two additional time boxes of 4 h:

  • The Product Owner presents the Product Backlog and the priorities to the team and explains the Sprint Goal, to which the team must agree. Together, they prioritize the topics from the Product Backlog which the team will take care of in the next sprint. The team commits to the discussed delivery.
  • The team plans autonomously (without the Product Owner) in detail and breaks down the tasks from the discussed requirements to consolidate a Sprint Backlog.

Daily Scrum meeting

Please document here topics to the Daily Scrum meeting

• Short, daily status meeting of the team.
• Time boxed (max. 15 min).
• Stand-up meeting to discuss the following topics from the Task board.
  • What do I plan to do until the next Daily Scrum?
  • What has blocked my work (Impediments)?
• Scrum Master moderates and notes down Sprint Impediments.
• Product Owner may participate may participate in order to stay informed.

Sprint Review meeting

Please document here topics to the Sprint Review meeting

• Time boxed (4 h).
• A maximum of one hour of preparation time per person.
• The team shows the product owner and other interested persons what has been achieved in this sprint.
• Important: no dummies and no PowerPoint! Just finished product functionality (Increments) should be demonstrated.
• Feedback from Product Owner, stakeholders and others is desired and will be included in further work.
• Based on the demonstrated functionalities, the Product Owner decides to go live with this increment or to develop it further. This possibility allows an early ROI.

Sprint Retrospective

Please document here topics to the Sprint Retrospective meeting

• Time boxed (3 h).
• After Sprint Review, will be moderated by Scrum Master.
• The team discusses the sprint: what went well, what needs to be improved to be more productive for the next sprint or even have more fun.

Sprint planning meeting

Please document here topics to the Sprint planning meeting

• Time boxed (8 h)

• Input: Product Backlog

• Output: Sprint Backlog

• Divided into two additional time boxes of 4 h:

  • The Product Owner presents the Product Backlog and the priorities to the team and explains the Sprint Goal, to which the team must agree. Together, they prioritize the topics from the Product Backlog which the team will take care of in the next sprint. The team commits to the discussed delivery.
  • The team plans autonomously (without the Product Owner) in detail and breaks down the tasks from the discussed requirements to consolidate a Sprint Backlog.

Daily Scrum meeting

Please document here topics to the Daily Scrum meeting

• Short, daily status meeting of the team.
• Time boxed (max. 15 min).
• Stand-up meeting to discuss the following topics from the Task board.
  • What do I plan to do until the next Daily Scrum?
  • What has blocked my work (Impediments)?
• Scrum Master moderates and notes down Sprint Impediments.
• Product Owner may participate may participate in order to stay informed.

Sprint Review meeting

Please document here topics to the Sprint Review meeting

• Time boxed (4 h).
• A maximum of one hour of preparation time per person.
• The team shows the product owner and other interested persons what has been achieved in this sprint.
• Important: no dummies and no PowerPoint! Just finished product functionality (Increments) should be demonstrated.
• Feedback from Product Owner, stakeholders and others is desired and will be included in further work.
• Based on the demonstrated functionalities, the Product Owner decides to go live with this increment or to develop it further. This possibility allows an early ROI.

Sprint Retrospective

Please document here topics to the Sprint Retrospective meeting

• Time boxed (3 h).
• After Sprint Review, will be moderated by Scrum Master.
• The team discusses the sprint: what went well, what needs to be improved to be more productive for the next sprint or even have more fun.

Sprint planning meeting

Please document here topics to the Sprint planning meeting

• Time boxed (8 h)

• Input: Product Backlog

• Output: Sprint Backlog

• Divided into two additional time boxes of 4 h:

  • The Product Owner presents the Product Backlog and the priorities to the team and explains the Sprint Goal, to which the team must agree. Together, they prioritize the topics from the Product Backlog which the team will take care of in the next sprint. The team commits to the discussed delivery.
  • The team plans autonomously (without the Product Owner) in detail and breaks down the tasks from the discussed requirements to consolidate a Sprint Backlog.

Daily Scrum meeting

Please document here topics to the Daily Scrum meeting

• Short, daily status meeting of the team.
• Time boxed (max. 15 min).
• Stand-up meeting to discuss the following topics from the Task board.
  • What do I plan to do until the next Daily Scrum?
  • What has blocked my work (Impediments)?
• Scrum Master moderates and notes down Sprint Impediments.
• Product Owner may participate may participate in order to stay informed.

Sprint Review meeting

Please document here topics to the Sprint Review meeting

• Time boxed (4 h).
• A maximum of one hour of preparation time per person.
• The team shows the product owner and other interested persons what has been achieved in this sprint.
• Important: no dummies and no PowerPoint! Just finished product functionality (Increments) should be demonstrated.
• Feedback from Product Owner, stakeholders and others is desired and will be included in further work.
• Based on the demonstrated functionalities, the Product Owner decides to go live with this increment or to develop it further. This possibility allows an early ROI.

Sprint Retrospective

Please document here topics to the Sprint Retrospective meeting

• Time boxed (3 h).
• After Sprint Review, will be moderated by Scrum Master.
• The team discusses the sprint: what went well, what needs to be improved to be more productive for the next sprint or even have more fun.