Scrum-Team

What are the main responsibilities of Scrum Team?

  • Executing sprint planning together with scrum master and PO
  • Organize daily scrum or stand up meeting
  • Work on sprint backlog
  • Give accurate effort estimate of the work (User story, task issue) they are working on
  • Update the effort remaining so burndown chart can be drawn to shown the real team progress
  • Identify blocking /impediment item which causing the team to function effectively
  • Ask for more information if the user stories they are working on not clear enough
  • Every scrum team member should understand the goal of sprint to achieve
  • Ideal Scrum team size is 5-8 team members
  • If the team size is greater than 8 members, you may split the scrum team into smaller teams to avoid complexity. It is easy to plan the sprint planning, review, and daily scrum meeting with an ideal size team.
  • Smaller scrum team is much easier to manage and they are much more effective
  • Pizza example [amazon]

What is the difference between Scrum and Kanban?

Kanban and Scrum focus on releasing software early and often and require highly collaborative and self-managed teams.

Scrum Kanban
Scrum processes place heavy emphasis on schedule. The scrum team is provided with a prioritized list of story points that need to be completed to deliver a shippable product. The team must decide how many of the points they feel can be completed within one sprint. Anything outside the scope they commit to must wait for the next sprint. Whereas, On a Kanban team, there are no required time boxes or iterations. While the Kanban method is iterative in nature, the continual improvement is expected to occur in an evolutionary fashion as work is continually completed. The limitations placed on various conditions in the workflow will be regulated early in a team’s (or organization’s) use of Kanban until an optimal set of limits is arrived at to keep the flow steady and efficient.
In scrum there are at least three roles that must be assigned in order to effectively process the work: the Product Owner, Scrum Master, and Team Members. Each role has its own set of responsibilities, and they must work together to achieve an orderly and efficient balance. Whereas in Kanban, no roles are prescribed, but roles theoretically evolve with the needs of the project and the organization.
On a Scrum board, the columns are labeled to reflect periods in the workflow beginning with the sprint backlog and ending with whatever fulfills the team’s definition of done. Whereas on a Kanban board, the columns are likewise labeled to show workflow states, but with one vital difference, they also publish the maximum number of stories allowed in each column at any one time.