MGMT 404 GETTA BYTE SOFTWARE PROJECT FINAL, Papers of Software Engineering

Download MGMT 404 GETTA BYTE SOFTWARE PROJECT FINAL and more Papers Software Engineering in PDF only on Docsity!

Running Head: Getta Byte Software project Crystal Persad Devry University Professor Teodor Sauca 26 th^ August, 2020 Getta Byte Software Project

Contents

• 1. Introduction..............................................................................................................................
  • 1.1 Project goals and objectives..............................................................................................
  • 1.2 Management of the project...............................................................................................
  • 1.3 Internal and external factors that may affect processes and procedure of the project......
• 2 Stakeholder Engagement Plan...............................................................................................
• 3 Communication management plan........................................................................................
• 4 Project Scope Statement........................................................................................................
• 5 WBS And the Project Schedule.............................................................................................
  • 5.1 WBS................................................................................................................................
  • 5.2 Project scheduling...........................................................................................................
• 6 Resource Allocation...............................................................................................................
• 7 Cost Overview.......................................................................................................................
• 8 Risk Register..........................................................................................................................
• 9 Conclusion.............................................................................................................................
• 10 References..............................................................................................................................

ease of the software shall be done by September 1st, this will be after having checked all parts that are not in a good working condition and rectify them accordingly. The project is budgeted $ 250, 000 for the entire work. Therefore, the work shall be scheduled accordingly and individual tasks split to enable the project team to carry out all duties with little or no friction. 1.2 Management of the project The project charter shall establish the requirements of the project and the basic needs of the project. In addition, the person who shall be liable of carrying out the entire project is the project manager. The project manager shall then appoint their team such as the human resource manager, the software engineer, the project coordinator and other different people who shall carry out duties assigned to them by the project manager. Each person shall be responsible in their area of operation to make sure that there is smooth running of activities. The project manager role shall be to oversee the entire process and therefore, providing all the resources, including the human resource, material and cost that shall be used in the project. The project manager will also ensure that communication is done and there is adequate control of all the resources provided. 1.3 Internal and external factors that may affect processes and procedure of the project As the project progresses, there is a likelihood that other internal and external factors may pose risks and hence challenging or even controlling the decisions made by the people, processes, project and even the procedure followed when carrying out individual tasks. The first factor is understanding the risks that may come to place or the potential risks that are likely to happen. The project team need to understand the risks that are likely to affect the project so that they can device method that will ensure that the impact of all negative risks is reduced as much as possible. The network issue has been identified as an external factor that may affect the normal operation of the project. It is worth noting that the project is online based and therefore,

network must be provided to ensure that everything is running smoothly as per the project objective. The network problem shall affect the rate at which data is transferred and the replacement process. Another factor, is the hacking of the data and information. This is an external factor that need to be put into consideration when building up the system and hence affecting the processes. Another factor that has to be given consideration is the budget issue. It is worth noting that the budget is a constraint. The project team should come up with procedures and processes that shall take into account the budget issue and hence, minimizing the project cost to attain the set objective. Communication is an internal factor that ensures that everything runs smoothly and in accordance to the plan put in place. The team members have to be given information regarding what is transpiring and what should be done regarding a given task. Proper communication is the main tool that shall ensure that each team member is on the same page and knows what is happening and what they are supposed to do. Communication shall help to fix all issues at the moment they happen. Therefore, all these factors have to be given consideration in terms of project operation, procedure and processes followed in the project.

Getta Byte Software project Project Charter

 the software shall be released into the production and go live The project is scheduled to go live by 1st^ September. Objectives To set up the Getta Byte Software for online billing system, that will enhance speed and accuracy in data management the following shall be major objectives of the project:  To work within a budget of $ 250,000 for the entire project and ensure that the end objective is attained within the set budget  To ensure that there is an increased benefit of serving the customers quickly and addressing the issues of inaccurate data.  To ensure that the project go live by 1st^ September  To reduce labor needs by 25% and therefore, ensuring that the company maximizes on profits earned.  To ensure that there is loyalty to customers and users by delivering accurate information within short period of time. 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 in accordance to the vendor by 25th^ August 2020 i) The product goes live by 1st^ September 2020 Budget In order to complete the project, 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,

