Personal tools
You are here: Home → Organization → Communication Management Strategy
 

Communication Management Strategy

Computing Communication Management Strategy follows PRINCE2 and ITIL methodologies.

 

Project Communication

The project pipeline is formally reviewed in Computing Board Meetings.

Most of formal project communication is handled via CPM, CELLS Project Management Application. This application manages the main project documents and stage authorization workflow. Projects are formally tracked in Project Meetings.

 

 

Owner Starting Up Initiation Delivery
Project Board

1. Project Mandate:
- business justification
- project executive and project managers assignment
- triggers Starting Up a project

 4. Authorize Initiation    
                                                                                             




7. Stage Authorization

12. Authorize Exception

15. Authorize Project Closure
Project Manager

2. Project Brief (PB)
2.1 Business case: project users and interested parties, reasons for doing the project, expected benefits and disbenefits, constraints, assumptions and risks.
2.2 Project product description: composition, required skills, customer acceptance's criteria, method and responsibilities.
2.2 Project approach: options and recommendation

3. Request to Initiate

                                           







5. Project Initiation Document (PID)
5.1 Refined business case
5.2 Refined product description
5.3 Refined project approach
5.4 Risk management strategy
5.5 Quality management strategy
5.6 Configuration management strategy
5.7 Communication management strategy

6. Request to Deliver
 










                                                                   

8. Highlight Reports: status summary, products completed, products to be started, tolerance status (time, schedule, cost, scope), change budget status, risk budget status, requests for change status, key issues and risks, early warnings, lessons report

9. Authorize a Work Package

11. Exception Report (cause, consequences, options, recommendation and lessons learned), Exception Plan (updated PID) & Request to Approve Exception

13. Request for Advice

14a. Premature Closure Report & Closure Recommendation

14b. Planned Closure Report & Closure Recommendation
Team Manager     10. Completed Work Package

  

Meetings

  Project Meeting Computing Board Meeting Section Meeting Cross Section Meeting
Objective Coordinate action




 Manage Service Portfolio, i.e. propose or review projects and authorize next stage, review service quality and any hot topic
 Discuss and set team objectives, review progress, decide on needed action, coordinate and leverage resources. Manage Computing team
Agenda
  • Project planning
  • Progress review
  • Issues review
  • Action item review
  • Project reviews: Request to initiate, Request to deliver, End of stage, Exceptions, Closure report, Request for input
  • Action item review
  • General information
  • Service level metrics review
  • Major incident reviews
  • Activity review, coordination and planning
  • Best practices and knowledge sharing
  • Action item review
  • General information
  • External requests
  • Cross section update
  • Review Computing Dashboard: Customers, Service, Projects, Process, People, Budget
  • Major incident reviews
  • Project and resource planning
  • Organizational issues & Improvement actions
  • Action item review
Participants
  • Project Manager
  • Team member
  • Project assurance (on a need basis)
  • User representative (on a need basis)   
                                   
  • Division head
  • Project Executive
  • Senior Supplier
  • Senior User
  • Project Manager
  • Project assurance
  • Section team
  • Computing Division head
  • Computing Section heads                         






Communication
 CPM highlight report automatically sent to project team and project board         

Link to CPM




                   







Meeting minutes sent to Computing division and stored here:

\\STORAGE00\Computing\ComputingBoardMeeting





 






 Meeting minutes sent to the section and stored on CELLS intranet and storage
  • Controls minutes: //storage00/Computing/Controls/MINUTES
  • Electronics minutes
    f//Storage00/Computing/Electronics/Section Meeting Minutes
  • MIS minutes
  • Systems minutes                      
 
Frequency Ad hoc Every 2 week if there is an agenda Weekly Weekly

 

 

Document Actions