Hi,
I recently started in a global company who are masters of corprate politics and unecessry bluster. I come from an Online Gaming agile background so this is a bt of shock to me. Anyway, I've been asked to write up a 'Detailed Operational Design' document and the way its been described to me is its a mish-mash of all the info thats been gathered with a lot of it being a 'copy & paste' job from other documents. I've seen some the other DOD's that have been done and theyre garbage.....40-50 pages of high level ambiguous blag that probably has a point in there but no-one can find it.
I'm not comfortable doing this so wondered if anyone has (or uses) a standard DOD template that can give me an idea of what one should properly contain?
Hi George,
I noticed that noone has tackled your question. Probably becuase the underlying/implied questions are enormous. But let's try to narrow the focus a bit.
First, what is a DOD in your words. That's not a common term used on these forums. My guess is that it overlaps with Business Requirements Documents, Requirements Specification Documents, etc.
Next, give a just a bit of context. What kind of documentation would you have put together in the past in your Agile environment?
And, yes the type of enivronment you are describing at this large company is far too common.
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: