MGMT 404 Getta Byte Software Project Part 2, Exams of Software Project Management

Download MGMT 404 Getta Byte Software Project Part 2 and more Exams Software Project Management in PDF only on Docsity!

Getta Byte Software Project _Course Project Part 2 Student Name University Affiliation Course Code: Course Title Instructor Name Due Date

Getta Byte Software Project _Course Project Part 2

Introduction

This Software project was established with the goal of developing new software for the organization, among other things. The method that is in placed used for billing is entirely manual, takes an inordinate amount of time, and has shown to be erroneous in recent years. Creating a new system that is automatic, time-sensitive, and accurate is the purpose of this project. There are numerous phases and considerations that will go into the development of this new program. In addition, there are a few aspects that might either impede or encourage the success of specific actions and outcomes. Some of these considerations are money as well as timeline.

Project Description and Project Product The project intents to transform the available system to a new system prior the end of the year. The new system will be fully automated, as well as quick and accurate. Objectives In some cases, switching from paper to electronic billing will reduce costs because it will save on time for the labor and at the same time increase profits through accuracy as well as increasing trustworthiness from more consumers while reducing costs by saving time and increasing efficiency in billing. Milestones October 15th^ – Develop and test system November 1st, do the first pilot November 10th,^ hold the final release Budget Approximated project’s budget is expected to be $350,000. The budget is based on estimates due to unforeseen circumstances which might lead to additional expenses. The goal is to operate below the projected budget, therefore, completing the project within the facility of the organization will help to reduce cost such as travel expenses. Projected Labor $70, Projected Material $70, Projected Contractors $70, Projected Equipment and Facilities

Projected Travel $70, Total Projected Expenses $350, User Acceptance Criteria When it comes to navigation, the system ought to be easy as well as simple for the employees

to utilize while also enhancing the speed of transaction by about 30 percent. Customer confidence in the success of their accounts billing cycle is also dependent on the accuracy of the results provided to them by the system. High-Level Project Assumptions The organization must make the assumption that the majority of their present client information is correct. The reason for this is that it will be prohibitively expensive and time- consuming to evaluate and study all of the present data, so we have chosen not to do so. Using the current data and assuming it is accurate, the project will save significantly on both the budget and the projected duration. High-Level Project Constraints The budget is considered the most significant constraint, as it limits the project's ability to be flexible. The timetable constitutes another constraint because time has been set aside for specific tasks, and if one job takes longer than expected to complete, it may cause the remaining time frame of the project to be extended. Exclusions and Boundaries Everything, including account receivable and the current financial system, will be able to remain the same save for the changeover to interface. In this project, the focus is to modernize the billing system. Changes to the financial system will not be permitted under the new structure. Major Risks The transfer of information in to the new system from paper is the major risk. This is a risk because information is likely to get lost during the transfer process and this may result in errors.. Key Stakeholders Manager of the project Manager of the project

 E-mail  Meetings. However, other modes of communication which could be used include: use of phone conversations, use of business forums, as well as expression forms. The communication management strategy for this project is as follows:

Section D: The Project Scope Statement

The project scope helps in defining specifics regarding the entire work necessary to properly execute the project. Defining as well as regulating the information flowing in and out of the project is essential in generating an effective project scope appropriate for the project. If you have finished the project scope document, you should have a better overall grasp of the project: Scope Statement Name of the Project Getta Byte Software Project. Date: 1/31/ Project Code or number Manager of the project

Project Description The project intents to convert the existing system to the new one. The new system will be fully automated, as well as quick and accurate. In place of the current manual billing system, a new cloud-based billing system should be implemented. Project Requirements In order to complete this project, two requirements must be met: -Auditing capabilities for auditing -Creating specialized reports. Project Deliverables The new system should be able to send appropriate information to all of its clients. All billing representatives must be able to access the system at all times. Additionally, it should be a cloud-based solution. (Exclusions) Excludes financial record’s system Acceptance Criteria In addition to being easy to use, the new system must also enhance transaction performance by 30% and also provide reporting and reduce bill cycles by about 30%. Projected project Schedule Milestones Projected Completion date

• Completion of the development -Data is migrated in to cloud. -Initial pilot is completed The project is completed
  • 15th^ August 2021 -August 25 2021 -1st^ September 2021 -10 September 2021 Estimated Duration of the time

Section E: (WBS) and Project Schedule

A work breakdown structure (WBS) can be quite useful for scheduling projects since it allows you to easily sub-divide the deliverables to manageable chunks that are easier to manage. It is an excellent tool for developing a framework for the project schedule (Fitzpatrick, 2016). The project's milestones are one of its most important components. There are six essential milestones to reach for the Getta Bill: finalize specifications, purchasing the software, customizing the software, transferring the data to cloud, training the staff, as well as launching the project. The project is scheduled to begin on February 18th and conclude on September 3rd,

according to the current plan.

respond in each case (Kerzner, 2019). I feel that I've gained a vast amount of fresh knowledge about businesses and the processes that go into developing new products, software, or undertaking any other initiatives. The process is certainly more difficult than anticipated, but not quite as difficult as I had anticipated it would be at this point in time. Once you have a basic understanding of project management, it is a valuable skill set to have in order to advance your firm or career in the business sector. References Fitzpatrick, B. J. (2016). Determining the optimal work breakdown structure for defense acquisition contracts. https://doi.org/10.21236/ad Kerzner, H. (2019). Innovation project management: Methods, case studies, and tools for managing innovation projects. John Wiley & Sons. Kuchta, D., & Ptaszyńska, E. (2017). Fuzzy based risk register for construction project risk assessment. https://doi.org/10.1063/1.

Martinelli, R. J., & Milosevic, D. Z. (2016). Project management toolbox: Tools and techniques for the practicing project manager. John Wiley & Sons. Thommen, J. (2015). 1 stakeholder-management. Glaubwürdigkeit im Stakeholder-Management , 11-46. https://doi.org/10.24096/9783039097227-