Errata

Professional Scrum Development with Microsoft Visual Studio 2012

Errata for Professional Scrum Development with Microsoft Visual Studio 2012

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Other Digital Version 1
n/a

The Scrum robot readme.txt has an unfinished sentence:

2. Have a TFS 2012 team project collection, There are destructive

Destructive what? I thing this last part should have been removed.

 Jesse Houwing  Nov 16, 2012 
Other Digital Version 1
n/a

The link to this errata page from the Scrum Robot utility page referenced on the back cover of the print edition doesn't work

There's a '>' at the end of the uri that should not be there.

 Jesse Houwing  Nov 16, 2012 
Printed Page 75
2nd "Smell" Box first line

using spelled usnig

 Niel Zeeman  Mar 03, 2013 
Printed Page 132
last sentence on page

"Use Witadmin exportagileprocess.config" should be : "Witadmin exportagileprocessconfig" without the full stop.

 Niel Zeeman  Mar 10, 2013 
Printed Page 149
2nd paragraph, second sentence

"... until the time that it the item is forecast ..."
should either have "it" or "the item"

Niel Zeeman  Mar 11, 2013 
Printed Page 233
2nd Paragraph under "Meeting effectively"

"Development Team to what they do best" - missing a "do"

Niel Zeeman  Mar 26, 2013 
PDF Page 329
3rd paragraph

A sentence before the THE PRODUCT OWNER subtitle is simply an excess. Somebody pasted it there in error. There is no such sentence in the original of that text, available at www.scrum.org/scrum-guides.

+++++++++++++++++++++
The excessive sentence says: "one is allowed to tell the Development Team to work from a different set of requirements and the Development Team isn't allowed to act on what anyone else says". Obviously, word NO at the beginning of the sentence is missing, and that sentence is placed elsewhere in the Scrum Guide :-)

 Anonymous  Mar 17, 2013