Project Management

Please login or join to subscribe to this thread

Documenting change -

linkedin twitter facebook   Organizational Project Management  
avatar
Tom Szelagowski United Kingdom
Hi All
I have a questoin about good practice.

If what the project was meant to deliver, as per ideation paper, is going to be delivered on a BAU basis after the proejct ends, what is the essential minimum regarding documentation?
Our team is strongly integrated across levels, so a board member is already aware - I am thinking with documenting and good practice in mind.

What was supposed to happen and what we believe will happen:
- split organisational data into operational and "aged" (long unaccessed) - won't happen
- move shared folders content into an integrated space to match an ongoing merger and the creation of a new operational model - will happen only when the model becomes apparent (quite obvious, I would think), which is after the project ends already
- project will end up mapping the as is and, to a very limited extent, future requirements

One of my concerns is that I am in a new role, not really sure if the project is badly designed on purpose - to test the new person's ability to think critically, or by mistake, in which case I need to tread carefully not to offend the authors.
Thank you.
Sort By:
avatar
David Portas London, United Kingdom
I work with technology, software and data. For technology solutions and more generally in other domains too, the continual improvement of solutions and processes during BAU is absolutely the norm.

My advice is to document the *product*, not the project. Project-specific documentation is of very transitory value so keep it to an absolute minimum. Product documentation evolves all the time. If you aim to build a sustainable process (dev-ops) so that the solution can keep evolving then the ending of each project becomes a milestone in a much longer journey.
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
What do business operations expect for documentation? They should drive your requirements. in fact, that should be identified for the hand-off.
avatar
Tom Szelagowski United Kingdom
Thanks for your answers.

Expectations are very relaxed.
We do document the product (in this case, as is mapping of the folder ownership and short-term requirements).

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Being powerful is like being a lady. If you have to tell people you are, you aren't."

- Margaret Thatcher

ADVERTISEMENT

Sponsors