Re: Getting developers to document their efforts

Subject: Re: Getting developers to document their efforts
From: Iggy <iggy_1996dp -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 17 Dec 2001 21:06:56 -0800 (PST)

One word: specification

Two types: functional and design

Three data types: planned, scheduled, and completed

Four benefits: developer has evidence of work done,
those who need info on what's new/changed now have it,
specs can be analyzed for future planning, and can be
used for knowledge transfer within development.

--- Lindalee -dot- Brownstein -at- ebancllc -dot- com wrote:
> We would like to give our developers a template that
> they can use to record
> technical information and changes they make during
> the development process.
> These could then be used by technical support, new
> developers,
> documentation staff, etc. Topics might include
> things like new features,
> changes to the data model, new options, etc. We are
> looking for ideas for
> the content and format, and any suggestions to help
> us make this work.

__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.


References:
Getting developers to document their efforts: From: Lindalee . Brownstein

Previous by Author: Re: Buying software oneself in order to learn it
Next by Author: Re: Users vs. usage
Previous by Thread: Getting developers to document their efforts
Next by Thread: Re: Getting developers to document their efforts


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


Sponsored Ads