At 10:39 AM 6/27/2002 -0400, Keren Solomon wrote: >Here's a suggestion. When your project starts and you have a team kickoff >meeting, bring up the subject of testing. At that point, the project >schedule is rarely set in stone. Ask (nicely) when testing will take place. >Suggest where it should be built into the project plan. Explain how long it >will take and what report/technical spec/bug list/other documentation will >result from doing the testing. Offer to write the test plan. Offer to >include the test plan in the first technical spec that you deliver to the >client, so that he/she can review and sign off on it. I'm assuming that >you're the developer on the project. If you have a QA resource, sit with >him/her early in the project. Figure out what you want to test and the >value it serves. Then talk to the project manager together. Frankly, while >many QA people used to talk to me about the value of testing, fewer >developers would. At the beginning of your project, make a list of project >risk factors, and explain how the testing you want to do will reduce some >those risk factors. Be as specific as you can, because that gives the >project manager a rationale for approving the extra hours in the schedule >and budget. > >Hope this helps. great advice. thanks a lot. this list rocks!!! __________________________________________________________________________ To unsubscribe send a blank message with unsubscribe in the subject to webproducers-request@xxxxxxxxxxxxx To access our webform (instead of sending e-mail) for popular commands including subscribe, unsubscribe, digest, and vacation visit www.WebProducers.org. You can also access the list archive at the website. Questions and comments are welcome just e-mail me, morry@xxxxxxxxxxxxxxxx