Getta Byte Software Project: Case Study in Management & Implementation, Exams of Software Engineering

A detailed case study of the getta byte software project, focusing on project management principles and software implementation. It outlines project goals, objectives, stakeholder engagement, communication plans, scope definition, work breakdown structure, scheduling, resource allocation, budget reports, and risk management. A comprehensive overview of the project's lifecycle, highlighting key milestones, challenges, and solutions.

Typology: Exams

2024/2025

Available from 03/18/2025

denis-kinyua-3
denis-kinyua-3 🇿🇦

1

(2)

3.9K documents

1 / 35

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Running Head: GETTA BYTE SOFTWARE PROJECT PART 1
Running Head: GETTA
BYTE SOFTWARE
PROJECT PART 1 2023
LATEST VERSION
Alyssa Miller
DeVry University
Professor Silas MGMT 404
October 21, 2020
Getta Byte Software Project
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23

Partial preview of the text

Download Getta Byte Software Project: Case Study in Management & Implementation and more Exams Software Engineering in PDF only on Docsity!

Running Head: GETTA BYTE SOFTWARE PROJECT PART 1

Running Head: GETTA

BYTE SOFTWARE

PROJECT PART 1 2023

LATEST VERSION

Alyssa Miller DeVry University Professor Silas – MGMT 404 October 21, 2020 Getta Byte Software Project

Getta Byte Software Project

Table of Contents

  1. Introduction................................................................................................................................... 3

1.1 Project goals and objectives .................................................................................................. 3 1.2 Management of the project ................................................................................................... 4 1.3 Internal and external factors that may affect processes and procedure of the project ....... 4

2 Stakeholder Engagement Plan ................................................................................................... 10

3 Communication management plan ............................................................................................ 11

4 Project Scope Statement............................................................................................................. 13

5 WBS and the Project Schedule ...................................................................................................... 16

5.1 WBS ..................................................................................................................................... 16 5.2 Project scheduling ............................................................................................................... 18

6 Resource Allocations and Budget Reports.............................................................................

6.1 Budget Reports………………………………………………………………………..

7 Risk Register……………………………………………………………………………

8 Conclusion…………………………………………………………………………….

10 References……………………………………………………………………………..

Getta Byte Software Project

1.2 Management of the project The project manager will be liable in carrying out the entire project. The project manager shall then appoint their team such as the human resource manager, the software engineer, the project coordinator and assigns objective tasks within the project. Each team member will be responsible in their area of operation and to ensure their task is completely efficiently and accurately in accordance with the project objectives. The project manager role shall be to oversee the entire process and therefore identifying the key stakeholders- such as the CEP, CFO, Finance, Billing and Customer Service is important within the project. Ensuring that there is great communication between the team will help establish a clear direction for the project and stable leadership roles from the project manager. Having a clear direction can ensure that the team is aware of the objections and goals of the project and everyone can give their best effort in completing a successful project.

1.3 Internal and external factors that may affect processes and procedure of the project As the project progresses and develops it is important to identify the potential internal and external factors that may pose risks and challenges to the project. These risks or challenges can make decisions within the project more difficult to carry out procedures and tasks. One of the risks that have been identified as an external factor is the potential of a network issue when transferring data into the new system. Since the new software is online based it is important to note that the network must be up and running to have a smooth-running project. The potential of a network problem would absolutely affect the rate at which data is transferred and the replacement process.

Another factor that needs to be considered is security to the network. Since the software is online the risk of online hacking increases. This is an external factor that need to be put into

Getta Byte Software Project

consideration when building up the system and will certainly affect budget and time management. This factor also gives to the teams already tight budget so minimizing any additional unnecessary cost will be important to attain the set goal budget.

An internal factor that can be controlled and risks can be minimized is thru proper communication. With good communication the team can stay on the team objective and goals as well as ensuring their assigned tasks are completed and on target.

Getta Byte Software Project Project Charter

e) Train the personnel^ •^ Transferring the data

  • Recruiting the personnel
  • • Developing the training manual using vendorScheduling the training for all CSR’s f) Go live^ •^ Carrying out training
  • the software shall be released into the production and go live *****The project is scheduled for final release by September 10th** September 1st.. Go live on

Objectives

