Difference between revisions of "Microsoft KB Archive/249298"

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 70: Line 70:
 
<br />
 
<br />
 
Change:<br />
 
Change:<br />
&quot;Some software developers place a high emphasis on project heroics (Bach 1995). But I think that they do more harm than good.&quot;<br />
+
"Some software developers place a high emphasis on project heroics (Bach 1995). But I think that they do more harm than good."<br />
 
<br />
 
<br />
 
To:<br />
 
To:<br />
&quot;Some developers place a high emphasis on project heroics and think that the certain kinds of heroics can be beneficial (Bach 1995). But I think that emphasizing heroics in any form usually does more harm than good.&quot;<br />
+
"Some developers place a high emphasis on project heroics and think that the certain kinds of heroics can be beneficial (Bach 1995). But I think that emphasizing heroics in any form usually does more harm than good."<br />
 
<br />
 
<br />
  
Line 81: Line 81:
 
<br />
 
<br />
 
Change:<br />
 
Change:<br />
&quot;They first estimate the size of the project, then they estimate the effort needed to build a product of that size, and then they estimate a schedule based on the effort estimate.&quot;<br />
+
"They first estimate the size of the project, then they estimate the effort needed to build a product of that size, and then they estimate a schedule based on the effort estimate."<br />
 
<br />
 
<br />
 
To:<br />
 
To:<br />
&quot;They first estimate the size of the product, then they estimate the effort needed to build a product of that size, and then they estimate a schedule based on the effort estimate.&quot;<br />
+
"They first estimate the size of the product, then they estimate the effort needed to build a product of that size, and then they estimate a schedule based on the effort estimate."<br />
 
<br />
 
<br />
  
Line 92: Line 92:
 
<br />
 
<br />
 
Change:<br />
 
Change:<br />
&quot;This is the same kind of chart that I presented in the “Classic Mistakes” chapter, and it describes the same lesson.&quot;<br />
+
"This is the same kind of chart that I presented in the “Classic Mistakes” chapter, and it describes the same lesson."<br />
 
<br />
 
<br />
 
To:<br />
 
To:<br />
&quot;This is the same chart that I presented in the &quot;Classic Mistakes&quot; chapter, and it provides a specific example of the general classic mistakes lesson.&quot;<br />
+
"This is the same chart that I presented in the "Classic Mistakes" chapter, and it provides a specific example of the general classic mistakes lesson."<br />
 
<br />
 
<br />
  
Line 103: Line 103:
 
<br />
 
<br />
 
Change:<br />
 
Change:<br />
&quot;Look at how much of the curve in Figure 6-10 is to the right of the planned-schedule line on typical projects.&quot;<br />
+
"Look at how much of the curve in Figure 6-10 is to the right of the planned-schedule line on typical projects."<br />
 
<br />
 
<br />
 
To:<br />
 
To:<br />
&quot;Look at how much of the curve in Figure 6-11 is to the right of the planned-schedule line on typical projects.&quot;<br />
+
"Look at how much of the curve in Figure 6-11 is to the right of the planned-schedule line on typical projects."<br />
 
<br />
 
<br />
  
Line 113: Line 113:
 
On page 168, in Figure 8-2, the upper graph labels on the right hand side are mixed up. From top to bottom, the graph labels should read as follows:<br />
 
On page 168, in Figure 8-2, the upper graph labels on the right hand side are mixed up. From top to bottom, the graph labels should read as follows:<br />
 
<br />
 
<br />
&quot; 1.6x<br />
+
" 1.6x<br />
 
1.25x<br />
 
1.25x<br />
 
1.15x<br />
 
1.15x<br />
Line 122: Line 122:
 
0.8x<br />
 
0.8x<br />
 
0.6x<br />
 
0.6x<br />
&quot;<br />
+
"<br />
 
<br />
 
<br />
  
Line 130: Line 130:
 
<br />
 
<br />
 
Change:<br />
 
Change:<br />
&quot;The efforts are given in developer man-months to two or three significant digits.&quot;<br />
+
"The efforts are given in developer man-months to two or three significant digits."<br />
 
<br />
 
<br />
 
To:<br />
 
To:<br />
&quot;The efforts are given in development-team man-months (including management and QA) to two or three significant digits&quot;<br />
+
"The efforts are given in development-team man-months (including management and QA) to two or three significant digits"<br />
 
<br />
 
<br />
  
Line 141: Line 141:
 
<br />
 
<br />
 
Change:<br />
 
Change:<br />
&quot;For more on using prototyping time effectively, see “Inefficient use of prototyping time” in Section 20.2.&quot;<br />
+
"For more on using prototyping time effectively, see “Inefficient use of prototyping time” in Section 20.2."<br />
 
<br />
 
<br />
 
To:<br />
 
To:<br />
&quot;For more on using prototyping time effectively, see “Inefficient use of prototyping time” in Section 21.2.&quot;<br />
+
"For more on using prototyping time effectively, see “Inefficient use of prototyping time” in Section 21.2."<br />
 
<br />
 
<br />
  
Line 159: Line 159:
 
<br />
 
