scrum Questions

If a Scrum "increment" is to be "done" by the end of the "sprint", where "done" means usable/releaseable, I assume testing has to be part of the sprint. Since sprints are not supposed to last more than a month, depending on the scope of the sprint goals, testing is either ongoing or occurs just before the end of the sprint. It seems on-going has to be the answer, but regressive testing of the new increment with previous incrments can grow into an increasing work item.

Does anyone with experience in this have thoughts to share so I can understand better how this is done?

We use Team Foundation Server for development and testing. Our Director has told our scrum master to go to 1-week sprints AND remove testing tasks from the product backlog to change the definition of "Done". We could use a suggestion on how to ensure we get testing tasks assigned, and track their progress, when our only tools are TFS and Google Docs. Having been forced to use Google Docs to track testing in the past, I expect issues trying to share -- for instance -- a spreadsheet to do this. Tasks could be forgotten or missed. Updates may go uncommunicated.

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.