1.
How the software will be tested
2.
How the stakeholders will verify the deliverables
3.
A list of all artwork that will be created
4.
Which is NOT an output of a Scope Management process?
5.
Testing the most recent build, I just noticed that if the player presses x–x–z–a–Shift–Shift–Space in that order, Bessie does the Charleston—it’s a really funny easter egg the developer just added at random.
6.
The printer just told us that she could also do silk screen T-shirts for everybody as a ship gift. Let’s get our design team to do some special artwork for them. We can have everybody’s names written in cows!!! Then we could use the same artwork on posters that we put around the office—oh, and coffee mugs for new people, too
7.
We need to create a screensaver to market the game. Let’s kill two birds with one stone and test out a brand new graphics engine on it. Oh, and we’ll need a story for the screensaver, so we should write that too. Of course we have to recruit some killer voice talent for the screensaver. Memorable names sell more games.
8.
We should add a calculator for tracking gallons of milk collected in the game. It will be really easy. We could even release the calculator as a separate add-in, and we could probably make it full‑featured enough for the folks developing the game down the hall to use it too.
9.
A description of how the WBS is created
10.
Which of the following is TRUE about a work breakdown structure?
