Document Control

Project Purpose

Charter Document
Title

Document Owner

Project
Template Manager

Author

Date
Drafted
Date
Approved

Version:
Date –
Document
Status
Submitted By:
Created by Revision History
Title [Add the details of the changes you
are making to the table below. Make
the comments as accurate and
meaningful as possible to enable
future users to easily establish the
history of how the document has
developed.]
Date Version Author Comments

Review/Approval
Register
Name Position/Role

Table of Content
Following are the given Table of
Contents for this Project

1 INTRODUCTION.....................................................5

1.1 PROJECT PURPOSE..........................................................................5

2 PLANNING..............................................................6

2.1 AUDIENCE OVERVIEW......................................................................6

2.2 DELIVERABLES...............................................................................6
2.3 REQUIREMENTS..............................................................................7
2.3.1 BUSINESS REQUIREMENTS...................................................................7
2.3.2 FUNCTIONAL REQUIREMENTS................................................................7
2.3.3 NON-FUNCTIONAL REQUIREMENTS..........................................................8
2.4 POTENTIAL RISK.............................................................................8
2.5 TESTING STRATEGY.........................................................................8
2.6 RESOURCES AND TOOLS...................................................................8
2.6.1 TEAM...........................................................................................8
2.6.2 TOOLS..........................................................................................8
2.7 METHODOLOGY ON APPROACH...........................................................8
2.8 PROJECT PLAN...............................................................................8

3 DESIGN AND DEVELOPMENT...................................9

3.1 DESIGN........................................................................................9
3.1.1 VISUAL STYLE.................................................................................9
3.1.2 LAYOUT.........................................................................................9
3.1.3 COLOUR SCHEME..............................................................................9
3.1.4 TYPOGRAPHY.................................................................................10
3.2 DEVELOPMENT AND IMPLEMENTATION...............................................10
3.2.1 TECHNOLOGIES..............................................................................10
3.2.2 ARCHITECTURE..............................................................................10
3.2.3 SITE MAP.....................................................................................10

Project Chart – 0.1 2

4 TESTING AND EVALUATION..................................11

4.1 TESTING.....................................................................................11
4.1.1 FUNCTIONALITY TESTING...................................................................11
4.1.2 USABILITY TESTING.........................................................................11
4.1.3 ACCESSIBILITY TESTING....................................................................11
4.1.4 DEVICE/OS TESTING.......................................................................11
4.1.5 BROWSER TESTING.........................................................................11
4.1.6 PERFORMANCE TESTING....................................................................11
4.1.7 SECURITY TESTING..........................................................................11
4.1.8 REGRESSION TESTING......................................................................11
4.2 EVALUATION................................................................................11

5 APPENDICES........................................................12

5.1 BACKLOG....................................................................................12
5.2 RISK LOG...................................................................................13

styles are maintained. Styles used

for the Section Headings are Heading
Project Overview 1 Heading 2 and Heading 3. Style
used for text is Normal. Any part of
Description source code should use style Code.
Use Caption style to describe images,
figures etc.
Grey italicized text enclosed in
square brackets ([text]) provides To update the Table of Contents,
instructions to the document author, right-click and select “Update field”
or describes the intent, assumptions and choose the option- “Update
and context for content included in entire table”
this document. Guidelines for naming files:
Grey italicized text enclosed in angle Projectname-version-date
brackets (<text>) indicates a field
that should be replaced with
information specific to a project.
Text and tables in black are provided
as boilerplate examples of wording
and formats that may be used or
modified as appropriate to a specific
project. These are offered only as
suggestions to assist in developing
project documents for guidance as a
team; they are not mandatory
formats
To add any new sections to the
document, ensure that the
appropriate header and body text

Project Chart – 0.1 3

1 Introduction
1.1 Project Purpose

1.2 Specific Goals

Project Chart – 0.1 4

2 Planning
2.1 Audience overview
2.2 Deliverables
1. Internal Deliverables:
 Website,
o Mock-up of initial site
o Edition of branding and
colour scheme
o UI design and User
Experience
 Help Desk
o Ticketing system
 Training phase of developers
o Labs and training for
developers to improve
their skills
o HR Training to provide
the best team to our
customers,
 Marketing strategy
o Branding
o SEO campaign
o Service description
o Presentation of the
brand
 Testing stage
o Environments to make
sure we can provide
testing to our products
to ensure quality to our
customers.
2. External Deliverables:
Project Chart – 0.1
 Website
 Performance Tuning Scope
o Planning a proper
process of scoping for
customers
o Proposal template
 Upgrade Scope
o Planning a proper
process of scoping for
customers
o Proposal template
 Customization Scope
o Planning a proper
process of scoping for
customers
o Proposal template
A. Project Deliverables:
Usually, these are deliverables for
the external stakeholders as we do
not have stakeholders, we will make
sure to create a proper deliverables
stages to record progress of our
project.
B. Planning Deliverables:
Management plans for this Project:
 Project Plan
 Work Breakdown Structure
 Website structure strategy
 Designs and Brand
impression
 Copy and Content creation
 Test Performance and
