Project Proposal-Part 3

Running head: PROJECT PROPOSAL 1

PROJECT PROPOSAL 2

Project Proposal-Part 1

Student Name

Institution Affiliation

Project Proposal

I have been assigned a task to lead the development of customized data management software as the project manager. The opportunity is an honor and it requires commitment and patience to deliver the best customized software that would meet the customer needs and attract most customers. The project would take at least 12 months because of the activities and engagements involved. Companies have been having a problem choosing data management software that is combatable to their operations and their choices always fails leaving gaps and vulnerabilities that becomes a threat to data security. The project focuses on developing customized data management software that take into considerations all the small details of the firm and develop the combatable one to make sure that it works best in delivering value. I was given the project management role because of my professional expertise in Software development and to achieve the desired goals require the support of other experts in IT and also resources.

The project goals are to deliver quality software that meets customer needs and also create transformational software that the market would consider to acquire and implement. The objectives include having customized software that make work effective in an organization and also have combatable data management software for the data available (Smith, 2020). The key customers of the data management software include small and big companies, corporations and government institutions. The product is fit for the broad type of organization because of the customization that adjusts to the divergent needs of each of them. The stakeholders of the data management software project include the company management, team members, sponsors, external customers that is different firms and employees who are the one responsible for implementing.

The data management software project has to follow the following key milestones that include the requirement gathering, implementation and the user acceptance testing. The requirement gathering is essential where the data about the customer (company) that require the software to make sure all the business requirements and essential details including number of employees and current data volume and expected future changes (Rogers et al., 2015) Implementation milestone is key to make sure it’s in place for testing and validation. Finally user acceptances testing which is essential to make sure those users are comfortable with the software (Cerdeiral & Santos, 2019). The project process is long and involves various activities and processes that has their distinct timelines as stated in the table below

Key Tasks	Timeline
Brainstorming	2 months
Requirements Gathering	1 month
Validation of expected requirements	1 month
Predevelopment planning	1 month and 2 weeks
Implementation	2 months
Quality assurance testing	1 month
User acceptance testing	1 month 2 weeks
Deployment	2 months

The timeline and key tasks are essential in achieving the required software project and the deployment of the software to the whole organization takes the longer time of two months because it require consultation and implementation in different sectors and departments. Quality assurance and user acceptance testing are important tasks that must be followed to comply with government requirements and also meet the needs of the user because it must be of simple and efficient usability software.

The success of the project require staff that have the required skills this include software developers, IT staff and data experts. The total staff required for the team is ten skilled officials. Equipments needed include computers, internet connections and a resource center for research. The staff payment is approximately $150,000 each coming to a total of $1,500,000 after the 12 months. The other resources needed including research sum up to $200,000 and the total budget is $1,700,000.

References

Cerdeiral, C., & Santos, G. (2019). Software project management in high maturity: A systematic literature mapping. Journal Of Systems And Software, 148, 56-87. https://doi.org/10.1016/j.jss.2018.10.002

Rogers, P., Pawlik, L., & Shwom, B. (2015). The Role of Deliverables in Project Work. SSRN Electronic Journal. https://doi.org/10.2139/ssrn.2576748

Smith, T. (2020). What Are 8 Milestones Every Software Project Should Have? - SOLTECH. SOLTECH. Retrieved 16 November 2020, from https://soltech.net/what-are-8-milestones-every-software-project-should-have/.