26.04.2015 Views

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5. Captures the test tasks in TFS and links them to the QoS<br />

6. Defines the acceptance criteria for each of the test tasks.<br />

7. Schedules and assigns the tasks.<br />

• The developer estimates each development task.<br />

Important – If it looks like the tasks (developer stories) might take longer than a day<br />

or two to implement, then you should break these down into sub-stories.<br />

• The tester, provide estimation for each of the test tasks.<br />

During the Iteration<br />

• The project manager guides the iteration.<br />

• The developer, writes code for the development task, and then closes the tasks once<br />

the acceptance criteria have been met.<br />

• The tester executes the test tasks that he or she is assigned and then creates new bugs<br />

(work items) for any issues identified.<br />

After the Iteration<br />

• The project manager:<br />

1. Assesses the project progress and reprioritizes any scenarios that are incomplete<br />

from the current iteration.<br />

2. Provide a status report to stakeholders.<br />

3. Decides which scenarios should be worked on during next iteration based on<br />

their priority.<br />

• The product manager:<br />

1. Adds any newly discovered scenarios.<br />

2. Reprioritizes scenarios (where necessary).<br />

3. Together <strong>with</strong> the project manager, creates QoS requirements for the project. The<br />

QoS is linked to the scenarios.<br />

Example 2: Field Customer Engagement<br />

The following example shows how the MSF Agile process is used by a field customer<br />

engagement.<br />

New Project Through Iteration 0<br />

• The business analyst:<br />

1. Creates a short (one-page) vision statement.<br />

2. Identifies an on-site customer who can be used to provide input and creates<br />

personas for the system.<br />

3. Brainstorms scenarios (names only) <strong>with</strong> the customer.<br />

4. Prioritizes scenarios <strong>with</strong> the customer.<br />

5. Writes scenarios for the upcoming iteration.<br />

• The project manager:<br />

1. Gathers the developers together and obtains their estimates. The estimates are<br />

rough- order-of-magnitude estimates.<br />

2. Checks if priorities change as a result of costs.<br />

3. Schedules scenarios for the upcoming iteration.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!