Implementation Reports
Management plans for the Business
- Marketing Strategy
- Human Resources policies
- Operation procedures
5
 - Development processes.
Scheduling, and budgeting, project
artefacts, etc.
C. Activity Deliverables:
Status reports, meetings, reviews,
etc. – To plan and set asap
2.3 Requirements
2.3.1 Business
Requirements
What Business requirements
dynatuners is going to deliver
[Describe here the business
requirements that the project work will
fulfil and how and/or where the
completed project product will fit into
any existing systems. Assign a unique
ID number to each requirement.]
It focuses on the needs and
expectations of the customer
and specifies what the business
wants to achieve. It should also
cover how to meet the
requirements.
2.3.2 Business goals
2.3.3 Company Industry
2.3.4 Product Purpose
2.3.5 Functional
requirements
[Functional requirements capture and
specify specific intended behaviour of
the system being developed. They
Project Chart – 0.1
define things such as system
calculations, data manipulation and
processing, user interface and
interaction with the application, and
other specific functionality that show
how user requirements are satisfied.
Assign a unique ID number to each
requirement.
The requirements set out here are
ranked in “MoSCoW”[1] order:
M – Must Have
S – Should Have
C – Could Have
W – Won’t have]
Must Have
With the use of this acronym, everyone
can see their website project in a
manner that helps them to determine
which parts of the design elements are
the highest priority.
 A pleasing design. Your
website needs to be easy on
the eyes, it's as simple as that.
...
 Mobile friendly layout. ...
 User friendly website
structure. ...
 Great content. ...
 Social media. ...
 Clear and complete contact
info. ...
 About you. ...
 Social proofs.
Should Have and Could Have
6
Once the completion of the user
interface is complete (Must Have), the
website owner and designers can begin
to consider the ‘should have’ features.
Should haves are also a high priority
after the Must Haves are added to the
design since they are the next step in
the entire project’s completion. In fact,
it is at this step that the website can
be launched live to the consumer and
is available to make money. Therefore,
to expedite the ROI on a company’s
site, the company’s reps may
recommend deploying the site without
any of the Could Have deliverables
(desired features but not necessary).
 A Clear Value Proposition.
Tell your visitors exactly what
you do with a clear, easy-to-
find value proposition. ...
 Links to Social Media. ...
 Intuitive Navigation. ...
 Contact Info. ...
 Blog Highlights. ...
 Client Testimonials. ...
 Video. ...
 High-Quality and Original
Images
 User-Friendly Website
Navigation. The most
important element for a good
website is having a user-
friendly navigation. ...
 Web Design and Layout. ...
 Responsive Design. ...
Project Chart – 0.1
 Content Writing. ...
 Call to Action. ...
 Testimonials. ...
 An Opt-In Offer. ...
 Story Telling.
Won’t Have
When web owners and web designers
collaborate on what needs to be done,
they will also review the won’t have
list. The won’t have list will not make it
to the design or development process
for one or more reasons. For instance,
both the design team and the web
owners do not see the value in
delivering these features.
 Automatic Sound / Music. ...
 Splash Pages. ...
 Pop-ups. ...
 Background Images. ...
 No Navigation. ...
 Click and Scroll. ...
 Huge Images. ...
 Animated Banner Ads.
2.3.6 Non-functional
requirements
[In addition to functions required,
describe the characteristics of each
interface between the product and its
users (e.g., required screen
formats/organization, report layouts,
menu structures, error and other
messages, or function keys)]
7
2.4 Potential risk
[Identify possible threats. Split risk
into: EXTERNAL - factors outside of the
project and outside of your control,
INTERNAL - factors internal to the
project and under your control or can
be influenced by you]
INTERNAL:
Human-factor Risk:
Staff is unable to work, it
decrease productivity.
important to
employees because they can be
more productive
motivation and appreciation.
Technological Risk
Physical Risk/Financial is also
included in internal
company can face.
Organisational structure, how
our business is structured can
also mitigate or enhance
business’s success.
Great management can help
reduce all the internal risks.
EXTERNAL:
The Economic factors can affect
a business because, a company
doesn’t have control over the
economy at large.
Political-Legal Factors: Factors
like change in government or
Project Chart – 0.1
their policies and legislation can
impact our business.
Technological developments in
the field and in the wider
business sphere can affect.
When
can
It’s [1] Practice based on software development process - Dynamic
motivate Systems Development Method
after
2.5 Testing strategy
and
[Describe testing objectives,
guidelines roles and responsibilities.
Outline a mechanism for handling
risks a and responding to feedback from
stakeholders on testing progress and
outcomes]
2.6 Resources and tools
Describe needed/assigned resources
to the project: people, equipment,
facilities, funding, or anything else
capable of definition required for the
completion of a project activity.
2.6.1 Team
2.6.2 Tools
2.7 Methodology on
approach
To take advantage of Agile in
the this project, it is important
to first understand what the
term "agile" means. Agile means
8
flexible. When it comes to
project management and
software development, the term
refers to fluidity in the process.
It allows the entire project to be
classified and executed in a way
that is more efficient by dividing
it into recursive cycles, with a
keen focus on continuous
improvement, called "sprints".
Sprints are usually two- to four-
week-long and allow an
extremely productive
development flow because, for
example, instead of discovering
problems and suggesting edits
at the end of the whole project,
you and your developer can
Project Chart – 0.1
become aware of them earlier
and adapt right away.
2.8 Project plan
Here is the Project Plan given with
the breaking of milestones and
timelines, sprint with Gantt Chart will
also be provided after the finalization
of the project plan.
Insert timescale, milestones, task
breakdown and assigned resources.
If possible, create Gantt Chart 1].
2.8.1 Website
Development
1st - Competitive Analysis on
structure
2nd -Strategic Analysis and
Planning
3rd -Information Architecture
4th - Initial Design Wireframe
5th Website Copy & Images
5.1- Graphic and User Interface
Design
5.1.1- Website color
combination and scope of branding
through graphics view
5.1.2 - Logo Design
5.1.3 - Mockup Design
5.1.4 - Animation and info
graphics for mockups
5.2- Content Creation
1
A Gantt chart is helpful when
monitoring a project's progress. A
Gantt chart is a type of bar chart that
illustrates a project schedule. Gantt
charts illustrate the start and finish
dates of the terminal elements and
summary elements of a project.
9
 5.2.1-Content for mockup Competitive Analysis on structure
