Project Charter

TEXAS PROJECT DELIVERY FRAMEWORK

PROJECT CHARTER

Faculty of Computer Science and EngineeringWP7 mobile application for private

documentsVERSION: 1.0 REVISION DATE: 04.03.2012

Approver Name Title Signature Date

[Agency/Organization Name] PROJECT CHARTER[Project Name] v1.0, 04.03.2012

ContentsSection 1. Project Overview................................................................................1

1.1 Problem Statement.............................Error! Bookmark not defined.1.2 Project Description.............................Error! Bookmark not defined.1.3 Project Goals and Objectives.............Error! Bookmark not defined.1.4 Project Scope.....................................Error! Bookmark not defined.1.5 Critical Success Factors.....................Error! Bookmark not defined.1.6 Assumptions.......................................Error! Bookmark not defined.1.7 Constraints.........................................Error! Bookmark not defined.

Section 2. Project Authority and Milestones........................................................1

2.1 Funding Authority...............................................................................12.2 Project Oversight Authority................................................................12.3 Major Project Milestones....................................................................1

Section 3. Project Organization..........................................................................1

3.1 Team Structure..................................................................................13.2 Roles and Responsibilities.................................................................1

Section 4. Points of Contact................................................................................1

Section 5. Glossary.............................................................................................1

Section 6. Revision History.................................................................................1

Section 7. Appendices........................................................................................1

Based on DIR Document 10PC-T1-5 Page i


Section 1. Project Overview1.1 Problem Statement

Today you need to remember many passwords. You need a password for your operating system logon, your e-mail account, other online passwords (like some website member account), etc. The list is endless. Also, it’s recommended that you use different passwords for each account.

So, there is a security concern for this matter. Actually, to avoid remembering lots and lots of passwords, people tend to choose one password for every purpose, or even worse, very weak passwords.

This is the solution to all that and more.

1.2 Project Description

The delivered software will be intuitive and easy to use password manager for Windows Phone 7.The application will store your passwords in an encrypted database which can be easily transferred from one device to another if necessary.

It will support password groups or categories, which means you can organize your passwords (for example into Windows, Internet, My Website, etc.). The program will come with a strong random password generator and password strength checker. Also, you will be able to store password protected documents.

1.3 Project Goals and ObjectivesWe have identified the following Project Goals and Objectives as being very important for successful implementation of this application. Upon completion of our implementation or within a designated period after the production launch date, we will have accomplished the following Business Objectives:

• Implemented Windows Phone 7 application software which will be effective and user-friendly

• Minimized cost to implement and maintain the application software

• Minimized time to implement the application software

• Adopted best practices or basis for best practice, where possible, during the implementation process

• Provided access to current, precise and complete documentation

Based on DIR Document 10PC-T1-5 Page 1


1.4 Project ScopeProject Includes

The application must have logon functionality and user access control.

The application should work on Windows Phone 7 platform.

The application should allow keeping files with encrypted data which will be protected with password.

The application should include a security mechanism in case of forgetting the master password (security questions and password recovery).

The application must allow deleting data from the files.

The application must allow proper display of the stored data.

The application must allow the user to change the master password.

The application must allow the user to input new data which will be stored.

The application must have groups or categories concerning the stored data.

If the user is idle for more than 10 minutes, or another application is started and shown on the display, the application should log the user off.

The program will come with a strong random password generator and password strength checker.

Project Excludes

The stored data (passwords, document and credit card information) should be entered manually by the user and not directly taken or downloaded from other databases.



1.5 Critical Success Factors

• Adequate resources must be committed to the project.

• The Project Manager, the Project Administrator and the Senior Consultant must lead the project.

• The Junior and Senior developer should comply with the leaders of the project.

• IT infrastructure resources needed for implementation, testing and support must be implemented, as the development environment (Visual Studio 2010) and proper simulator for testing.

• The project team must possess an appropriate mix of skills.

• Regular communication with stakeholders is crucial.

1.6 Assumptions

The developing team will have all the necessary IT resources and equipment to develop and test the project.

1.7 ConstraintsThe budget is the main constraint of the project. Also, there is a specific operating system for the system to be developed and that is Windows Phone 7.



Section 2. Project Authority and Milestones2.1 Funding Authority

Initial budget that this company has to start the project is 3000 euro. The budget is approved by the project manager, who is responsible for managing the process of development. This amount is planned to be used for the necessary resources for developing the software and first month salaries. The method of finance includes monthly payment i.e. payment after every deliverable.