Getta Byte Software project Project Charter

Estimated Contractors $20, Estimated Equipment and Facilities

Estimated Travel $50, Total Estimated Cost $250, User Acceptance Criteria  The software to go live by 1st^ September  The software has highest level of security and protects the data from theft  The software to reduce the labor requirement by 25%  The software to have a reduced level of being hacked.  The project to be completed within the prescribed budget High-Level Project Assumptions  The project shall be completed with the prescribed budget  The system shall be secure and it shall not be susceptible to hacking  The project shall be live by 1st^ September 2020  A reasonable vendor for software supply shall be found  The software shall be working properly without collapsing  Personnel shall be hired and trained appropriately  The project shall not have struggles along the way and all risks shall be handled appropriately. High-Level Project Constraints  Getting a license may prove to be a challenge  Passing data security inspection shall be a challenge  Getting the software live may take longer than expected  Finding the appropriate vendor for the software may prove to be a problem  The software may not be working appropriately  The budget might not be enough  The subcontractors may not deliver services on time  The time schedule may not be adequate Exclusions and Boundaries Boundaries:  Minor changes on the software design while the project has already resumed  Removing all unnecessary expenditures that may have big impact on the project  Shortening and extending time if deemed  The software may crash during installation

Getta Byte Software project Project Charter

Getta Byte 18 th^ 07,

2 Stakeholder Engagement Plan Project Name: Getta Byte Software project Project Manager: Crystal Persad Date: 07/18/ Who What How Who When Othe r Stakehold er Stakehold er's Role Catego ry Influen ce High/Lo w Interes t High/Lo w Suppo rt Neutr al Again st Monit or Infor m Satisf y Mana ge Method (e- mail, meetings, posting on collaborati ve site, etc.) Strateg y Owner Frequen cy Note s Damiel Pishem CEO Key High High Neutr al Inform Meeting and Mail Project team Weekly Subcontract ors Supplies Second ary Medium Medium Neutr al Satisfy Posting and mails Project team Daily Kent C. Detrees CFO Key High High Suppo rt Manage Meeting and Mail Project team Daily Lou Seguzi Director Fin Key High High Agains t Manage Postings Project team Daily Accounts Payable Team Billing Primary High High Suppo rt Manage Meeting and Mail Project team Daily Finance Department Reporting Primary High High Agains t Satisfy Meeting and Mail Project team Weekly Accounting team Processing Primary High High Suppo rt Satisfy Meeting and Mail Project team Daily Sales team Sales Second ary Medium High Neutr al Monitor Meeting and Mail Project team Weekly Ima Payne Team member Key High High Suppo rt Manage Meeting and Mail Project team Daily Hugh Duitt Team Key Medium Low Suppo Manage Meeting and Project Daily

3 Communication management plan Getta Byte Software Project Billing software Communication Vehicle Target Audience Description/Purpose Frequency Sender Distributio n Vehicle Internal / External? Comments previous day regarding all that has been attained in the last 24 hours Project Review meeting All departmental heads To provide feedbacks regarding project deliverables and discussing the subsequent stage Bi-Weekly Project manager Meetings Internal Only Review on the milestones and attainment to be done in the meeting Project Post Mortem Report Meeting Head of Departments Analyzing on what was attained, the achievement and the failures after project completion Monthly Project manager Meeting Internal & External Review on the milestones and attainment to be done in the meeting Daily mails Project team Informing all team members on the progress, work to be done, among other important information Bi-Weekly Project manager and project teams Mail only Internal & External Mails send to individual or another project team Project kick-off meeting Project team and stakeholders introducing the project targets and goals to the team members and stakeholders Once Project manager Meetings Internal & External Project objectives and aims shall be clearly stated and outlined to the team members and stakeholders Technical meetings Project technical team Reviewing and discussing on various technical matters that are affecting the progress of the project Weekly Project Technical manager Meetings Internal Only Technical matters which affect different departments shall be discussed during this meeting Stakeholder update meeting Stakeholders Updating stakeholders on the current status and the plan of the project Bi-Weekly Project manager Meetings Internal External The stakeholders shall be informed on various issues affecting the progress of the project Board Members meeting Board members Discussing the financial status and progress made and solving matters related to different certification Bi-Monthly Project manager Meetings Internal External All board members shall be informed on the schedule of this

