Project Charter

For
Multi-platform Kanban Taskboard

Version 1.0

Prepared by Harsh Seth

CSI 668

September 24, 2010

CSI 668 Topics in System Architecture, Fall 2010

Project Charter for Multi-platform Kanban Taskboard

Page ii

Table of Contents
1. Project Description.......................................................................................................... 1
2. Business Objectives and Success Criteria....................................................................... 1
3. Stakeholders.....................................................................................................................1
4. Vision...............................................................................................................................2
5. Project Scope................................................................................................................... 2
6. Functional / Non-Functional Requirements:................................................................... 2
7. Constraints.......................................................................................................................3
8. Milestones........................................................................................................................3
9. Business Risks.................................................................................................................3
10. Resources.......................................................................................................................4
Approvals............................................................................................................................4
Revision History.................................................................................................................5

Project Charter for Multi-platform Kanban Taskboard

Page 1

1. Project Description
The aim of the project is to design and implement a functional prototype for visualizing and
operating a multi-platform virtual "Kanban Taskboard. Kanban is an agile methodology for
visualizing, managing and optimizing the flow of software requirements for a given application
and for distributing the associated work among the development team.
The Kanban Taskboard should be operated entirely through a web interface, and partially
through other technologies. It should be possible to integrate it simply with some team tasks
repository. The Kanban Taskboard should have reports with team performance indicators for
development activities, and is expected to generate activity and work outcome reports.
The project should additionally focus on selecting and implementing tracking and team
productivity metrics. The Kanban methodology should be used by the team itself for the
Kanban Taskboard development. The project should focus on interfaces and algorithms (not
on technologies), as well as on architecture design.

2. Business Objectives and Success Criteria

There are many organizations that have software development teams spread across the globe.
The communication and management of tasks among such teams is a project managers
nightmare, and the existing tools for communication like email, messengers do not provide a
comprehensive collaborative environment for early detection of potential problems or for
measuring progress.
Our objective for this project is to design and implement a functional prototype for visualizing
and operating a multi-platform virtual Kanban Taskboard to tackle the above mentioned
problems.

3. Stakeholders

Market Demographics

The target audiences are project managers and the development team members spread in
geographically different locations. This implies that most users will be familiar with various
software development methodologies and use of web browsers.

Stakeholder Summary

Project managers are concerned about optimizing the flow of software requirements and
distributing the associated work among the development team, generate activity and work
outcome reports and early detection of bottle-necks and other potential problems in the
development process.
The software development team members are concerned about efficient communication among
them and measuring performance indicators for development activities.

Project Charter for Multi-platform Kanban Taskboard

Stakeholder
Project Sponsor
Project
Coordinator
User Class # 1
Project Manager

User Class # 2
Development
Team Member

Major Benefits

Optimize the
software
development
process
Provide a
comprehensive
view of the
current state of
the project

Page 2

Attitudes

Win Conditions

Constraints

Ability to generate
activity reports and
measure
performance of the
development team
Ability to
communicate with
other team
members and view
the current state of
the project

4. Vision
We envision a multi-platform virtual Kanban Taskboard providing a one-stop location for
project managers and the development team to manage their tasks, generate activity reports,
and collaborate remotely. The interface will be modern and easy to use, without the requirement
to navigate deep into menus to perform simple tasks. A single tool that combines the features
of email, RSS feeds and a virtual task-board is desired.

5. Project Scope
To design and implement a functional prototype for visualizing and operating a multi-platform
virtual Kanban Taskboard to be used by software development teams for collaborating and
distributing the associated work among the development team and optimizing the flow of
software requirements. It shall support integration with other task repositories, notification
mechanisms such as email and RSS feeds as well as generation of activity and work-outcome
reports.

6. Functional / Non-Functional Requirements:

1. Access to the Kanban Taskboard must be available through different technologies:
Web and Mobile access is required and must be developed.
Desktop, Firefox add-in, Eclipse plug-in, Visual Studio plug-in and others are
optional.
2. The Kanban Taskboard should provide an UI that emulates graphically a task board with
tasks written on post-its. Optionally a drag & drop mechanism to move tasks should be
provided.

3. Support to versioning the taskboard and the ability to compare versions should be
provided. Chronological replay of the task board changes is an optional requirement.

4. A reporting mechanism so that team productivity and status can be monitored is needed.
At least 4 reports must be included.

Project Charter for Multi-platform Kanban Taskboard

Page 3

5. Mechanisms to subscribe to task state change must be provided. At least mail

notifications and RSS subscription should be considered.
6. Importing and exporting of the complete backlog and of a given version of the task board
is needed. Excel format is recommended for such imports/exports.

7. Constraints
<Identify known project constraints, such as products to be reused, components to be acquired,
interfaces to other projects or products, or technologies to be employed. Describe the priorities
among the projects features, quality objectives, schedule, staff, and budget. The following table
identifies the parameters around the projects key drivers (top priority objectives), constraints to
work within, and dimensions that can be balanced against each other to achieve the drivers
within the known constraints. Example:>
Constraint
(state limits)

Dimension

Driver
(state objective)

Features

Degree of Freedom
(state allowable range)
70-80% of high priority
features must be included in
release 1.0
70% of user acceptance
tests must pass for release
1.0

Quality

Schedule

release 1.0 to be
available by 10/11

Staff

maximum team size is

6 developers + 4
testers

8. Milestones
Event or Deliverable
Project charter approved
Project plan completed
Project plan approved
Project team assembled
Project execution initiated (Sprint 1)
Project execution completed (Sprint 1)
Customer acceptance
Project closed out

Target
Date
09/24/2010
09/27/2010
09/27/2010
09/27/2010
09/29/2010

Responsibility
Harsh Seth & Hao Shi

12/12/2010

9. Business Risks
<Summarize the major business risks associated with this project, such as marketplace
competition, timing issues, user acceptance, implementation issues, or possible negative
impacts on the business. Estimate the severity of each risks potential impact and identify any
risk mitigation actions that could be taken. This is not the place for the projects overall risk list.>

Project Charter for Multi-platform Kanban Taskboard

Risk

Probability

Page 4

Impact

Mitigation

10. Resources
Resource

Description and Source

Approvals
<Indicate the status of the charter following submission for approval. List the names and
positions of the individuals who must approve the charter, particularly the project sponsor. You
may wish to add some descriptive text to make sure all of these individuals agree on what their
signature of approval means. For example, approving the charter could mean that the signatory
agrees with the content as presented here, agrees to use this charter as a basis for the project,
and agrees to keep the information in the charter current and relevant.>

Approval Decision:

Approved, development of detailed project plan is authorized

Approved, project execution is authorized
Approved, but project is on hold until future notice
Revise charter and resubmit for approval
Charter and project proposal are rejected
Role or Title

Project Coordinator
Project Coordinator

Name and Signature

Prof. Chen

Date

Project Charter for Multi-platform Kanban Taskboard

Page 5

Revision History
Name

Harsh Seth

Date

09/24/2010

Reason For Changes

Created Project Charter

Version

1.0