Professional Scrum Development with Microsoft Visual Studio 2012

by Hundhausen, Richard

• ISBN13: 9780735657984
• ISBN10: 073565798X
• Edition: 1st
• Format: Paperback
• Copyright: 2019-11-21
• Publisher: Microsoft Press

Summary

NOTE: This book is based on Visual Studio 2012 Release Candidate; its content and publication date will be updated for final Visual Studio 2012 software. Discover how to turn requirements into working software increments-faster and more efficiently-using Visual Studio 2012 in combination with Scrum and Agile engineering practices. Designed for software development teams, this guide delivers pragmatic, role-based guidance for exploiting the capabilities of Application Lifecycle Management (ALM) tools in Visual Studio and Team Foundation Server. Team members will learn proven practices and techniques for implementing Scrum to manage an application's life cycle, as well as seamlessly plan, manage, and track their Scrum projects.

Author Biography

Richard Hundhausen, a Microsoft MVP for Visual Studio ALM and a Microsoft Regional Director, has 30+ years of experience in software development and 20+ years in training. He leads a company that focuses on helping software development teams apply Application Lifecycle Management (ALM) tools and Scrum practices, and hes written several books and courses.

Table of Contents

Foreword	p. xv
Introduction	p. xix
Who should read this book	p. xix
Who should not read this book	p. xx
Organization of this book	p. xx
Conventions and features in this book	p. xxi
Code samples	p. xxii
Acknowledgments	p. xxiii
Errata & book support	p. xxiii
We want to hear from you	p. xxiv
Stay in touch	p. xxiv
Fundamentals
Scrumdamentals	p. 3
The Scrum Guide	p. 3
Scrum in action	p. 4
Scrum roles	p. 6
Scrum events	p. 14
Scrum artifacts	p. 27
Definition of "Done"	p. 36
The professional Scrum developer	p. 37
Chapter burndown	p. 39
Mircosoft Visual Studio 2012 ALM	p. 41
Delivering continuous value	p. 42
Visual Studio 2012	p. 44
Editions	p. 46
Team Foundation Server	p. 51
Team Foundation Service	p. 52
Visual Studio Team Explorer Everywhere 2012	p. 54
MSDN subscriptions	p. 54
Chapter burndown	p. 55
Microsoft Visual Studio Scrum 2.0	p. 57
Dissecting the process template	p. 57
MSF process templates	p. 59
Exploring a process template	p. 59
Visual Studio Scrum 2.0	p. 61
What's new and different	p. 62
Work item types	p. 67
Work item queries	p. 81
Reports	p. 83
Common customizations	p. 86
Chapter burndown	p. 88
Using Scrum
The pre-game	p. 93
Setting up the development environment	p. 94
Team Foundation Server: Buy vs. build	p. .94
Create a team project collection	p. 96
Configure Team Foundation Build	p. 97
Configure Lab Management	p. 100
Setting up product development	p. 103
Create a team project	p. 103
Source control	p. 108
Automated builds	p. 113
Project portal	p. 115
Reports	p. 118
Security groups	p. 121
Teams	p. 122
Chapter burndown	p. 124
The Product Backlog	p. 127
Creating the Product Backlog	p. 127
Team Web Access	p. 128
Using the "quick add" experience	p. 130
Handling epic PBIs	p. 134
Importing existing PBIs	p. 137
Reporting a bug	p. 140
Effective Product Backlog creation	p. 147
Grooming the Product Backlog	p. 149
Specifying acceptance criteria	p. 150
Estimating items in the Product Backlog	p. 152
Tracking estimates in the Product Backlog	p. 155
Ordering the Product Backlog	p. 156
Planning a release	p. 160
Time-driven vs. feature-driven releases	p. 161
Controlling and prioritizing scope	p. 161
Using Velocity to estimate	p. 162
Release Burndown report	p. 166
Chapter burndown	p. 167
The Sprint	p. 169
Creating the Sprint Backlog	p. 170
Forecasting the PBIs	p. 170
Capturing the Sprint Goal	p. 173
Creating the plan	p. 174
Daily Scrum activities	p. 179
The Daily Scrum	p. 180
Taking on work	p. 183
The task board	p. 185
Chapter burndown	p. 196
Acceptance test-driven development	p. 197
Keep the conversation going	p. 198
Collaborative specifications	p. 199
Executable specifications	p. 201
Acceptance test-driven development	p. 202
Test-driven development	p. 205
Automated acceptance testing	p. 206
Creating a test case	p. 206
Associating an automated test	p. 210
Executing automated acceptance tests	p. 214
Reusing test cases	p. 217
Other acceptance-testing frameworks	p. 221
Acceptance	p. 224
Chapter burndown	p. 225
Effective collaboration	p. 227
Individuals and interactions over processes and tools	p. 227
Listen actively	p. 229
Collocate	p. 230
Set up a team room	p. 232
Meet effectively	p. 233
Collaborate productively	p. 234
Achieve continuous feedback	p. 236
Collaborative development practices	p. 237
Collective code ownership	p. 238
Commenting in code	p. 240
Code reviews	p. 241
Collaborative development tools	p. 244
Team Foundation Server	p. 244
Continuous integration	p. 245
Gated check-in builds	p. 249
Email alerts	p. 250
Shelving	p. 253
My Work	p. 254
PowerPoint Storyboarding	p. 257
Feedback client	p. 261
Code reviews	p. 267
Chapter burndown	p. 271
Improving
Continuous improvement	p. 275
Common challenges	p. 275
Bugs	p. 276
Impediments	p. 277
Estimation	p. 279
Assessing progress	p. 282
Renegotiating scope	p. 286
Undone work	p. 288
Spikes	p. 293
Fixed-Price contracts and Scrum	p. 294
Common dysfunctions	p. 296
Not getting "done"	p. 297
Flaccid Scrum	p. 298
Not inspecting, not adapting	p. 299
Development Team challenges	p. 300
Working with a challenging Product Owner	p. 304
Working with challenging stakeholders	p. 307
Working with a challenging Scrum Master	p. 309
Changing Scrum	p. 312
Improving	p. 315
Get a coach	p. 315
Build a cross-functional team	p. 316
Achieve self-organization	p. 317
Improve transparency	p. 318
Swarm	p. 319
Use a Kanban board to limit WIP	p. 319
Professional Scrum Developer training	p. 322
Assess your knowledge	p. 322
Become a high-performance Scrum Development Team	p. 323
Chapter bumdown	p. 324
Appendix: The Scrum Guide	p. 325
Index	p. 341
Table of Contents provided by Ingram. All Rights Reserved.