NearlyFree.com IT Governance
The following is an excerpt from the NearlyFree.com IT Governance.
Below you will find the IT policies for the Service Oriented Architecture and Enterprise, which is the basic framework and structure for all IT-related activities and customer and user interactions at NearlyFree.com. The philosophy here is service centered on customer satisfaction and quality.
IT Governance Overview
Governance policies provide guidelines to manage all IT programs and projects. Governance establishes clear roles, responsibilities, and accountabilities for all project team members including executive leadership and project managers. Industry best practices include the use of a governance process to oversee and manage project spending and to ensure there is an acceptable benefit or return on investment in all initiatives.
The key to the NearlyFree.com IT governance is the creation of the IT Program Management Office (PMO). The PMO seeks to understand and integrate organizational business goals with all approved project definitions and objectives. The PMO has a set definition and objectives, which set the scope and boundaries to deliver project management methodologies, guidelines, training, and investment benefits.
IT Service Oriented Governance Policies
The following types of policies apply to all service-oriented IT projects.
- Project life cycle (design, development, and implementation) policies.
- Quality management policies.
- Configuration and change management policies.
All projects will have to adopt the project management office (PMO) quality management plan and policies. Project change requests must go through the process and gain approval of the change control board (CCB).
Amendment History – Document Status (Release #7, 2008)
| Document Version # |
Approval Date |
Modified By |
Section, Page(s)and Text Revised |
| 7.0 |
2/1/08 |
HGM |
Governance overview |
| 7.1 |
2/7/08 |
HGM |
PMO definition update |
PMO Quality Management Discipline and Policies
Introduction
The project management office (PMO) upholds the IT service-oriented architecture and enterprise, which is the basic framework and structure for all IT-related activities and projects. The philosophy is service, centered on customer satisfaction and quality.
The PMO provides training and the quality management discipline to plan and control through testing and continuous improvement to ensure that each project satisfies the needs for which it was undertaken (PMBOK® measure of quality).
The scope of quality management includes the following:
- Quality planning.
- Quality control.
- Quality assurance.
These quality elements interact with each other and with each of the project management disciplines.
Concept Map of PMO Quality Management Tools and Techniques (Project Management Institute, 2004)
Benefits
The project management office:
- Identifies the requirements that will satisfy the needs of the project.
- Identifies which quality standards are relevant to the project such as ISO 9001:2000 and CMMI.
- Measures and monitors specific project outputs to determine if they comply with relevant project quality metrics and standards and comply within the variance thresholds.
- Tests, evaluates, and validates all project outputs and overall project performance.
- Documents quality management strategies and measurements that can be collected, reviewed, and archived for reference in future projects.
Guidelines and Procedures
| Step |
Action |
Responsible personnel |
| 1 |
Review project scope and deliverable specifications. |
PM |
| 2 |
Assemble organization quality policies, standards, and regulations. |
PM |
| 3 |
Describe process using inputs and outputs in particular team disciplines (tools and techniques). |
PM and project team |
| 4 |
Analyze outputs from steps 1, 2, and 3 and create a list of operational definition of quality. |
PM and project team |
| 5 |
Compile items in a list and sort into logical groupings. |
PM and project team |
| 6 |
Create the checklist that various project team members can use to inspect quality. |
PM and project team |
| 7 |
Develop a quality statement on how quality management and quality plan will be implemented. |
PM and project team |
| 8 |
Develop a quality control procedure on how to examine specific project results to see if they comply with the quality standards and to identify means to eliminate any error or unsatisfactory results. |
Quality audit team |
| 9 |
Establish quality assurance by evaluating project performance on a regular basis to provide confidence that the project will satisfy the quality standards previously set. |
Quality audit team |
Quality Assurance Template
Quality Assurance Plan for [Project Name]
Prepared by: Date:
1.0 Draft quality assurance plan.
1.1 Introduction.
1.2 Purpose.
1.3 Policy statement.
1.4 Scope.
2.0 Management.
2.1 Organizational structure.
2.2 Roles and responsibilities.
2.2.1 Technical monitor/senior management.
2.2.2 Task leader.
2.2.3 Quality assurance team.
2.2.3 Technical staff.
3.0 Required documentation.
4.0 Quality assurance procedures.
4.1 Walkthrough procedure.
4.2 Review process.
4.2.1 Review procedures.
4.3 Audit process.
4.3.1 Audit procedures.
4.4 Evaluation process.
4.5 Process improvement.
5.0 Problem reporting procedures.
5.1 Noncompliance reporting procedures.
6.0 Quality assurance metrics.
Appendix.
Quality assurance check list forms.
Configuration and Change Management Policies
All projects will have to adopt the project management office (PMO) change control system process and procedures. Project change requests go through the process and approval of the change control board (CCB).
PMO’s change control system is a formal process with documented procedures that defines how a project Scope Statement (original, defined, and signed by project sponsors) must be maintained when the need for changes occur. The process includes steps by which the official Project Scope Statement document may be changed. The process also includes all electronic/paperwork tracking systems, processes, and approval levels necessary for authorizing changes.
Concept Map of PMO Change Control Tools and Techniques (Project Management Institute, 2004)
Completing a change-request form template is a requirement for this process. User (Change) requests are submitted to the change control board (CCB) for approval.
Change Request Form Template
Project Name:
Date Request Submitted:
Title of Change Request
Change Order Number:
Submitted by: (name and contact information)
Change Category: Scope Schedule Cost Technology Other
Description of change requested:
Events that made this change necessary or desirable:
Justification for the change/why it is needed/desired to continue/complete the project:
Impact of the proposed change on:
Scope:
Schedule:
Cost:
Staffing:
Risk:
Other:
Suggested implementation if the change request is approved:
Required approvals:
| Name/Title |
Date |
Approve/Reject |
| |
|
|
| |
|
|
| |
|
|
| |
|
|
References
Project Management Institute. (2004). A guide to the project management book of knowledge (3rd ed.). Newtown Square, PA: Author.
Schwalbe, K. (2007). Information technology project management (5th ed.). Boston: Thomson.