Historical errata for Manage It!

Hi,

I’m missing the mentioned templates on this website.

(Page 15: "All the templates in this book are also online, at the book

Project templates mentioned in the book cannot be found in the book’s website. Please make them available as soon as possible.
Thanks,
Jay

Incorrect sentence in the last paragraph on page 20

What jumps out as you as being required for your project

Major part of page 81 is empty. Next subsection is moved to the page 82. Additionally Figure 5.1 and Tip come before subsection on page 82.

Last line, “timboxed iterations” should be “timeboxed iterations”.

The 2nd bullet, ‘timeboxed’ should be used: line with “… to continue using time-boxed iterations,…”. ‘timeboxed’ is used consistently in text.

Or every usage should be changed to ‘time-boxed’ because spell checker complains about ‘timeboxed’ usage.

“Who writes a project charter? Chartering is on early way to help a team jell.” Although both “jell” and “gel” are verbs representing the same thing, the trademark Jell-O comes to mind rather than the verb meaning to clarify and solidify. Similar to the argument for tissue and Kleenex. In your article “Got Good Rhythm?” of 05/10/2004, you used the expression “projects that mysteriously gel, the rhythm becomes clearer and more focused..” Your spelling and terminology left no room for error the image you were trying to portray. My vote is obviously for “gel” and not “jell”.

In the penultimate bullet point it says “people use inch-pepples”, but I suspect it should have said “people use inch-pebbles”. Cheers.

Title Page is missing (in contrast to other pragmatic books), sometimes the footer is missing (with link to erratum report)

“the nonwork people are doing complete dwarfs their project accomplishments”
Should be “completely”.

In the “System Test Entry Criteria” section,
“it’s too easy for the project team think they’ve met
their milestones.” should be
“… team to think …”

End of the second paragraph:
“Longer projects need even long retrospectives”
should be
“Longer projects need even longer retrospectives”.

Figure 16.2 is titled “Project Portfolio”, the same as Figure 16.1. In context, it seems 16.2 should be called “Product Backlog”.

Near the bottom of the page:
“…not to try to obtain all the requirements perform
the analysis up front.”.
Seems to be a word missing, possibly “or”.

Definition of life cycle says:
“This is the way your organize the project”
Should be “you”.

“Requirements” is not exactly the correct term for the charter template. It should be “Driver” or something like that. The key is to talk about what’s driving the project. In the templates, I’m changing Requirements to “Drivers, Constraints, and Floats”. (I could use some editing help here :-)

Final line: What jumps out at you as being required

First paragraph: they realize not only that they are accountable for their part

Decide between “Feature X” (first list) and “Feature x” (second list).

Third paragraph: for this product and/or this project

Next-to-last paragraph: people […] believe that end date

Put parentheses around “Appendix B, on page 335” in the frst line of text

Second bullet in second list: you and your team

First paragraph: several features or a set of requirements

First paragraph: The category name becomes the criterion (singular)

Third paragraph: we didn’t have to manage

Fourth paragraph: the nonwork […] completely dwarfs

It seems quite redundant to “see the tip” inside the tip itself.

Next-to-last line: acknowledgement

Strike “the” in the first line

Next-to-last paragraph: By the time they got

Last paragraph: what would solve their problems

Strike second “the Team” in section title

Second-to-last paragraph: I don’t demand each project team to perform nightly builds

Second paragraph: the team is more likely to monitor it

Second paragraph: on a multisite project

Section Title: How Product Risks Affect the Ratio

First Section Title: How Project and Process Risks Affect the Ratio

Fourth paragraph: process risks will demand that you add more testers

Section Title: Features Not to Be Tested (capitalized)

Last paragraph: I’ve used a template

Second bullet point: Each project is a significant effort so it requires

Second-to-last paragraph: Your job is to look

Second paragraph: Review the project managers’ risk lists

First paragraph: The team asks questions

Second paragraph: Longer projects need even longer retrospectives

Life cycle: This is the way you organize the project

Program management: Program management means

Koh93: Incentive Plans

The references SH06a and SH06b seem identical (apart from the subtitle) and thus redundant

You99: Encoding error in book title (left quotation mark)

Next-to-last paragraph: Incomplete sentence: “not to try to obtain all the requirements to perform the analysis up front”

Figure A.2: Use a forced hyphenation in “development” in the fifth box.

Put some/more acronyms into the Index:
BDUF, 258
BWC, 201, 259, 286
IR, 201
SMART, 27, 30
SWAG, 63, 83
YAGNI, 284

“We had about six project teams, one of which was networking team.”

was a networking team

Period used instead of comma in paragraph under History: “If you’re managing a follow-on release. such as Release 4.3…”