3 Communication management plan Getta Byte Software Project Billing software Communication Vehicle Target Audience Description/Purpose Frequency Sender Distributio n Vehicle Internal / External? Comments meeting Project Monthly status report Project Team Giving monthly updates regarding achievement and status of the project Monthly Project manager Meetings Internal External informing the project team regarding the attainment and monthly progress Newsletter Wider development updating the wider development on various achievement and what is being offered by the project Once Project communicatio n team Meetings Internal External making newsletter which shall capture all information regarding the project Project Documents Entire project team All documents related to the project When needed Project team members emails Internal Only

Project Does Not Include (Exclusions) The project will not include the following: a) The financial records shall be out of scope of this project b) Shall not include the financial statements and standing of the entire company c) Database regarding 10 years pay slips of employees and related information Acceptance Criteria  The software to go live by 1st^ September  The software has highest level of security and protects the data from theft  The software to reduce the labor requirement by 25%  The software to have a reduced level of being hacked. The project to be completed within the prescribed budget Estimated Project Schedule Milestones Estimated Date of Completion a) The project shall begin on 1st^ August 2020 b) Requirements from users gathered by 5th^ August 2020 c) Appropriate vendor selected by 7th^ August 2020 d) Purchase the software by 10th^ August 2020 e) Customization tested by 15th^ August 2020 f) Data transferred to cloud and validated by 20th^ August 2020 g) Data transferred to cloud and map fields by 21st^ August 2020 h) Appropriate personnel recruited by 22nd^ August 2020 i) Appropriate manual for training developed in accordance to the vendor by 25th^ August 2020 j) The product goes live by 1st^ September 2020 The estimated completion date shall be 1st^ 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 Estimated Cost of Project Expense Type Description Estimated Cost Labor The labor shall include payments made to different people such as engineers, the project manager, IT manager for offering different services required to accomplish the project. The payments shall be made promptly to the parties delivering the services. Other payments such as payment to different services not outlined in this section shall also be termed as labor

Material The material cost shall include but not limited to purchase of all materials such as purchasing of Desktop, the billing software, the testing kit and other materials needed for this purpose

Contractor’s payment Different contractors hired to deliver given services such as connection, processing of licenses and other payment to external parties shall be paid under this bill.

Equipment and Facilities All equipment hired for the purpose of installation shall be paid under this bill. The equipment shall be hired and paid on hourly basis. The facility fee shall also include payment of different venues for meeting and processing all documents required by the project.

Travel cost The travel cost shall facilitate travelling of different parties in delivering project duties. Such travels shall include going for meetings, meeting different stakeholders among other travels as long as they are beneficial to the project

Total Estimated Cost of Project $ 250,

aim of attaining the major goal prescribed in the project charter. However, for the goal to be attained, the tasks have to be split into individual subtask for easy performance. There are several ways through which a WBS can be prepared. This include an outline format, table format and tree format (United States. Bureau of Land Management, 2008). Other project management software such as MS Project prove to be handy in preparing WBS. In this section the WBS was prepared by both manual and using the MS project as follows:

1. Finalize on project requirement 1.1 Gathering the information required by the user 1.2 Gathering the requirements by the customers 1.3 Finalize on project requirement complete
2. Purchase the software 2.1 Selecting the appropriate vendor 2.2 Negotiating the contract with the appropriate vendor 2.3 Executing the purchase 2.4 Purchase the software complete
3. Customize the software 3.1 Defining the features required 3.2 Setting up testing environment

3.3 Developing customization 3.4 Customize the software complete

4. Transfer the data to cloud 4.1 Validating the data 4.2 Creating map fields 4.4 Transferring the data 4.5 Transfer the data to cloud compelete
5. Train the personnel 5.1 Recruiting the personnel 5.2 Developing the training manual using vendor 5.3 Scheduling the training for all CSR’s 5.4 Carrying out training 5.5 Train the personnel complete
6. Go live 6.1 Go live 6.2 Project complete 5.2 Project scheduling Task Name Duration Start Finish Predecessors Getta Byte Software project 23 days Sat 8/1/20 Tue 9/1/ Finalize on project 4 days^ Sat 8/1/20^ Wed 8/5/