Page 1 of 11
PROJECT CHARTER TABLE OF CONTENTS
1.1 Introduction .................................................................................................................... 2 1.2 Purpose of Project Charter/ Client’s introduction ......................................... 2 1.3 Project And Product Overview/Background ................................................. 2 2.0. Justification ..................................................................................................................... 2 2.1. Business Need ........................................................................................................ 2 2.2. Public role and Business Impact .......................................................................... 2 2.3. Strategic Alignment ................................................................................................ 3 3.0. Scope ................................................................................................................................ 3 3.1. Objectives ................................................................................................................ 3 3.2. High-Level Requirements ...................................................................................... 3 3.3. Major Deliverables .................................................................................................. 3 3.4. Boundaries ............................................................................................................... 4 3.5. Functional and Non Functional Requirements ................................................... 4 4.0. Duration .......................................................................................................................... 5 4.1. Timeline .................................................................................................................... 5 4.2. Executive Milestones ............................................................................................. 5 4.3. Gantt chart ................................................................................................................. 5 5.0. Budget Estimate ............................................................................................................. 7 5.1. Funding Source ....................................................................................................... 7 5.2. Estimate ................................................................................................................... 7 5.3. .. High-Level Alternatives Analysis………………………………………………7 6.0. Assumptions, Constraints, And Risks .......................................................................... 7 6.1. Assumptions ............................................................................................................ 7 6.2. Constraints ............................................................................................................... 8 6.3. Risks ......................................................................................................................... 8 7.0. Project Organization ..................................................................................................... 8 7.1. Key Stakeholder, Roles and Responsibilities .................................................... 8 7.2. Stakeholders (Internal and External) ................................................................... 9
8.0. PROJECT CHARTER APPROVAL ............................................................................ 10 APPENDIX A: REFERENCES .................................................................................................10
Page 2 of 11
1.1 INTRODUCTION 1.2 PURPOSE OF PROJECT CHARTER/ CLIENT’S INTRODUCTION The purpose of the charter is to provide a detail description of the android application for pre-ordering beverages and breakfast. It will drafted by the project manager. The project charter would be presented to Mr. Andrew (client) as the main audience to facilitate approval and financially support the project. The project will clearly describe the scope of the project which will include a project overview, justifications, budget estimates, risk management, business case, objectives, deliverables, and project organization.
1.3 PROJECT AND PRODUCT OVERVIEW / BACKGROUNG The project title is Lacafé’ android application hosting three types of beverages (tea, coffees, drinks). The application will be installed in an automated payment machine located near the service bay of the café. The implementation of the project will help the customers to pre-order their beverages and pay them before they consume. The project duration will be 6 months from design to project closure. The project estimated to cost a budget of about $16,310.00.
2.0. JUSTIFICATION 2.1. BUSINESS NEED The changes in technology have prompted many businesses to adapt to news to serve their customers well. The rising number of customers who need to be served quickly and conveniently at all times has prompted La café to implement a preordering system that customers can pay in advance for drinks. The systems expected to capture more customers in the morning which in the long run increase revenues for the business.
2.2. PUBLIC ROLE AND BUSINESS IMPACT The system application will collect customer personal information that which will be used for making marketing information. Many customers will be conveniently be using the service at all times thus increase in revenues. On health, customers will be provided with choices to make on beverages and drinks that suit their lifestyles. The application will also facilitate integration in which feedbacks and customer reviews and recommendations will be possible enabling corrective measures and customer loyalty.
Page 3 of 11
2.3. STRATEGIC ALIGNMENT Goal Project Response Rank
Comments
Scale: H – High, M- Medium, L – Low, N/A – Not Applicable Division / Branch Strategic Goals: To generate more revenues for his business H The main focus of the project Hospitality Strategic Goals: To target more customers especially in the morning as this will be a convenient way of pre-ordering their beverages and picking them up at the café counter M The output resulting from the main goal IT Goals: To create an android application for preordering beverages and breakfast L External influence of the project
3.0. SCOPE 3.1. OBJECTIVES The objectives of La café android application project are as follows: To create an android application for pre-ordering beverages and breakfast within a period of 6 months To come up with a suitable pre-ordering service that will target more customers conveniently they can pick the products at the café counter. To design an application that can record customer services by registering their personal information and contact details. To create integrative application that allows customer reviews, and feedbacks 3.2. HIGH-LEVEL REQUIREMENTS The following table presents the requirements that the project’s product, service or result must meet in order for the project objectives to be satisfied. Req. # I Requirement Description 001 Drafting of project proposal 002 Sourcing of appropriate application software developer 002 IT infrastructural purchase 003 Staff trainings
3.3. MAJOR DELIVERABLES The following table presents the major deliverables that the project’s product, service or result must meet in order for the project objectives to be satisfied.
Page 4 of 11
Major Deliverable I Deliverable Description Drafting of project proposal/plan Writing of formal proposal for funding Create android application Sourcing of appropriate application that can perform on project objectives and implementation of both prototype and completed application software Creating awareness Training staff on how the software will be working t to help in service provision
3.4. BOUNDARIES
Exclusions: Creation of awareness of the software, training customers, financial support.
Inclusions: they include: project proposal development, application software development, piloting of prototype application, integration and implementation of the application software, and training staff on its usage.
3.5. FUNCTIONAL AND NON FUNCTIONAL REQUIREMENTS Functional requirements:
User Friendly Software design and development New Customer Sign Up Existing Customer Login Pre-ordering of beverages and breakfast Online Bill Payments Confirmation of Payment and Order Customer review and feedback Social media integration Local-based alerts Non-functional requirements:
Staff training resources
User manual
Appropriate Android devices
Technical staff
Computer aided infrastructure
Page 5 of 11
4.0. DURATION
4.1. TIMELINE
4.2. EXECUTIVE MILESTONES The table below lists the high-level Executive Milestones of the project and their estimated completion timeframe.
Executive Milestones Estimated Completion Timeframe
The project proposal and project plan are accepted and approved.
The project proposal is after one week after the inception of the idea. The project plan will be two weeks after the proposal has been approved.
Completed of project infrastructural requirements
Will take place three-week and five days after project has been developed Prototype testing Will take place four weeks after obtaining all requirements of the project Capacity training and implementation of the actual project It will take place three weeks after prototype testing Project closure One month after full implementation and reviews
4.3. GANTT CHART The Gantt chart is a useful scheduling tool that provides how activities will be performed in diagrammatic form.
15/3/2017 30/3/2017 09/4/2017 05/8/2017
System Development Completed Project closureDeveloped Prototype and awareness
Requirements Analysis Completed
Project Plan Completed
15/09/2017
Page 6 of 11
Start Wed 3/15/17
Finish Thu 9/15/17
Apr '17 May '17 Jun '17 Jul '17 Aug '17
Project proposal development
Completed infrastructure Tue 4/4/17 - Tue 5/9/17
Prototype testing Fri 5/5/17 - Thu 6/15/17
Capacity trainings & implementation Fri 6/16/17 - Fri project closure Fri 7/14/17 - Thu 8/24/17
Today
Page 7 of 11
5.0. BUDGET ESTIMATE 5.1. FUNDING SOURCE The source is operational and baseline information’s
5.2. ESTIMATE This section provides an overview of the expected cost to meet the objectives of the La café’ android application project as described in this project charter. This summary of spending is preliminary and should reflect costs for the entire investment lifecycle.
Object Code
Budget Item Qtr1 Qtr2 Qtr3 Qtr4 Total
010 Stationary supplies $50 $30 $10 $15 $105.00 020 IT infrastructures purchases $- $5,000 $- $- $5,000.00 030 Contractual agreements $6,500 $ - $ - $1,000 $7,500.00 040 Transportation of things….. $ - $200 $300 $ - $500.00 050 Rent, Telecom, Other Comm & Utilities….. $50 $40 $20 $50 $160.00 060 Printing & Reproduction…… $50 $40 $10 $50 $150.00 070 Materials supplies $20 $60 $45 $25 $150.00 080 Hires and consultancy $1,000 &500 &500 $200 $1,200.00 090 Salaries and wages $400 $300 $250 $400 $1,350.00 Total $8,020.00 5,640.00 $ 625.00 $ 1,725.00 $ 16,010.00 $
5.3. HIGH-LEVEL ALTERNATIVES ANALYSIS During the development of the android application, the project team did benchmarking. A visit to one of the Macdonald restaurants and checking how the La café android application works were done. The benchmarking activity provided intelligence gathering that a replica will be designed to serve a distinctive function. Macdonald application is automated menu selected software that customers can use to choose different meals and pay for them before collecting them.
6.0. ASSUMPTIONS, CONSTRAINTS, AND RISKS 6.1. ASSUMPTIONS The project will make assumptions that the system will integrate well with organization structures, and customers will have a positive response towards.
1. Implementation of the system must be able to integrate well with the current operations, procedures, and culture.
Page 8 of 11
2. The success of the system will depend on how positive the customers will embrace and use it. The project assumes that they will be doing so.
6.2. CONSTRAINTS The major constraint of the study is on time required to implement the project. The technical staff required will be of technical know-how and have required knowledge and skills.
6.3. RISKS The sections address some of the risks that the project will face and provides mitigation mechanisms for them.
Risk Mitigation Resistance of the employees Proper training will be conducted to create awareness and reduce work conflicts
Changes in technology A good system software application will be adopted that will take consideration of changes in technology in the future.
Competitions from the industry
Proper marketing strategies will be employed in conjunction with the software
7.0. PROJECT ORGANIZATION 7.1. KEY STAKEHOLDERS, ROLES AND RESPONSIBILITIES This section describes the key roles supporting the project. Name & Organization Project Role Project Responsibilities Mr. Andrew- La Café restaurant Project Sponsor The person responsible for acting as the project user. The person is expected to approve the project, consulted on the project specifications. He will be needed to provide the required resources to support the project. X project management organization Project manager WHITE, K. (2014), stated that a person who performs the day-to-day management of the project and has specific accountability for managing the project within the approved constraints of scope, quality, time and cost, to deliver the specified requirements,
Page 9 of 11
Name & Organization
Project Role Project Responsibilities
deliverables and customer satisfaction. Document and implements the project proposal and plan
Y. Legal institution
Contracting legal Officer
According to WHITE, K. (2014), a person who has the authority to enter into, terminate, or change a contractual agreement on behalf of the restaurant. This person mediates any agreement between any parties involved with the project.
Various contractors/ subcontractors
Consultancy role Persons from different institutions or organizations that need to provide additional extra knowledge and advice. E.g. researchers, technicians, software analysts, trainers.
Employees of La café restaurant
Technical roles Persons who are responsible for the technical day-to-day aspects of the system including the details of system implementations. The Technical employees are responsible for providing technical service and corporations to the project. (Schwalbe, K., 2015).
La café IT technical employee
IT Security Steward
A person who is responsible for playing the lead role in maintaining the project’s information technology security and work in consultation with the project team. (Schwalbe, K., 2015).
7.2. STAKEHOLDERS (INTERNAL AND EXTERNAL) There are a number of stakeholders who will be within or outside the project who will be affected directly or indirectly. Examples of internal stakeholders include: Project sponsor who will provide resources and project specifications La Café employees- will be needed to co-operate and run the system Technical employee- provide necessary IT support to the project Examples of external stakeholders include: Project team- who will ensure project is delivered as per specifications Customers- will be needed to embrace the new technology Consultants- they will provide technical assistance and advice on various matters to the project Sub-contractors-work together with a project to ensure specific deliverables are achieved.
Page 10 of 11
8.0. PROJECT CHARTER APPROVAL APPENDIX A: REFERENCES The following table summarizes the documents referenced in this document. Document Name and Version Description Location
Coghlan, D., & Brannick, T. (2014). Doing action research in your own organization. Sage.
Was a useful book in explaining the business case in the charter (p.3)
https://scholar.google.com/sch olar?q=project+organizations+ and+roles&btnG=&hl=en&as_ sdt=0%2C5&as_ylo=2013
Franklin, A. S., Steiner, M., & Perlow, J. D. (2015). U.S. Patent Application No. 14/844,231.
Used to explain the contractual needs of any IT application development pp.8
https://scholar.google.com/sch olar?as_ylo=2013&q=RESTA URANT+APPLICATION+SOF TWARES&hl=en&as_sdt=0,5
HEAGNEY, J. (2016). AN OVERVIEW OF PROJECT MANAGEMENT. In Fundamentals of Project Management (pp. 1-24). New York; Atlanta; Brussels; Chicago; Mexico City; San Francisco; Shanghai; Tokyo; Toronto; Washington, D.C.: AMACOM Division of American Management Association International
It was a useful document that helped to follow project steps and techniques
Retrieved from http://www.jstor.org/stable/j.ctt1d 2dpw4.5
Hughes, J. F., Van Dam, A., Foley, J. D., & Feiner, S. K. (2014). Computer graphics: principles and practice. Pearson Education.
Useful in explaining various constraints facing software applications development and implementations (pp.7)
https://scholar.google.com/schola r?q=constraints+of+COMPUTER +APPLICATIONS&btnG=&hl=e n&as_sdt=0%2C5&as_ylo=2013
Ngai, E. W. T., Suk, F. F. C., & Lo, S. Y. Y. (2017). Development of an RFID-based sushi management system: The case of a conveyor-belt sushi restaurant. International Journal of Production Economics, 112(2), 630-645
The reference was used to describe the requirements of the project charter pp.4
https://scholar.google.com/sch olar?hl=en&q=RESTAURANT +APPLICATION+SOFTWARE S&btnG=&as_sdt=1%2C5&as _sdtp=
Spirin, G., & McGregor, J. (2013). U.S. Patent No. 8,498,900. Washington, DC: U.S. Patent and Trademark Office.
It was used in the project charter to explain the need for securing information’s (pp.9).
https://scholar.google.com/sch olar?as_ylo=2013&q=RESTA URANT+APPLICATION+SOF TWARES&hl=en&as_sdt=0,5
Schwalbe, K. (2015). Information Useful in explaining https://scholar.google.com/sch
Page 11 of 11
technology project management. Cengage Learning.
the role of information technology in projects
olar?q=project+organizations+ and+roles&btnG=&hl=en&as_ sdt=0%2C5&as_ylo=2013
Too, E. G., & Weaver, P. (2014). The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), 1382-1394.
A useful component in describing project organizations and roles in projects (pp.8-9)
https://scholar.google.com/sch olar?q=project+organizations+ and+roles&btnG=&hl=en&as_ sdt=0%2C5&as_ylo=2013
Verbeke, A., & Tung, V. (2013). The Future of Stakeholder Management Theory: A Temporal Perspective. Journal of Business Ethics, 112(3), 529-543.
The source provided guidance on how to identify stakeholder in an establishment (p.9)
Retrieved from http://www.jstor.org/stable/233 27338
WEI, L., & CHEN, W. (2014). Internet Cafés. In Esarey A. & Kluver R. (Eds.), The Internet in China: Cultural, Political, and Social Dimensions (1980s2000s) (pp. 204-210). Great Barrington, Massachusetts: Berkshire
The source provided baseline information on creating exclusions and inclusions of the project (pp.5)
Retrieved from http://www.jstor.org/stable/j.ctt 1j0pt3f.31
WHITE, K. (2014). Why IT Matters: Project Management for Information Technology. In DINSMORE P. & CABANISBREWIN J. (Eds.), The AMA Handbook of Project Management (pp. 479-490). New York; Atlanta; Brussels; Chicago; Mexico City; San Francisco; Shanghai; Tokyo; Toronto; Washington, D.C.: AMACOM Division of American Management Association International.
It provided a guideline of how to write project charter for projects
Retrieved from http://www.jstor.org/stable/j.ctt1d 2qzkc.54
Wright, C. (2016). Enterprise risk management (ERM) frameworks. In Fundamentals of Information Security Risk Management Auditing: An introduction for managers and auditors (pp. 3142). IT Governance Publishing.
The information was used to explain the risks found in café when implementing softwares (pp.8)
Retrieved from http://www.jstor.org/stable/j.ctt1b j4t5n.8