Getta Byte Software
The Getta Byte software project charter is a modernized online system characterized by accuracy, speed, automation, and labor-saving. This billing system is best suited to replace the manual mode, which is inefficient, inaccurate, and slow.
It is the company’s mission to maximize profits by lowering labor expenses, speeding up transactions, and generating reports dynamically. The company’s desire to be golden perfectly aligns with the high accuracy, time, and labor-saving Getta Byte software project. Implementation of the project will boost the company’s general productivity; this is to say it is part of a larger project.
PROJECT DESCRIPTION AND PROJECT PRODUCT
The project will create a revolution in the company; output levels will be remarkable, customer satisfaction enhanced, and expenses reduced. The company will rise to the standards of excellence credit to the new project implementation. For the project to be fruitful, professional services will be required. For instance, the project will need a CEO, CFO, financial and specialists, and customer care experts. When this is done, the company will speed up transactions, reduce billing expenses, save on labor, generate reports dynamically, easily record data, and high accuracy will be ascertained.
The project implementation aims to replace the manual, time-consuming, and inaccurate system with an advanced one. The new project will save the company 25% of monthly labor expenses and reduce billing cycles by 30%.
The project requires milestone dates so that the company can work as a team towards achieving the goals. The project’s first pilot should be on September 1st, and the final presentation of the system should be on September 10th. The following is a list of the milestones dates for the project to work
- By June 10th,2020, the design approval by the stakeholders.
- By July 1st, raising of funds.
- By July 15th, hiring skilled personnel and identifying their roles in the project running.
- By July 23rd, conduction of extensive market research for suitable external vendors.
- By July 26th, the workforce should feed the stakeholders with information about the project process.
- By August 1st, measurable performance costs of the system should be determined.
- By August 10th, the system should be able to provide the intended service.
- On August 15th, the project should be ready for testing.
- On September 1st, the first piloting of the project and correcting defects.
10. On September 10th, the new should be available for use and run effectively
For the implementation of the new system, the company needs an estimate of $ 125,000. The amount is, in fact, the only amount available for the task. To complete the project planning, below is a table giving a rough estimate of the order in the magnitude of costs to incur.
|Estimated Equipment and Facilities||$10,000|
|Total Estimated Cost||$115,000|
An estimate of $10,000 will be left to serve as a backup in case of an emergency.
USERS ACCEPTANCE CRITERIA
The stakeholders will aspire to generate reports dynamically, speed up transactions, and obtain a response in time for acceptance. Under the personnel’s critical supervision and inquiry of customers’ satisfaction, the stakeholders should be able to monitor and measure the project quality. Negative feedback from the customers would indicate poor quality delivery of services. An increase in customer satisfaction by 80%, a 100% increase in profit, and an expense decrease of 50% is an indicator of success.
HIGH-LEVEL PROJECT ASSUMPTIONS
The project is based on the assumption that customers’ data in the former system is accurate. It is also expected that transactions will be faster, easy entry of data, reports will be generated regularly, labor expenses and billing cycles are to reduce, accuracy improved, and customers’ satisfaction.
HIGH LEVEL PROJECT CONSTRAINTS
The limiting factors in the project execution include; capital, network problems, inability to change financial records, unreliable customer data. The project is bound to obey the following rules;
- Flexibility of the system,
- Modifications and improvement with time,
- Adherence to the plan,
- Working with urgency,
- Visualizing the project deliverables and communicating,
- Regular assessment of risk,
- Ensuring open communications,
- Law- abiding,
- Keeping track of time, budget and quality.
EXCLUSION AND BOUNDARIES
The project boundary will include hiring skilled personnel, a reliable network, and a joint agreement among the stakeholders. However, the project will exclude the following;
- Training of the personnel,
- Construction of the premise,
- Changing the financial system of record,
- Hiring more staff,
- Installing a loyalty program,
- Power backup in the event of failure,
- Addition of extra equipment and facilities,
- Renewing the contractor.
The project will face the following risks during implementation;
- Possible funds deficiency,
- Network problems,
- Inaccurate customer data,
- Transferring data from paper records to the system problems,
- Time scheduling and estimation limitations,
- Possible procedure risks,
- Account receivable risks,
- Unpredictable rise in needs,
- Technical issues.
|Project Manager Authority Level||Staffing, budget management, conflict resolution and making technical decisions.|
|Project Core Team||They are responsible for the project’s success by playing the roles assigned to them. The project core team includes the CEO, CFO, finance, billing, and customer care experts.|
|Subject Matter Experts (SMEs)||Electricians will need electrical cables and accessories. IT experts require network cables and efficient equipment such as computers and backup to install the software program.|
|Project Manager Approval.|