From WikiEducator
Jump to: navigation, search
Convenor: Giorgos Saslis
  • Andriy Stekhnovych
  • Peter Lawrey
  • Themistoklis Dakanalis
  • Jesper Udby
  • Ioannis Kostaras
  • Marek Nowicki
  • Ioannis Christodoulou
  • Giorgos Saslis
Scrum - JCrete2013

Free content media streamed from Wikimedia Commons

Download: .ogg

Initial discussion on what we actually apply from the Agile/Scrum principles? The …"scrum BUT"... Mentions that we don't always follow all steps in the Scrum process, and suggestions from others who do that they work really well. (e.g. sprint retrospective, sprint review, sprint grooming).

Hours vs. user story points? what unit do people use to measure progress? Most people use hours. User story points good as a measure of comparison between different user stories.

What do we do for user stories that take longer? do we leave them in the sprint? do we do them later? Concerns expressed on contingencies, and how they are treated. Are they added to the sprint backlog as new items, or are they put on the product backlog? People said it's mainly looked at on a case-by-case basis, but some times people said it's not possible to leave behind. They take some time off of the pre-estimated time for grooming, etc. to cover for such tasks.

What are typical team sizes? Most people said around ~5 people

Team composition? Mainly developers, but in some cases, both testers & developers (each might have their own sprints - or both on same team... but this has some overhead).

how do we take testing into account? user acceptance tests

performance and its importance: functional (?) requirement What is the ideal sprint length? Short discussion on short vs. longer sprints (from 2 to 6 weeks), but general consensus that sprints should be 2-4 weeks.

Concerns raised about merging code from different teams... takes long - especially when teams' sprints don't end at the same time.

Scrum as the main agile development technique that everyone uses.

How can we improve our estimates? --experience, grooming, importance of sprint retrospectives

  • Important to do sprint retrospectives - especially for inexperienced teams.
  • Sprint grooming also helps for some refactoring and research tasks before going into the next Sprint.