Keynote: Scaling Scrum
Summary
Sees lots of teams being successful with Scrum in small projects, but people tend to get lost when they look at scaling up… It’s an emergent field. The challenges – highly collaborative, need the team involved in the planning, risk of losing easy way of resolving issues, hard work! Product Owner – workload, being at all the meetings Establishing Sprint goal, distributed team members at Scrum meeting, Increment has dependencies on other teams, emphasis on electronic management of sprint backlog (remoteness), political impact on product backlog (more at stake on big project), sprint review – who’s in it?, combining lessons from teams in retrospective. (assumes you are starting a fresh project – Rachel sees lots of organisations getting benefit from Scrum on existing products) For existing products – extract a virtual team to focus on forward plan, and another to focus on integration, keeping it all working. May need communities of common disciplines e.g. DBAs Think about series or parallel for multiple daily Scrum meetings Keep clear about “levels” in plans – vision, releases roadmap, themes per sprint, product backlog, sprint backlogs per team.