Project X Content

Project Scope
Technical author to use the project definition document or agile project scope document to kick this page off.
 * Encourage stakeholders to review this page and use the contribute option to include edits.
 * Please use edit summary so we can keep track of changes.
 * Change is good as long as it's clearly communicated and managed.
 * Check out this useful resource if the scope's not drafted yet: http://itsadeliverything.com/agile-project-scope

Project Methodology
It always helps stakeholders and new team members if obfuscation (intentional confusion and cliquey jargon) is avoided. This is especially important when deciding what methodology is to be used. It doesn't matter which it is, just that everyone is clear of the choice made.

Consider including links to the best practice resources so everyone is pulling in the same direction.

Project Reporting
Include reporting deliverables and the individuals responsible for their creation.
 * Advise including links to individual team members pages so they publish their deliverables there. Transparent and allows us all to share and motivate each other even if we're not in the same building or office.
 * Include a link to the project timetable in order that it doesn't end up stored (AND LOCKED FOR EDITING) on a local machine or in a 10 level folder structure on a slow and unweildy CMS.

Project Team Members
Include all individuals in the team with a page of their own. It's their way of sharing what they're up to so the SCRUM can be focussed and quickly completed.
 * Advise including links to individual team members pages so they publish their deliverables there. Transparent and allows us all to share and motivate each other even if we're not in the same building or office.
 * And so on...

Project End Date
Include the date that we hope to complete, plus a team celebration plan. Great for motivation and to ensure we all feel that we are focussed on something SMART.