Viking project charter

Viking Project Charter


Viking Project Charter

Table of Contents
1 Project Description...........................................................................................................3
2 Project Scope....................................................................................................................3
3 Project Stakeholders.........................................................................................................3
4 Project Approach..............................................................................................................4
4.1 Roles and Responsibilities.........................................................................................4
4.2 Timeline.....................................................................................................................5
4.3 Costs..........................................................................................................................5
5 Risks.................................................................................................................................5
6 Assumptions......................................................................................................................5

Page 2 of 5


Viking Project Charter

1 Project Description
The objective of this project is to deliver the Viking product to market within 6 months
of the kick-off of this project, and within budget. Viking will be a multi-function project
management tool (PMT) developed and sold to customers in many business sectors,
initially including aerospace-defense companies. Viking improves project management
processes by providing the following functionality: action item management, to-do lists,
risk and defect tracking, architecture, design, and test documentation management, and
lessons learned reflections. The Viking project deliverables include the software
application, user documentation (installation and user guide), and training material.
Viking is intended to run on any desktop/laptop, Personal Digital Assistant (PDAs), and

multi function (mobile) phone.

2 Project Scope
The scope of the Viking project is to:
•
•
•
•
•

Create the Viking software product
Test the Viking product, including engineering test, system test and beta test.
Develop Viking all user and administrative documentation and training material
Produce Viking product CD(s) containing the Viking system and soft
documentation
Prepare the material required to support the Viking product (hopefully it will be
supported by ABC Systems)

3 Project Stakeholders
The following table lists Viking’s stakeholders and criteria for completion and
success of this project. These measures will be further refined as the project team
reviews this charter with all stakeholders and as additional project detail is defined.

Stakeholder

Project Completion/Success

Customer

•

•

Project Management

•

(Program Manager,
Portfolio
Manager, Project
Manager)

•
•
•

Viking will achieve time to market within 6 months
All high-priority functionality defined in the
requirements specification is delivered in the first
release
There is no impact on organizational resources or
projects.
Total project cost does not exceed 10% of the initial
budget.
The actual project duration is within 10% percent of the
committed duration.
Product passes acceptance criteria defined by 80% of
beta site evaluators.
Page 3 of 5

Viking Project Charter
Stakeholder
Project Team

Project Completion/Success
•
•
•
•

ABC Management

•
•
•

Product Manager

•
•

Total project cost does not exceed 10% of the initial
budget.
The actual project duration is within 10% percent of the
committed duration.
Viking supports defined quality criteria and test
measures.
Customer satisfaction - Product passes all acceptance
criteria defined by beta site customers.
Customer requirements are met

Customer is pleased with the Viking product that they
receive
Viking supports all high priority requirements in initial
release.
All high-priority functionality defined in the
requirements specification is delivered in the first
release
All deliverables are completed as described in the initial
release

4 Project Approach
As the project plan is further refined, the project will be divided into logical units of
work based on the selected project management and development methodology.
The following sections identify the required roles, timeline, and cost to develop Viking
as well as provide ongoing maintenance and support.

4.1 Roles and Responsibilities
This section identifies the project roles and responsibilities required for this project.

Role

Responsibility

President (Sponsor)

•
•

Project Manager

•
•
•

System Architect

•
•

Budget approval
Owner of the overall business change that is being
supported by the project
Creates and maintains project plan
Oversees day-to-day operations
Ensures tools and methodologies are being adhered
to
Reports status
System design and development oversight

Page 4 of 5


Viking Project Charter
Role

Responsibility

System Analyst

•

Develop and refine use cases

Developers

•

Testers

•
•

Technical Writer

•
•
•

Development and unit and integration testing of
Viking
Creates and maintains test plan
Works with end users and system analysts to
identify test populations and scenarios
Writes test scripts
System testing
Internal documentation and system documentation

Functional Management

•

Provide resources

4.2 Timeline
Viking will be developed with an iterative approach. The development timeline is 6
months. Maintenance releases are scheduled to be every 4 months after a full release.

4.3 Costs
Costs are tbd.

5 Risks
Risks are tbd.

6 Assumptions
Assumptions are tbd.

Page 5 of 5