Re: When to write in less-than-perfect Agile

Subject: Re: When to write in less-than-perfect Agile
From: Tony Chung <tonyc -at- tonychung -dot- ca>
To: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
Date: Tue, 1 Apr 2014 10:34:24 -0700

Should a feature even need to be documented if it's not yet fit for
consumption? I'm just curious if maybe you're jumping the gun about writing
about new features as the product is still being formed.

I'm researching this for other purposes, but in my opinion, any feature
that is complete but not consumable (or requires a lot of excess work) is
still a beta.

The last point in this TDD cycle is "refactor the code to meet acceptable

It's like saying instant coffee makes a decent espresso. Maybe it completes
the feature, but it's not consumable "by acceptable standards."

Personally I don't think company's set their release standards high enough.

As for the rules for good scrum masters, you don't need a scrum master to
be agile. Scrum is just one tool that has worked successfully in the past.
If your team is able to maintain work visibility, and know their action
items with follow up deadlines, then a decent PM or team lead should keep
the cycle moving.

Of course, I've never worked in a successful agile implementation, so I
can't speak from good experience. I just know that teams work effectively
when they:
a) know what's expected of them
b) know what everyone else is doing

That's just common sense.
Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.

Learn more:


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


When to write in less-than-perfect Agile: From: McLauchlan, Kevin

Previous by Author: TechWhirl: Technical Communication Recap for April 25, 2014
Next by Author: Re: Get a free proofreading checklist while they're hot
Previous by Thread: RE: When to write in less-than-perfect Agile
Next by Thread: Re: When to write in less-than-perfect Agile

What this post helpful? Share it with friends and colleagues:

Sponsored Ads