On Tue, Mar 02, 2010 at 05:14:37PM -0500, berg...@merctech.com wrote: > I include documentation in the "budget"...whether I'm doing an estimate in my > head or presenting a more formal project plan, there's always a documentation > component. > > This way it's clear that documentation is an integral part, not an > afterthought > for which it's difficult to justify the time required.
That makes a lot of sense. One of our problems is that we're usually barrelling forward at 110% speed 120% of the time. We don't get time to slow down and plan things properly, although this is starting to change, and should also get better now that we're starting to staff up a bit. Have you noticed whether the documentation phase of your projects generally stays around X hours, or does it vary more directly with the complexity of project? For me it always seem to vary inversely with the length of the project. Blah. > => "make the n00b on the team do all the documentation." > > I like that as a training tool and a way to expose whether existing > documentation is sufficient, in the absence of senior team members....but > it's > no substitute for on-going internal docs written by the people working on > each > project. Recently we told our junior admin that he'd be in charge of the majority of tickets coming into our RT queue. The hope is that even if it's not something he knows enough about to document, it will force us to get our docs out there for him, just to save ourselves time in the long run. We just started this last week, so I'm unsure how it will actually play out. Thanks for the info, definitely some tips I'm going to try out. -jkl _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