and Initial Design Wireframe
pages
Creation of a layout and graphical
5.2.2-Content for Marketing design for the website
Structure of the branding image.
5.2.3 -Content for SEO
purpose 2nd - 4th week- (10th - 14th
February) - (17th - 21st February)
6th Implementation
Graphics (images, thumbnails) and
7th-Functional Prototype Content Creation (for each section)
development.
7.1 A complete functional
Back-end and Front-end
website with design, content and development with approved layouts
for the website
functionality.
8th Website Development 5th - 6th Week - (24th - 28th
February) - (2nd - 6th March)
Complete
Testing process on testing
9th Testing environment
User experience report
9.1-Responsive design testing
SEO implementation and structure
9.2 -User Experience Testing process on production
phase
9.3- Design
10th Post Launch Support and 7th Week - (9th - 13th March)
Launch of the website
Maintenance
11th Website Launch
11.1-Hosting
11.2-Domain
12th SEO Implementation
12.1-Off/On page SEO
12.2-Link Building
12.3-Social Media Marketing
12.4-Search Engine Marketing

2.8.2 Time Estimation for

this project

Time-related: 7 weeks project

(estimation based on investigation
of a website project)

1st week- (3rd - 7th February)

Project Chart – 0.1 10

3 Design and Animation and info graphics
for mockups
Development
Content Creation
3.1 Design Content for mockup pages
Website Copy & Images Content for Marketing
Graphic and User Interface Content for SEO purpose
Design
Website color combination 3.1.1 Visual style
and scope of branding 3.1.2 Layout
through graphics view
3.1.3 Colour scheme
Logo Design
Mockup Design

3.1.4 Typography

3.2 Development and implementation

[Insert here description of technologies, frameworks and techniques and any
other related information]
For website Development Structure

Initial Design Wireframe

Page Mockups
Home page
About Us
Services
Performance Tuning
Upgrade
Automation
Customization
Products
Our Clients
Testimonials

Project Chart – 0.1 11

 News
Request a Consultation/Contact Us

3.2.1 Technologies
Wordpress, Theme, plugins, PHP, JQuery, CSS, CSS3, HTML, HTML5

3.2.2 Architecture

3.2.3 Site map

Project Chart – 0.1 12

4 Testing and evaluation

4.1 Testing
[Describe major issues and undertaken methods. Provide description about the
quality of the product or service under test. Use typical testing types:
functionality testing, regression testing, usability testing, accessibility testing,
device testing, browser testing, security testing and performance testing]

4.1.1 Functionality testing

4.1.2 Usability testing

4.1.3 Accessibility testing

4.1.4 Device/OS testing

4.1.5 Browser testing

4.1.6 Performance Testing

4.1.7 Security testing

4.1.8 Regression testing

4.2 Evaluation
[Describe which planned and unplanned objectives and outcomes were achieved,
to identify the factors of success or failure, to assess the sustainability of the
benefits generated, and to draw conclusions that may inform future
programming, policy making and overall organizational learning. What is lesson
learned?]

Project Chart – 0.1 13

5 Appendices

[Insert the name, version number, description, and physical location of any
documents referenced in this document. Add rows to the table as necessary.]

5.1 Backlog
Score as follows, High = H, Medium = M, Low = L]

Id Case Task Priority Status Issues

1
2
3
4
5
6
7
8
9
10

Project Chart – 0.1 14

5.2 Risk Log
[Score as follows, for Likelihood and Impact: High = H, Medium = M, Low = L]

Nature of Likelihood Impact Likelihood Actions required

Risk or High/ High/ x Impact and who will take
Uncertainty Medium/ Medium/ [Score] responsibility to
Low Low manage the risk

Project Chart – 0.1 15