Implementing Getta Byte Software online billing system, that will enhance speed and accuracy in data management. The Project Objectives are as follows: ❖ Stay within the budget of $ 250,000 for the entire project and ensure that the endobjective is attained within the set budget ❖ To ensure that there is an increased benefit of serving the customers quickly andaddressing the issues of inaccurate data. ❖ ❖ To ensure that the project go live by 10To reduce labor needs by 25% and therefore, ensuring that the company maximizes onth^ of September profits earned. ❖ Dynamic updates to receivables.

Milestones In order to attain the overall set objectives, the following are major milestones that shall be attained with the following dates: a) Requirements from users gathered by 5th^ August 2020 b) Appropriate vendor selected by 7th^ August 2020 c) Purchase the software by 10th^ August 2020 d) Customization tested by 15th^ August 2020 e) Data transferred to cloud and validated by 20th^ August 2020 f) Data transferred to cloud and map fields by 21st^ August 2020 g) Appropriate personnel recruited by 22nd^ August 2020 h) Appropriate manual for training developed by 25th^ August 2020 i) The first pilot done by 1st^ September 2020, Final release on 10th^ September

Budget

Getta Byte Software Project Project Charter

The budget estimation was adopted using the top-down method. The following gives budget estimation for the entire project.

Estimated Labor $40, Estimated Materials $120, Estimated Contractors $20, Estimated Equipment and Facilities $20, Estimated Travel $50, Total Estimated Cost $250,

User Acceptance Criteria ❖ First pilot done by 1st^ September ❖ Ensure the software has the highest level of security and protects the data from theft ❖ The software to reduce the labor requirement by 25% ❖ The software to reduce billing cycles by 30%. ❖ The project to be completed within the set budget

High-Level Project Assumptions

High-Level Project Constraints

  • The system shall be secure and it shall not be susceptible to hacking
  • The project first pilot will be completed by 1st^ September 2020
  • All data transferred will be accurate
  • The software shall be working properly without collapsing
  • Personnel shall be hired and trained appropriately -.
  • Getting the software live may take longer than expected
  • Finding the appropriate vendor for the software may prove to be aproblem
  • The software may not be working appropriately
  • The Budget of $250,000 may not be sufficient
  • The subcontractors may not deliver services on time

Getta Byte Software Project Project Charter

Type Name Signature Project Manager Approval

Instructor

Customer/Sponsor Approval

Getta Byte

APPROVALS

Date

2 Stakeholder Engagement Plan

Project Name: Project Manager: Alyssa Miller Getta Byte Software project Date: 09/07/

Who

Getta Byte Software Project Project Charter

What How Who When Other

Dayse RosarioCEO KeyHigh HighNeutral Inform Meeting and Mail Project teamWeekly

Getta Byte Software Project Project Charter

Accounts PayableBilling PrimaryHigh HighSupport Manage Meeting and Mail Project teamDaily

Finance DepartmentReporting PrimaryHigh HighAgainst Satisfy Meeting and Mail Project teamWeekly

Accounting teamProcessing Primary High HighSupport Satisfy Meeting and Mail Project teamDaily

Getta Byte Software Project Project Charter

Sales teamSales SecondaryMedium HighNeutral Monitor Meeting and Mail Project teamWeekly

Ima PayneTeam member Key High HighSupport Manage Meeting and Mail Project teamDaily

Hugh DuittTeam member Key Medium LowSupport Manage Meeting and Mail Project teamDaily

Getta Byte Software Project Project Charter

Weekly status meetingProject Team Communicate updated project status Project managerMeeting

DistributionVehicle External?Internal / Comments

Weekly

Informing stakeholders on the progress of the project External Steering Committee Review CEO, CFO, Finance, Director sales, Prospect, Manager, Data architect updating the team on the status of the project Project managerMeeting

Steering committeeWeekly status report

Monthly External

CEO, CFO, Finance, Director sales, Prospect, Manager, Data architect Status updates regarding the current timelines, key accomplishments, planned works

Project manager^ Weekly E-mail Weekly updates Team stand-up reports Project Team members

Internal Only

Discuss on the achievements of the team members in attained in the previous day Daily Heads of departmentMeetings

