A few weeks ago I managed to steal a couple of hours of Ken Schwabers' time and recorded a series of 10 minute podcasts where Ken answers some of the more frequently asked questions about the Scrum Process. The FAQ will ship, in written form, as part of the documentation for "Agile Software Development with Scrum" for Team System. If you haven't listened to them already, Part 1 and Part 2 of the series are still available.
The questions Ken answers in Part 3 are listed below:
- Why is everything in Scrum time-boxed?
- Why does Scrum say nothing about engineering practices?
- How do I measure the performance of the team?
- How do I measure the performance of a team member?
- What is the benefit of doing a Sprint Retrospective?
- How to fix a bug in a Sprint?
- How can you get buy-in for the use of Scrum?
- What kind of reports do I supply to management?
- Why would you cancel a Sprint?
- Can scrum work without fulltime commitment from one or more of the stakeholders?
- Do Scrum teams need to be co-located?
- Doesn't Scrum mean we have to throw away the best IT practices we've developed over the last 20 years?
- What's the cost of change? Will the introduction of Scrum cause more problems than it solves?
- Is there a downside to changing the make up of a team after the Sprint has started?
- How do you scale Scrum to larger projects?
