Programme Content

Programme Scope
Technical author to use the programme management deliverables 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.
 * Maybe include a useful resource: http://www.techrepublic.com/blog/10things/10-best-practices-for-successful-project-management/904

Programme 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.

Reporting Lines
Include reporting lines so we're all clear who to go to for various parts of the project delivery puzzle.
 * PMO?
 * Infrastruture.
 * Change requests.
 * Operations.
 * 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.

Stakeholders (and expected availability)
Include all individuals in the stakeholder and SME group possibly with a page of their own. It's their way of sharing what they're up to in the likelihood that they are joining team meetings less frequently, if at all.
 * 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...

Jaffa jim (talk) 16:44, July 4, 2013 (UTC)