2.2 Project Oversight AuthorityThe developers are controlled by the management team, which is controlled by the Project manager. The team that is in charge for development of the project is also responsible for communication with clients and selling the project. There are no external oversight bodies.

2.3 Major Project Milestones

Milestone/Deliverable Planned Completion Date

Application interface 20.03.2012

Application with the main functions 20.04.2012

Finished mobile application 31.05.2012



Section 3. Project Organization3.1 Team Structure

The Project Team Structure is based on a collaborative team effort, drawing resources and skills from two major groups of students with two main goals: developing the software and managing the process of development. The sub-teams consist of three developers and six managers. Each sub-team has its team leader. Team Leaders will have a specific role in the structure, but in the same time they would be responsible for the management and coaching of that sub-team.

More specifically, the managing team will have three different roles. The Project Manager will be the person that is over all responsible about the definition and the development of the project. The Project Administrator will work on defining all the functionalities of the project in more details than the Project Manager. He will be responsible for the risks, problems, issues, defining the milestones etc. The Senior Consultant will be responsible for the budget, communication with the client (and the supplier in the same time) and communication with the developers.

We have two types of developers: Senior and Junior. Senior Developer should be a kind of a team leader for the Junior Developers. He should try to resolve their issues before asking the managing team for help.


Junior Developer

Senior Developer

Project Manager

Project Senior Consultant


3.2 Roles and ResponsibilitiesRole Responsibility

Project Manager

Managing and leading the project team. Detailed project planning and control including. Developing and maintaining a detailed project plan.

Managing project deliverables in line with the project plan. Recording and managing project issues and escalating where

necessary.

Resolving cross-functional issues at project level. Monitoring project progress and performance. Providing status reports if necessary. Managing project training within the defined budget. Managing consultancy input within the defined budget. Final approval of the design specification. Working closely with users to ensure the project meets business

needs.

Project Administrator

To work with the Project Manager on defining and executing development requirements.

Produces consolidated reporting, including milestone summary, key issues, risks, benefits, summary of costs incurred.

Establishes standards, tools and procedures for use on the project, including Issue, Risk, Change and Information Management.

Reviews project activities for compliance with procedures and standards.

Manages the support and provision of project tools and equipment. Manages data security, software and license control. Assists with the production of user documentation. Assists with testing.

Senior Consultant

Makes effective use of supplier resources within the approved budget.

Tracks performance of developers and takes appropriate action. Ensures that there are clear communication paths within the project

team and the organisation and supplier. Acts as main point of contact between the supplier and the

organisation. Produces and monitors financial reports.

Senior Developer

Supporting and mentoring junior staff in development work. Regular communication with the Senior Consultant. Developing the application. Testing the application. Preparing deliverables in the predicted time. Problem solving skills.

Junior Developer

Finishing tasks in time. Developing the application. Regular communication with the Senior Developer and the Senior

Consultant.



Responsibility matrix:

Task/Role Project Manager

Project Administrator

Senior Consultant

Senior Developer

Junior Developer

Project Management H H H - -

Deliverables H H M H H

Budget H L H - -

Documentation M H M L L

Risks/ Issues H L H - -

Team Leading H H H M -

Testing L H - H M

Key: H (High), Medium (M), L (Low), - None

Team members and their roles:



Section 4. Points of Contact



Section 5. Glossary

Task– every member of the developer team will be assigned a specific task or problem that he has to solve. Every member will have approximately three tasks in a month.

Milestone – specific period of time that defines duration and the end date for completing task or deliverable.

Deliverable – part of the final project that contains some functionalities, but not all of them. It is predicted that we will have three deliverables.

Budget – virtual money that will be spent for salary and other resources. At the same time they will be earned by finishing deliverables and selling the project. The project budget starts with 3000 Euros.

Project manager - person that is responsible about the definition and the development of the project.

Project administrator – person that will work with the project manager and will take care of the problems, issues, risks and milestones of the project.

Senior consultant – person responsible for the budget, communication with the client (and the supplier in the same time) and communication with the developers.

Senior developer – person who is responsible for the tasks of junior developers. He has more experience in programming.

Junior developer – person who solves the given tasks.

Supplier – person who provides the resources for developing the project. At the same time, he is the client who buys it.

Team leader – all the members of the managing team and the senior developers are kind of team leaders. The senior developer leads the junior developers, and the managing team leads the developing team.



Section 6. Revision HistoryVersion Date Name Description



Section 7. Appendices


Date post:	26-Aug-2014
Category:	Documents
Upload:	vivijana-stojanovik
View:	36 times
Download:	0 times

Project Charter

Documents