The teams to present a summary report regarding all that has been attained in the last 24 hours^ Internal Only Project Review meeting All departmental heads To provide feedbacks regarding project deliverables and discussing the subsequent stage Bi-Weekly Project managerMeetings

Review on the milestones and attainment to be done in the meeting^ Internal Only Project Postmortem Report Meeting Head of Departments Analyzing on what was attained, the achievement and the failures after project completion Monthly Project managerMeeting

Review on the milestones and attainment to be done in the meeting^ Internal & External Daily mails

Getta Byte Software Project Project Charter

Project team Informing all team members on the progress, work to be done, among other important information

Project manager and project teams^ Bi-Weekly Mail only Mails send to individual or another project teamProject kick-off meeting Project team and stakeholders

Internal & External

introducing the project targets and goals to the team members and stakeholders Once Project managerMeetings

Project objectives and aims shall be clearly stated and outlined to the team members and stakeholders^ Internal & External Technical meetings Project technical team Reviewing and discussing on various technical matters that are affecting the progress of the project Weekly Project Technical managerMeetings

Technical matters which affect different departments shall be discussed during this meeting^ Internal Only Stakeholder update meeting Stakeholders Updating stakeholders on the status and the plan of the project Bi-Weekly Project managerMeetings

The stakeholders updated on various issues affecting the progress of the project^ Internal External Board Members meeting Board members Discussing the financial status and progress made and solving matters related to different certification Bi-Monthly Project managerMeetings

All board members updated on schedule meetingsProject Monthly status report Project Team

Internal External

Giving monthly updates regarding achievement and status of the project Monthly Project managerMeetings

informing the project team regarding the attainment and monthly progress^ Internal External Newsletter Wider development updating the wider development on various achievement and what is being offered by the project Once Project communication teamMeetings Internal External

Getta Byte Software project

Getta an online automated system. The project is cloud based and information can be entered online and Byte Software project to implementing and replacing the current manual billing system with accessed elsewhere by any of the permitted users. The system will be fast speed and accurate as compared to the current manual system. The billing system will reduce the billing cycle by more than 30% as well as cut the labor monthly cost by 25%.

Project Description

The a) designed system The system must must have fulfill the the capability following of (^) auditingto prove allthat it information is working entered and accordingly: give accurate information to the users b) The reports. system must have the capacity to generate very specific, accurate and dynamic billing

Project Requirements

The project has two main goals or deliverables. These goals include the following: a) the must data be foreliminated all customers must be as accurate as possible. Therefore, all sources of error b) the system should be easily accessed by all billing departments. c) The data stored in the software must be protected with up to date security from hackers and d) theft.The system must operate at a high speed that will increase the processing of data reports and generating the billing reports

Project Deliverables

The a) project will The financial not include the records will be following: out of scope of this project b) c) WillDatabase not include regarding the 10 financial years paystubs statements of ofall companycompany employees and related information

Project Does Not Include (Exclusions)

4 Project Scope Statement Scope Statement Project Name Getta Byte Software project Date Project Number 725215 Project Manager Alyssa Miller

Getta Byte Software project

Estimated Project Schedule Milestones Estimated Date of Completion a) The project begins on 1 st^ August 2020 b) Requirements from users gathered by 5 th^ August 2020 c) Appropriate vendor selected by 7 th^ August 2020 d) Purchase the software by 10 th^ August 2020 e) Customization tested by 15 th^ August 2020 f) Data transferred to cloud and validated by 20 th^ August 2020 g) Data transferred to cloud and map fields by 21 st^ August 2020 h) Appropriate personnel recruited by 22 nd^ August 2020 i) Appropriate manual for training developed in accordance to the vendor by 25 th^ August 2020 j) The product goes live by 1 st^ September 2020

The estimated completion date is 1 st^ September 2020

Total Estimated Length of Project 30 days Resource Requirements Role Quantity^ Estimated Length of Time Project manager 1 30 days IT specialists 2 30 days Software engineer 1 30 days Billing software 1 30 days Complete Desktops 10 30 days Human Resource manager 1 30 days Laborers 10 15 days

❖ The software to go live by 1 st^ September ❖ The software has highest level of security and protection from data hackers. ❖ The software to reduce the labor requirement by 25% The^ ❖ project to^ The software to have a reduced level of being hacked. be completed within the set budget of $250,000.

Acceptance Criteria