Sprint Structure

Every Sprint Package will ALWAYS have one sub-package named "QA" at the top, followed by multiple sub-packages usually representing a project or client.

QA Sub-Package

The QA package will have all the tasks that need to be tested for this sprint. Any QA will ALWAYS go in the "QA" package, and NOT the client package.

You'll notice that the screenshot shows a testing task that is from the Planet Express client, but it is not under the "Planet Express" package. QA will be working on many different projects in a Sprint. If we kept all QA tasks with their Sprint Client Package, the priority might not be correct. You'll notice that Acme Corporation is higher than Massive Dynamic which is higher than Planet. If we didn't have a special QA package, all Acme Corporation QA tasks would always end up being more important than Planet Express QA tasks. It is up to the Account Manager or Project Manager to know what is more important. We may have a website launching that needs to be QA before another app.

Client/Project Sub-Packages

Client (or sometimes Project) Sub-Packages will contain a top down ordered lists of tasks that will need to be completed during the sprint. Tasks should only be in the Sprint Package if they are scheduled to be worked on during that time frame.