PROJECT CHARTER
Defect Management Systems Version: 1.0 Revision Date: 19th September, 2007 (Initial Version)
Defect Management Systems
Page 2 of 6
Table of Contents Section 1. Project Overview ..................................................................................3 1.1 1.2 1.3 1.4 1.5
Project Details .....................................................................................3 Project Purpose...................................................................................3 Project Objectives ...............................................................................3 Project Phases ....................................................................................3 Project Scope: .....................................................................................4
Section 2. Project Authority and Milestones ..........................................................4 2.1 2.2
Funding Authority ................................................................................4 Major Project Milestones.....................................................................4
Section 3. Project Organization .............................................................................5 3.1 3.2
Project Structure .................................................................................5 Roles and Responsibilities ..................................................................5
Section 4. Revision History....................................................................................6
Group #9 Kiriakidis
Project Charter_ Version 1.0 th 19 September, 2009
Defect Management Systems
Page 3 of 6
Section 1. Project Overview 1.1
Project Details The preliminary project details are as follows: Project Title: Defect Management System Project Start Date: September 19, 2007 Project End Date: May 26, 2008 (Expected project completion date) Project Manager: Daniel O’Leary
1.2
Project Purpose The purpose of the ‘Defect management System’ project is threefold: a. To standardize the way in which defects are managed across projects within the company. b. To allow defects to be managed more efficiently within projects thereby increasing project productivity. c.
1.3
To allow upper management (and customers) greater visibility into defects encountered which will enable them to keep project on course and draw important conclusions to effectively manage future projects.
Project Objectives The main objective of this project is to develop and implement an intranet based system that will
allow defects encountered to be registered and tracked them to closure. This system will be access constrained with different access levels assigned on the basis of role and responsibilities of the person accessing the system.
1.4
Project Phases The following project phases have been identified to successfully complete this project: 1.4.1 Require Gathering Phase: This phase will include gathering requirements, documenting and reviewing the final scope statement. 1.4.2 Design Phase: This phase will include preparing the system design and specific documentation and review.
Group #9 Kiriakidis
Project Charter_ Version 1.0 th 19 September, 2009
Defect Management Systems
Page 4 of 6
1.4.3 Development and Testing Phase: This Phase will involve developing the code based on requirements definition and design specifications. The code will then be tested against existing in house projects. 1.4.4 Implementation: After the testing phase is completed, the system will be deployed on the company’s intranet so that it can be accessed by the various projects executed in the company. 1.4.5 Training: Training will be provided to specific people across projects to help them understand and use the system more effectively and efficiently.
1.5
Project Scope: The defect management system will cater to all existing projects being executed at the time of implementation and those that will be execute in the future. Projects completed before the implementation of the Defect Management System are currently not within the scope of the project. Also, the system will only serve to manage defects for client projects executed within the company and will not serve as a defect management tool for the Consulting Services provided by the company to its external clients. In the Training Phase, training will be provided to key people identified within various projects and who will then be expected to provide training to their team members.
Section 2. Project Authority and Milestones 2.1
Funding Authority
A capital budget of $1, 40,000 has been planned to be allocated for the Defect Management System project. The funding will be approved and authorized by the sponsor and CEO ok JKRD Solutions, Dwayne Whitten. 2.2
Major Project Milestones
The major project milestones to be covered during the course of this project are as listed below:
Group #9 Kiriakidis
Milestone/Deliverable
Target Date
Project Scope Statement
November 15, 2007
Design Document and Specifications
Design 31, 2007
Project Development and Testing
March 25, 2008
Project Implementation and Training
May 3, 2008
Project Charter_ Version 1.0 th 19 September, 2009
Defect Management Systems
Page 5 of 6
Section 3. Project Organization 3.1
Project Structure The CEO of JKRD Solutions will be the main sponsor and authority for this project. The Project Manager and Business Analysts will work together to come up with the project scope and report to the CEO for final approval. The Technical Architect and DBA will come up with system design once the project scope is approved and requirement definition is completed. They will report to the project manager for review and final approval of the system design. The technical architect and database designer will lead a staff of system developers to build, test and implement the system. The following graph gives the organizational structure of the project team and stakeholders
CEO (Sponsor)
Project Manager
Business/Risk Analyst
Technical Architect
DBA
In-House Developers/Staff
3.2
In-House Developers/Staff
Staff
Roles and Responsibilities
The following table gives an overview of the roles and responsibilities of the project tem and stakeholders.
Group #9 Kiriakidis
Name
Role
Position
Dwayne Whitten
Sponsor
JKRD Solutions, CEO
Daniel O’Leary
Project Manager
Project Manager
Jui Tataria
Technical Architect
Systems Analyst/Technical Architect
Kunal Desai
Business/Risk Analyst
Business/Risk Analyst
Reena Pinto
DBA/In-House Developer
DBA
Contact
Project Charter_ Version 1.0 th 19 September, 2009
Defect Management Systems
Page 6 of 6
Section 4. Revision History
Group #9 Kiriakidis
Version
Date
1.0
19 Sept, 2007
th
Name
Description
Daniel O’Leary
Project Charter – Initial Version
Project Charter_ Version 1.0 th 19 September, 2009