Professional Scrum Development With Microsoft® Visual Studio® 2012 by Hundhausen, Richard -- Read -- Imperial Library of Trantor

Index

Professional Scrum Development with Microsoft® Visual Studio® 2012 Dedication A Note Regarding Supplemental Files Praise for this book Foreword Introduction

Who should read this book Who should not read this book Organization of this book

Finding your best starting point in this book

Conventions and features in this book Code samples

Installing and using the Scrum Robot

Acknowledgments Errata & book support We want to hear from you Stay in touch

I. Fundamentals

1. Scrumdamentals

The Scrum Guide

Scrum in action Scrum roles

The Development Team The Product Owner The Scrum Master Stakeholders

Scrum events

The Sprint Sprint Planning meeting The Daily Scrum Sprint Review meeting Sprint Retrospective meeting Product Backlog grooming

Scrum artifacts

Product Backlog Sprint Backlog The Increment

Definition of “Done”

Undone work

The professional Scrum developer Chapter burndown

2. Microsoft Visual Studio 2012 ALM

Delivering continuous value Visual Studio 2012

Editions

Professional edition Test Professional edition Premium edition Ultimate edition Express editions

Team Foundation Server Team Foundation Service

Hosted builds Agents for Visual Studio 2012

Visual Studio Team Explorer Everywhere 2012 MSDN subscriptions

Chapter burndown

3. Microsoft Visual Studio Scrum 2.0

Dissecting the process template

MSF process templates Exploring a process template

The Process Editor

Visual Studio Scrum 2.0

What’s new and different

What’s new What’s changed What’s removed

Work item types

Product Backlog Item Bug Task Test Case Impediment Hidden work item types

Work item queries Reports

Backlog Overview report Release Burndown report Sprint Burndown report Velocity report Build Success Over Time report Build Summary report Test Case Readiness report Test Plan Progress report

Common customizations

Chapter burndown

II. Using Scrum

4. The pre-game

Setting up the development environment

Team Foundation Server: Buy vs. build Create a team project collection Configure Team Foundation Build

Team Foundation Build features

Configure Lab Management

Setting up product development

Create a team project

How many team projects will you need? Creating a !Backlog team project Supporting the entire lifecycle of the product What should you name your team project?

Source control

Set up the folder structure Choose a branching strategy Local workspaces vs. Git (DVCS)

Automated builds Project portal

Definition of “Done”

Reports Security groups Teams

Chapter burndown

5. The Product Backlog

Creating the Product Backlog

Team Web Access

Licensing and permissions

Using the “quick add” experience

Removing an item from the Product Backlog Customizing the “quick add” panel

Handling epic PBIs Importing existing PBIs Reporting a bug

What makes a bug report good? Where do bugs come from? In-Sprint vs. out-of-Sprint bugs Bug reactivations

Effective Product Backlog creation

Grooming the Product Backlog

Specifying acceptance criteria

Scope creep (a.k.a. Feature creep)

Estimating items in the Product Backlog

Planning Poker Avoid anchoring White Elephant game

Tracking estimates in the Product Backlog Ordering the Product Backlog

Customizing the backlog columns

Planning a release

Time-driven vs. feature-driven releases Controlling and prioritizing scope Using Velocity to estimate

The forecasting tool

Release Burndown report

Chapter burndown

6. The Sprint

Creating the Sprint Backlog

Forecasting the PBIs Capturing the Sprint Goal Creating the plan

Capacity planning Customizing the (Sprint) backlog page

Daily Scrum activities

The Daily Scrum

Handling impediments

Taking on work

Decomposing tasks

The task board

Viewing tasks by team member Adding new tasks Setting task ownership Changing a task’s state Updating remaining work estimates

Chapter burndown

7. Acceptance test-driven development

Keep the conversation going

Collaborative specifications Executable specifications

Acceptance test-driven development

Test-driven development

Automated acceptance testing

Creating a test case Associating an automated test

CodedUI CodeFirst

Executing automated acceptance tests Reusing test cases Other acceptance-testing frameworks

Acceptance Chapter burndown

8. Effective collaboration

Individuals and interactions over processes and tools

Listen actively Collocate Set up a team room Meet effectively Collaborate productively Achieve continuous feedback

Collaborative development practices

Collective code ownership

Tracking ownership in TFS

Commenting in code Code reviews

Pair programming

Collaborative development tools

Team Foundation Server Continuous integration

Builds check-in policy Build Notifications tool

Gated check-in builds Email alerts Shelving My Work

Suspending and resuming work

PowerPoint Storyboarding

Creating a storyboard

Feedback client

Requesting feedback Providing feedback Voluntary feedback

Code reviews

Chapter burndown

III. Improving

9. Continuous improvement

Common challenges

Bugs Impediments Estimation Assessing progress Renegotiating scope

Canceling a Sprint

Undone work

Feature toggles Handling undone work in Visual Studio

Spikes Fixed-Price contracts and Scrum

Common dysfunctions

Not getting “done” Flaccid Scrum Not inspecting, not adapting Development Team challenges

Measuring performance

Working with a challenging Product Owner Working with challenging stakeholders Working with a challenging Scrum Master Changing Scrum

Old waterfall habits ScrumButs

Improving

Get a coach Build a cross-functional team Achieve self-organization Improve transparency Swarm Use a Kanban board to limit WIP Professional Scrum Developer training Assess your knowledge Become a high-performance Scrum Development Team

Chapter burndown

A. The Scrum Guide

Scrum Overview

Scrum Framework

Scrum Theory

Transparency Inspection Adaptation

Scrum The Scrum Team

The Product Owner The Development Team

Development Team Size

The Scrum Master

Scrum Master Service to the Product Owner Scrum Master Service to the Development Team Scrum Master Service to the Organization

Scrum Events

The Sprint

Cancelling a Sprint

Sprint Planning Meeting

Part One: What will be done this Sprint? Part Two: How will the chosen work get done? Sprint Goal

Daily Scrum Sprint Review Sprint Retrospective

Scrum Artifacts

Product Backlog

Monitoring Progress Toward a Goal

Sprint Backlog

Monitoring Sprint Progress

Increment Definition of “Done”

Conclusion Acknowledgements

People History

Index About the Author Copyright

← Prev
Back
Next →

← Prev
Back
Next →