<br />
 
Change:<br />
 
Change:<br />
&quot;Millington, Don, and Jennifer Stapleton. 1995. “Developing a RAD Standard.” IEEE Software, January: 54–55.&quot;<br />
+
"Millington, Don, and Jennifer Stapleton. 1995. “Developing a RAD Standard.” IEEE Software, January: 54–55."<br />
 
<br />
 
<br />
 
To:<br />
 
To:<br />
&quot;Millington, Don, and Jennifer Stapleton. 1995. “Developing a RAD Standard.” IEEE Software, September: 54–55.&quot;<br />
+
"Millington, Don, and Jennifer Stapleton. 1995. “Developing a RAD Standard.” IEEE Software, September: 54–55."<br />
 
<br />
 
<br />
 
Microsoft Press is committed to providing informative and accurate books. All comments and corrections listed above are ready for inclusion in future printings of this book. If you have a later printing of this book, it may already contain most or all of the above corrections.
 
Microsoft Press is committed to providing informative and accurate books. All comments and corrections listed above are ready for inclusion in future printings of this book. If you have a later printing of this book, it may already contain most or all of the above corrections.

Latest revision as of 13:51, 21 July 2020

Article ID: 249298

Article Last Modified on 7/18/2007



APPLIES TO

  • MSPRESS Rapid Development ISBN 1-55615-900-5



This article was previously published under Q249298

SUMMARY

This article contains comments, corrections, and information about known errors relating to the Microsoft Press book Rapid Development, ISBN 1-55615-900-5.

The following topics are covered:

  • Page 41: Clarification needed
  • Page 55: project should be product
  • Page 60: Clarification needed
  • Page 128: 6-10 should be 6-11
  • Page 168: Label Error
  • Page 186: Additional clarification needed
  • Page 572: 20.2 should be 21.2
  • Page 613: Add Citation
  • Page 618: January should be September


MORE INFORMATION

Page 41: Clarification needed

On page 41, the first two sentences of the Heroics section require clarification.

Change:
"Some software developers place a high emphasis on project heroics (Bach 1995). But I think that they do more harm than good."

To:
"Some developers place a high emphasis on project heroics and think that the certain kinds of heroics can be beneficial (Bach 1995). But I think that emphasizing heroics in any form usually does more harm than good."

Page 55: project should be product

On page 55, the second sentence of theEstimation and Scheduling section refers to a project rather than a product.

Change:
"They first estimate the size of the project, then they estimate the effort needed to build a product of that size, and then they estimate a schedule based on the effort estimate."

To:
"They first estimate the size of the product, then they estimate the effort needed to build a product of that size, and then they estimate a schedule based on the effort estimate."

Page 60: Clarification needed

On page 60, the first sentence after Figure 4-2 is inaccurate.

Change:
"This is the same kind of chart that I presented in the “Classic Mistakes” chapter, and it describes the same lesson."

To:
"This is the same chart that I presented in the "Classic Mistakes" chapter, and it provides a specific example of the general classic mistakes lesson."

Page 128: 6-10 should be 6-11

On page 128, the second sentence after Figure 6-11 refers to Figure 6-10 rather than 6-11.

Change:
"Look at how much of the curve in Figure 6-10 is to the right of the planned-schedule line on typical projects."

To:
"Look at how much of the curve in Figure 6-11 is to the right of the planned-schedule line on typical projects."

Page 168: Label Error

On page 168, in Figure 8-2, the upper graph labels on the right hand side are mixed up. From top to bottom, the graph labels should read as follows:

" 1.6x
1.25x
1.15x
1.1x
1.0x
0.9x
0.85x
0.8x
0.6x
"

Page 186: Additional clarification needed

On page 186, the first sentence of the Efforts section requirs additional clarification.

Change:
"The efforts are given in developer man-months to two or three significant digits."

To:
"The efforts are given in development-team man-months (including management and QA) to two or three significant digits"

Page 572: 20.2 should be 21.2

On page 572, the first cross-reference refers to thw wrong section.

Change:
"For more on using prototyping time effectively, see “Inefficient use of prototyping time” in Section 20.2."

To:
"For more on using prototyping time effectively, see “Inefficient use of prototyping time” in Section 21.2."

Page 613: Add Citation

The following citation should be added to page 613.

DeMarco, Tom. 1995. Why Does Software Cost So Much? Dorset House.

Page 618: January should be September

On page 618, the bibliography entry for Millington, Don, and Jennifer Stapleton contains an incorrect month.

Change:
"Millington, Don, and Jennifer Stapleton. 1995. “Developing a RAD Standard.” IEEE Software, January: 54–55."

To:
"Millington, Don, and Jennifer Stapleton. 1995. “Developing a RAD Standard.” IEEE Software, September: 54–55."

Microsoft Press is committed to providing informative and accurate books. All comments and corrections listed above are ready for inclusion in future printings of this book. If you have a later printing of this book, it may already contain most or all of the above corrections.


Additional query words: 1-55615-900-5 devbook 978-1-55615-900-8

Keywords: kbdocerr kbdocfix kbinfo KB249298