Useful strategy documents
Do you find yourself in such situation, that you feel at the end phase of your project: "It would have good if we found the solution earlier" , "would have gone much more smoothly", don't you?
With many IT projects behind my back I think I could summarize what kind of documents are very useful if they have made at early phases of a project. Usually these documents are that ones what project members "hate" to create or like to laze them. But I have to say it's quite wrong practice.
What are these document types?
What are these document types?
- migration strategy
- interface strategy
- testing strategy
- going live procedure
- handover/takeover criterias
- acceptance/goal criterias
At this post I will extract my thoughts about the migration strategy.
