CMS and Website 2.0 Project [Step.1]

1,072 views
969 views

Published on

By detecting and correcting weaknesses early in a technology project\’s life-cycle, organisations can reduce both risk and costs. Find out where the path to creating a secure project framework begins.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,072
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

CMS and Website 2.0 Project [Step.1]

  1. 1. Content Management System<br />& Website 2.0 Project<br />Introduction: Project start-up<br />22nd November 2006<br />Daniel Newman<br />INTERNATIONAL PROJECT MANAGER<br />
  2. 2. Agenda<br />Introduction: Snapshot<br />Meeting Objectives<br />Key deliverables - Quick view<br />The Project Management Team<br />Project Board<br />Project Team<br />Review Team<br />Questions<br />Lift-Off<br />
  3. 3. Introduction <br />The importance of this presentation is to make you all aware;<br />that to deliver the CMS & Website 2.0 project we need a framework.<br />That framework is called the Project Management Team.<br />This presentation gives an outline of what the Project Management <br />Team is, why we need it, its roles and its responsibilities in delivery <br />of this project.<br />.<br />Obviously, this requires YOUR input.<br />
  4. 4. Snapshot <br />Because we all have responsibilities to other areas in the<br />business, it is critical to have an overview of what this<br />project is about, and where we fit in.<br />Business Needs<br />Business<br />User<br />Solutions<br />Web Strategy<br />Review<br />New content<br />management system<br />
  5. 5. Meeting Objectives <br />1<br />To give a high level overview of the required framework for delivery of the CMS & Website 2.0<br />To obtain agreement from the proposed Project Board that they are committed to working together as a team.<br />For the Project Board to agree next steps, arising from their first viewing of the Project Brief, sent out yesterday.<br />2<br />3<br />
  6. 6. Key Deliverables <br />Quick view<br /> The CMS & Website 2.0 project key deliverables are;<br />New Content Management System (CMS).<br /><ul><li>User acceptance of the new CMS.
  7. 7. Migration of all existing web site content to the new CMS.</li></ul>Implementation of agreed upon web strategy recommendations.<br /><ul><li>To be defined (3rd Party Supplier)</li></li></ul><li>The Project Management TeamRoles & Responsibilities<br />
  8. 8. Project Management Team<br /> The Project Management Team consist of:<br />PROJECT<br />BOARD<br />Review<br />TEAM<br />PROJECT<br />TEAM<br />
  9. 9. Project Management Team<br /> They are responsible for:<br />Executive direction<br />Review<br />PROJECT<br />BOARD<br />Review<br />TEAM<br />PROJECT<br />TEAM<br />Daily Operations<br />
  10. 10. Project Management Team<br /> This is how the team works<br />Assigns<br />PROJECT<br />BOARD<br />Reports<br />Assigns<br />PROJECT<br />TEAM<br />Monitors<br />Approval/<br />Decline<br />Review<br />TEAM<br />Reports<br />Reports<br />
  11. 11. Project Management Team<br /> Authority Level<br />CEO<br />Time and cost parameters<br />Ultimate accountability<br />Key decision maker<br />PROJECT CHAMPION<br />Executive<br />EXECUTE<br />IT Director<br />Director<br />PROJECT SPONSOR<br />Senior User<br />SOLUTIONS<br />(INTERNAL)<br />Support<br />SUPPORT<br />User resource<br />User requirements are met<br />Product must provide user benefits<br />Must achieve the results<br />Required by the Senior User<br />Accountable for the quality of all delivered Product s<br />
  12. 12. Project Management Team<br /> Communication Plan<br />Method<br />Provider<br />Frequency<br />PROJECT BOARD<br />Review Team<br />Project Team<br />External supplier<br />Monthly<br />Report<br />Meeting<br />Collaboration Site<br />Email<br />Fax<br />Telephone<br />Meeting<br />Review Team<br />Project Board<br />External supplier<br />Team members<br />PROJECT TEAM<br />Daily<br />Review TEAM<br />Report<br />Meeting<br />Project Board<br />Project Manager<br />Weekly<br />
  13. 13. Project Management Team<br /> This is why we need the team<br />1.To plan and coordinate resources.<br />2.To obtain sufficient definition of the key deliverables.<br />3.To work as a team,providingthe best possible estimates on time and cost.<br />4.To avoid delivery of products that are unacceptable or unusable.<br />5.To avoid any lack in communication.<br />6.To provide good measurable progress showing theexact status of the <br />project (visibility at all times).<br />
  14. 14. Project BoardRoles & Responsibilities<br />
  15. 15. Project Board<br /> A Project Board is required because the <br />project must have :<br /> 1. Direction to be delivered successfully <br />(authorisation, closure, etc).<br /> 2. A project initiation document to act as a <br />“How to do” guide. <br /> 3. An agreed upon Project Team.<br /> 4. Advice and guidance if the project faces <br />any major threats.<br /> 5. A review of each project milestone.<br />
  16. 16. Project Board<br />CEO<br />Project Champion<br />Laine<br />Project Sponsor<br />BOARD<br />Obama<br />Project Client<br />Chambers<br />Solutions<br />JCC<br />HR Consultant<br />3rd Party Supplier<br />External Supplier<br />Located in the Project Team<br />Neutral Project Board<br />
  17. 17. Project Board<br /> They are responsible for;<br />Approve /<br />Decline<br />PROJECT<br />BOARD<br />Direction<br />Advice & Guidance<br />Project PR<br />
  18. 18. Project TeamRoles & Responsibilities<br />
  19. 19. Project Team<br /> A Project Team is required because the project :<br /> 1. Needs to be investigated (SCOPED).<br /> 2. Needs to be DESIGNED to meet <br /> requirements. <br /> 3. Needs to BUILD the designed products.<br /> 4. Needs to TEST the built products.<br /> 5. Needs to REVIEW the product.<br />
  20. 20. Project Team<br />Emmanuel<br />Development<br />Olivier<br />Usability Expert<br />External Supplier<br />IS<br />Development<br />3rd Party Supplier<br />Consultants<br />Dan<br />Project Manager<br />IS<br />Development<br />Located on the Project Board<br />
  21. 21. Project Team<br /> They are responsible for;<br />3<br />Builds<br />5<br />Tests<br />2<br />PROJECT<br />TEAM<br />Designs<br />6<br />Delivers<br />1<br />Scopes<br />7<br />Reviews<br />
  22. 22. Review TeamRoles & Responsibilities<br />
  23. 23. Review Team<br /> A Review Team is required because :<br /> 1. Project Board cannot do everything, they <br /> do not have the time!<br /> 2. Questions throughout the project need to<br /> be asked; is it really going well? <br /> 3. The stakeholders need to know that the <br /> project is on track to deliver what it <br /> promised.<br /> 4. Nothing should be hidden in the project.<br /> 5. To confirm that nothing that was agreed <br /> to be delivered has been missed out. <br />
  24. 24. Review Team<br />Michael<br />Project Champion<br />Britta<br />Project Sponsor<br />Ronnie<br />Project Client<br />Thierry<br />Internal Solutions<br />JCC<br />HR Consultant<br />Nikolaj<br />External Solutions<br />Is everything OK?<br />
  25. 25. Review Team<br /> They are responsible for:<br />Check<br />PROJECT<br />Review<br />TEAM<br />Visibility<br />Focus<br />Control<br />Added-Value<br />
  26. 26. Key Deliverables <br />Reminder<br /> The CMS & Website 2.0 project key deliverables are;<br />New Content Management System (CMS).<br /><ul><li>User acceptance of the new CMS.
  27. 27. Migration of all existing web site content to the new CMS.</li></ul>Implementation of agreed upon web strategy recommendations.<br /><ul><li>To be defined (3rd Party Supplier)</li></li></ul><li>Start-up Steps <br />1. CREATE<br />Project Management Team<br />2. DEFINE<br />Project Objectives<br />3. IDENTIFY<br />Solution (plus production)<br />4. ANALYSE<br />Business Case / Risks<br />5. PLAN<br />The actual work involved<br />We are here<br />First steps for delivery of the CMS and Website 2.0 project.<br />
  28. 28. Questions?<br />Do not be afraid to ask any questions,<br />they help us to learn!<br />You can also use our project discussion board<br />
  29. 29. Thank you for your participation<br />
  30. 30. Clients include:<br />ABC News<br />Amadeus<br />GSK<br />HMV<br />IBM<br />Interactive1<br />J Sainsbury Plc<br />Knight Frank<br />LBNL<br />Mobilkom Austria– Vipnet<br />National Westminster Bank<br />PwC<br />The British Council<br />The European Society of Cardiology<br />Daniel Newman<br />INTERNATIONAL PROJECT MANAGER<br />

×