Scrum Development Blog » sprint http://blog.3back.com Better teams make better products. Sun, 22 Aug 2010 18:55:29 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 How do you fill a sprint? http://blog.3back.com/scrum-questions/how-do-you-fill-a-sprint http://blog.3back.com/scrum-questions/how-do-you-fill-a-sprint#comments Tue, 09 Feb 2010 02:11:37 +0000 The 3Back Team http://blog.3back.com/?p=97
  • You get past work experience. And calculate the amount of work the team can handlestory fill sprint epic too big
  • Get estimates from the team and double the number they give you to determine work load.
  • Meet with each individual and see how much work they can take on. Build a sprint plan from that information. Then gather everyone, show the sprint plan and kickoff the team sprint.
  • Use the PO/SM powers to challenge the team to take big bites. Get as much loaded in the sprint as possible. The PO/SM can form a powerful pincer to overcome resistance.
  • This is sprint planning.  You commit one story at a time. Make sure the team is committing to sharp definitions of done.

    • Comment: After a Story is committed to, the Team (with the PO in the lead) has the option to reprioritize the Story list, and the Team takes the next one to consider. Once again, the Team comes to the “doneness” Agreement and commits to adding the Story to the list of already-committed-to Stories. This process is repeated until the Sprint is “full” and the Sprint Plan is complete.

    ]]>     http://blog.3back.com/scrum-questions/how-do-you-fill-a-sprint/feed 0     When is a story too large for a sprint? http://blog.3back.com/scrum-questions/when-is-a-story-too-large-for-a-sprint http://blog.3back.com/scrum-questions/when-is-a-story-too-large-for-a-sprint#comments Thu, 04 Feb 2010 02:06:19 +0000 The 3Back Team http://blog.3back.com/?p=91
  • too big for sprintIt is never too large for the sprint. The team must learn how to meet business expectations.
  • The team cannot agree on which stories to work  on during the sprint
  • The product owner has prioritized the story into sprint planning without any written definition of done
  • When the team cannot agree on how to commit to the story
  • Teams are inherently anxious; SM/PO must challenge the team and not accept no for an answer.
  • Make the sprint bigger so the story fits.

    • Comment: The Team may not be able to commit to a story, or might noteven be able to agree on “done.” This makes the story in question is an epic, by definition, and the Team must decide what to do. Typical choices include committing to an Analysis Story to figure out what to do about the epic, or extracting a smaller story from the epic to do instead (putting the remainder back on the backlog), or skipping the story altogether and moving to the next one. Bottom line: We need a sense of movement to understand what the team can and cannot do. Biting off chunks of work that are too large obscures movement and makes throughput / velocity that much harder to understand. Use the team’s ability to commit to understand the work that the  story represents.

    ]]>     http://blog.3back.com/scrum-questions/when-is-a-story-too-large-for-a-sprint/feed 0     Should the team be allowed to drop the retrospective? http://blog.3back.com/scrum-questions/should-the-team-be-allowed-to-drop-the-retrospective http://blog.3back.com/scrum-questions/should-the-team-be-allowed-to-drop-the-retrospective#comments Tue, 02 Feb 2010 01:50:23 +0000 The 3Back Team http://blog.3back.com/?p=86
  • sad scrum teamsYes, It’s their process why not?
  • No, explain to them and work through why the retrospective is so important.
  • Maybe, if they are no longer a team then why continue with Scrum?
  • Only do retrospectives once a quarter and build up a good list of things to change.
  • Yes, the process will take care of itself we don’t need to watch it that closely. After all it’s common sense!

    • Comment: Of things to watch out for and not allow this is high on my  list.  It boils down to this rule: If the team is not doing a retrospective then they are not doing scrum. The retrospective is where the team takes formal ownership of their process. In these situations I crack shins, and kick knee caps and generally do what is necessary to ensure they continue doing a retrospective. Without that we often see teams fall into “it’s not my fault”  because “x” told me to. In some cases “x” is the process that no-one owns, imagine the process that gets created by someone who decides to own it but, does not do it themselves!.

    Retrospective is an external constraint that must be demanded of the team. There are many ways to run a good retrospective, ScrumMaster rise to the challenge and support your team.

    ]]>     http://blog.3back.com/scrum-questions/should-the-team-be-allowed-to-drop-the-retrospective/feed 0     When should a sprint end? http://blog.3back.com/scrum-questions/when-should-a-sprint-end http://blog.3back.com/scrum-questions/when-should-a-sprint-end#comments Sat, 30 Jan 2010 01:40:15 +0000 The 3Back Team http://blog.3back.com/?p=69
  • We have consumed all the work we said we would in our sprint planning
  • All of the work has been completed.
  • Both the team and the product owner agree it should end.
  • The amount of time specified for the sprint has run out

    • Comment: Set a time-box and stick to it. Failing to adhere to the time boxes for your sprint is a badusing time boxes is best practice habit. Without time-boxes we rapidly loose our sense of predictability and the amount of complexity we tackle in each bite drifts upward. Teams become fragmented and loose cohesion. This is a strong rule but, by no means an absolute. Be smart when you vary your timebox and you really need a disciplined experience well formed team to carry this off.

    ]]>     http://blog.3back.com/scrum-questions/when-should-a-sprint-end/feed 0