PROJECT CHARTER
1.0 PROJECT IDENTIFICATION
Name
Build New Content Management System
Description
Design, develop, test and launch new CMS and retire old CMS
Project Manager
Shilpa G.
Project Team
Resources
Product Owners, Technical Writer, DBA,
Developers, Testing team, Localization
team and content strategist
PROJECT SCOPE
§Define roles and responsibilities
§Create the article template which are user friendly
§Content creation and workflow management
§Permission to different level users as per roles and responsibilities
§Supporting and training materials
§Localization workflow for global customers
§Integration with the image repository system
2.0 BUSINESS REASONS FOR PROJECT
§Retire old CMS system as costly to maintain and add new features
§Archive the old, expired articles and reduce the system burden
§Implement better Taxonomy system for articles
§Build a better customer experience by creating good contents
3.0 PROJECT OBJECTIVES (PURPOSE)
§Overall, to create a better Content Management system for internal users
§Build user friendly article templates
§To develop tools, guidelines and support the content strategist and producers’ teams
§To develop a CMS with managed content creation area (White and black project area)
§Improve the content management system experience for technical writers
§Build a collaborative content review and approval process
§Add a localization workflow
4.0 Measurable project objectives and related success criteria
Objective
Success Criteria
Templates
are
developed
by
September
2nd
1. Creation of 4 templates for creating contents for different content types and
regions
2. CMS access permission is set up no later than September 2, 2020
3. The completion rate has to be 99.9%
White and
Black
Project
areas
1. White and black content creation areas are created as we will need to restrict
certain content types during NPI.
2. Only Manager approved users can have access to Black project area
3. No more than 10 people can work in Black project area
Content
Creation
and
approvals
1. Content Creation should do in English Master format only
2. After creating a content, it should be approved by 5 different reviewers before
publishing
3. There should be a product tagging system build in the content creation workflow
which further helps to find the product tagged contents. We have 100 products
and their child product so the tagging has to be 2 level tagging.
Localizatio
n workflow
1. After publishing an article, writer should be able to send
2. After creating a content, it should be approved by 5 different reviewers before
publishing
3. There should be a product tagging system build in the content creation workflow
which further helps to find the product tagged contents. We have 100 products
and their child product so the tagging has to be 2 level tagging.
5.0 HIGH LEVEL REQUIRMENT
1. Permissions Levels
§ Access should be given by admin only
§ Approval from management is needed to access black project visibility
§ Reviewers should have the permission to comment on the article
2. Template requirements
§ Pre-made, easy to access templates are created
§ Template should have title, description, image as mandatory fields
§ Tagging system is incorporated with the article properties field
§ Meta data tagging is available
3. Content Approval workflow
§ Content should be created in English only
§ Content should go through the 5 levels of approval before goes public
§ Only Technical writer should be able to publish the final approved copy of article
5.0 HIGH LEVEL REQUIRMENT
4. Article Properties
§ User should be able to tag the article with the product hierarchy
§ User should be able to mark the article public or private
§ User should be able to tag the article with countries it can be shown
6.0 Assumptions and constraints
Assumptions
§ A core development team will full time work on the new CMS development team
§ Project team will have training and support which will be needed to execute this project
§ Project budget will reflect the external cost but not the internal cost for available devices and
software for development and testing purpose
§ Collaboration will be exit between design, test and launch team
Constraints
§ The training and support must be acquired within given budget and timeframe
§ The new CMS must be aligned with the old CMS system for data migration purposes
§ The project team will be working with offshore teams so need to manage the different time
zones so need to work collaboratively
§ Team will have some other projects needs and availability of some team members can be
challenging so need to have backup resource in place
7.0 RISKS
Severity
Description
High
Template customization could be challenging as it has to be aligned with old CMS system
High
Permission grant for different users and different work area to access content
Medium
Authorization workflow may fail if not responded in given time limit
Low
Implementation timelines
Medium
Availability of resources as geographically located teams
High
Stakeholder communication and updates
8.0 MILESTONE DATES
Item
Major Events / Milestones
Start Date
End date
1.
Project Planning
5/28/2020
5/30/2020
2.
Establish a project team
6/1/2020
6/3/2020
3.
Obtain the training
6/4/2020
6/5/2020
4.
Development a communication plan
6/6/2020
6/10/2020
5.
Requirement gathering and review
6/10/2020
6/19/2020
6.
Development and testing
7/20/2020
8/20/2020
7.
UAT testing
8/21/2020.
8/29/2020
8.
New CMS launch
9.
Post Production bug fixes
9/2/2020
9/3/2020
9. Budget
Project Phases
Estimates ($)
Planning and
Documentation
15,000
Development
and testing
90,000
System
Integration cost
10,000
Training Cost
10,000
Other Expenses
5,000
Estimated Cost
130,000