week 2 summary

Gergő Pintér, PhD

gergo.pinter@uni-corvinus.hu

scrum team

  • optimally 3 to 9 people
  • cross-functional
  • self-organizing

roles

  • scrum master
    • responsible establishing scrum as defined in the Scrum Guide
      • by helping everyone understand the theory and practice, both within the scrum team and the organization
    • responsible for the scrum team’s effectiveness
  • product owner
    • responsible for maximizing the value of the product resulting from the work of the scrum team
    • also responsible for effective product backlog management
  • developers

sprint planning

  • initiates the sprint
  • maximum of eight hours for a one-month sprint
  • define a sprint goal
    • definition of done
  • it is up to the developers how to turn product backlog items into increments

sprint

  • 1-4 week long
  • considered a short project
  • turns backlog items into increments
  • includes daily scrum

sprint review

  • scrum team presents the their work to the stakeholders
    • increment is evaluated
  • the attendees collaborate on what to do next
  • maximum of four hours for a one-month sprint

sprint retrospective

  • concludes the sprint
  • maximum of three hours for a one-month sprint
  • the scrum team discusses what went well/bad, what problems encountered

kanban

  • uses a visual workflow
  • pull-based system
    • no task in the workflow without request
  • uses columns for states of the product
  • defines conditions when to move a task between columns
  • conditions flow
    • no iterations (sprints)
    • no roles
  • encourages to improve the workflow