AGILE PROJECT MANAGEMENT WITH TEAM FOUNDATION SERVER 2010 Brian Keller Microsoft
MANUAL TESTING WITH MICROSOFT TEST MANAGER 2010 Philosophy and Design Goals Microsoft Test Manager Test Plans Test Case Management Authoring Tests Running Tests Fast-Forward for Manual Testing Introduction to Coded UI Tests Tuesday| 3:45 PM – 5:00 PM Mediteranea 2
TEST AUTOMATION WITH VISUAL STUDIO 2010: CODED UI TESTS AND LAB MANAGEMENT Advanced Coded UI Tests Lab Management Build-Deploy-Test Best Practices Getting Started Wednesday | 9:45 AM – 11:00 AM Europa 2
AGILE PROJECT MANAGEMENT WITH TEAM FOUNDATION SERVER 2010 Backlog Management Iteration Planning Running the Sprint Project Server Integration Team Foundation Server vNext
I WORK HERE…
…ON THIS…
…AND THIS.
I BLOG HERE:
INDIVIDUALS AND INTERACTIONS over processes and tools WORKING SOFTWARE over comprehensive documentation CUSTOMER COLLABORATION over contract negotiation RESPONDING TO CHANGE over following a plan THE AGILE MANIFESTO
Product Backlog Sprint Backlog Sprint Potentially Shippable Increment
Product Backlog 1 8 Priority 5
Product Backlog
Acceptance Criteria I can search for …. I can pay with a …. I can view and edit … Product Backlog
DEMO Backlog Management
Product Backlog Sprint Backlog Sprint Potentially Shippable Increment
5 8 5 Product Backlog Sprint Backlog 3
Product Backlog Sprint Backlog
Product Backlog Sprint Backlog
Product Backlog Sprint Backlog TOO BIG!
Product Backlog Sprint Backlog COMMIT!
DEMO Iteration Planning
Product Backlog Sprint Backlog Sprint Potentially Shippable Increment
Product Backlog Sprint Backlog
Product Backlog Sprint Backlog
Product Backlog Sprint Backlog
Product Backlog Sprint Backlog
Product Backlog Sprint Backlog Sprint Potentially Shippable Increment
Product Backlog Sprint Backlog
Product Backlog Sprint Backlog What worked? What didn’t work? What should we change?
Product Backlog Velocity Sprint 1: Sprint 2: Sprint 3: Sprint 4:
Product Backlog Priority
Product Backlog Sprint Backlog Sprint Potentially Shippable Increment
Burndown chart tracks remaining and completed work
Detailed sprint progress is tracked on the project portal The burndown shows the team on track… And almost half of the tasks remain open But the team hasn’t closed any of the three stories…
Test are passing… But bugs are climbing steadily The portal brings data together so it can be analyzed to ensure success on a sprint
Rich set of reports track progress
1.Define done 2.Fail fast 3.Understand your team’s velocity 4.Write unit tests – always 5.Bugs are real work 6.Code with confidence 7. Always deliver value 8. Finish what you start 9. Autonomy, mastery, purpose 10. Do the right thing… at the right time 11. Plan until you need to learn 12. Quality is not a variable
QUESTIONS? After the session please fulfil the questionnaire. Questionnaires will be sent to you by and will be available in the profile section of the NT Conference website Thank you!