|What we want|
Templates that are useful and valuable. That means substantial information pertinent to a real IT environment, beyond that which is obvious to a project manager. For example, technical specifications, workflow maps, requirements definitions, use case and other business models, test criteria, ROI cases.
Frameworks of or guidelines for developing something an IT project manager must deliver to a client or something a project team member must develop and maintain as a work document.
Templates that have passed internal quality control checks at your company and are grammatically correct. (Spelling counts!)
|What we don't want|
Templates that are no more than common sense on paper. We're not looking for the basics of setting up a meeting or work session, such as list of attendees, time, location; or anything as simple as sign-off sheets.
Templates that contain acronyms, specs and procedures specific to your project environment. If you have a useful template with some adaptations/modifications to other IT shops, clean it up to make it applicable and understandable by other project managers.
Copyrighted, grammatically incorrect, pirated, plagiarized, confidential, proprietary OR virus laden documents. Actually, you probably don't want those either.
|What's in it for you|
Need help submitting your template? For more information on submitting your template, contact firstname.lastname@example.org