Comprehensive IT Project: Mobile and Desktop App Development Report

This comprehensive IT project report details the development of a mobile and desktop application designed to manage employee professional development for a large company with over 30,000 employees across multiple sites. The project includes a business case, project charter, work breakdown structure (WBS), and project plan, addressing challenges such as stakeholder management, quality control, and transition planning. The report emphasizes the importance of schedule, quality, cost, and stakeholder satisfaction in project success. Key aspects covered include architectural views, quality testing, and the ethical responsibilities of software administrators. The application aims to facilitate communication, improve professional development tracking, and streamline conference documentation submission. The report analyzes the project's stakeholders, including the project manager, management team, and employees, highlighting their roles and contributions to the project's success. The project also addresses potential delays, budget overruns, and the importance of providing useful and secure software to users. The report concludes with references to relevant project management literature.

Running head: COMPREHENSIVE IT PROJECT 1
Comprehensive IT Project
Business Case
The scope of this project is to develop a mobile and desktop app that will be used by the
organization to manage its employees work and social life related to the business. The project
manager has decided to develop a mobile and desktop application to allow for easy access to
project information among its teams (Serra, & Kunc, 2015). The mobile and desktop application
is suitable to this company because it has more than 30, 0000 employees who are distributed
across different sites such as Colorado, Florida, Texas and Illinois. The major problem in
developing this project is that the project has many members but they are not located at one
point, they are distribute in the four sites named above. Therefore, the project manager is tasked
with the duty to control all the project team by developing a system that will allow the company
employees to locate and schedule professional development activities which are relevant to their
positions.
Project Charter and WBS
In order to measure the success of the project to develop mobile and desktop application
the project manager will consider the following objective and subjective process.
Schedule: To ensure that the project to develop mobile and desktop application become
successful, the project manager will have to make sure that they the original timeline is
maintained. Although it is hard to keep the original timeline, as a project manager it is advisable
to continuously keep evaluating the progress of the project. The project manager will be required
to update the project schedule on a regular basis at the end of every phase by reporting it to
senior project stakeholders (Aga, Noorderhaven, & Vallejo, 2016). To make it easier the project

COMPREHENSIVE IT PROJECT 2
manager will built an online Gantt chart whereby each task and its deadline shall be made into
visual timelines. In this sense, the project manager should look at the major milestones to check
whether they still coincide with the originally agreed dates.
Quality: Once every project phase has been completed this is the right time to perform a
quality review. At this point the project manager checks the quality of their project management
practices to determine if they are working in accordance to the change management criteria each
time as well as the deliverables (Joslin, & Müller, 2016). The quality review evaluate the project
to determine that indeed what is being done meets the set standards as stated in the quality plan.
Cost: Many researchers in project management states that cost management is a critical
feature to a project, hence cost evaluation is important. The project manager for the mobile and
desktop app development will have to make comparison between their present and actual
expenditure that had been budgeted. In case there are any variables the project leader will have to
explain these differences (Kristiansen, & Ritala, 2018). At this point the project manager should
re-forecast the budget to the end of the project by comparing the it to the initial estimate to
ensure it is close enough for the management group to feel the work is on track.
Stakeholder satisfaction: Since the mobile and desktop application development team is
large the stakeholders are key towards getting much of the work completed, hence it is
significant that the project manager check in with them to find out their feeling regarding the
present project status and what they could be doing differently. Therefore, stakeholders should
confirm that the application meets all the requirements such as support notifications and allow
company managers to receive notice when their system directly submit report documentations to
the company administrators.

COMPREHENSIVE IT PROJECT 3
Performance to the business case: At the end the project manager will go back to the
business case that is mobile and desktop app development to confirm what they initially agree
upon. This helps to determine if the project benefits are still realistic that indeed the business
problem the project was designed to resolve does not exist (Todorović, Petrović, Mihić,
Obradović, & Bushuyev, 2015). In this case, the mobile and desktop application should solve the
company problem by ensuring that these applications promote relationships and ensure that the
company has representations at important conferences. The developed application will be used
by employees to submit conference documentation to the company. In addition, the developed
application should send employees with notifications about approaching deadline for
professional-development requirements which have not yet been accomplished.
Project plan and requirements
The stakeholders to the mobile and desktop application will include the project manager,
company management team, employees and supporters of resources for this application. These
stakeholders will play a very critical part in this project. Indeed, stakeholders are a vital part to
the project because they help in uncovering and reducing risks hence they increase their buy-in.
In regard to this project, the project manager will be tasked with the responsibility of leading the
project. The management team will be tasked with managing all the resources as well as time
constraints provided by the owner of the project. The employees will be the one in charge of
actually building the application hence they have a very high influence toward the success of the
project. The application development project engage different stakeholders to provide the project
with expertise, uncover and reduce risks, increase project success and grant project acceptance.
According to Eskerod, Huemann, and Ringhofer (2015) stakeholders provide expertise to a
project because they are a wealth of knowledge in regard to the present process, industry insight

COMPREHENSIVE IT PROJECT 4
and historical information. In this context the stakeholders provide the necessary requirements
according to information from the company which is important in helping the project manager
understand the risk and project constraints. Through engagement of the stakeholders in the app
development project they will reduce and uncover risks likely to affect the project. This is
reached out through discussion regarding the needs of the project, initial requirements and
constraints, which are brought up as major concerns (Eskerod, Huemann, Savage, 2015).
Unmasking risks will allow the project leader to discuss on the plan to mitigate them before
arising hence it will dramatically increase the success of the project. Lastly but not least, the
sponsor of this project will be an individual that will be providing resources for the project
because they have enough experience with the type of application and could therefore guild the
project team in the right direction.
Architectural views
The major and most common issue that faces all Information Technology (IT) companies
involved in making mobile apps is about quality control. The reason is because there are a wide
range of devices through which the application will be downloaded and the challenge comes in
whether the app will work on all the devices just like the developed intended. Consequently, this
is the main quality issue that each application development company is likely to experience.
Quality control is a vital phase when it comes to application development, hence to be able to
complete all things within a short span can be a challenging task (Kerzner, 2017). In line to that,
the quality testing team will be allowed the right from the time the project commences, meaning
that after each phase has been completed quality testing shall be performed. Therefore, quality
assurance and project development will be conducted in parallel to ensure that the application is
completed on time with the quality assurance (Paz, & Pow-Sang, 2016).

COMPREHENSIVE IT PROJECT 5
Delays is another issue that is likely to occur during development and implementation
stages because of the project’s complexity hence this will result in budget overpass and extension
of release date.
Transition plan
For a software development company its responsibility is to provide in-depth use of the
software. However, for an administrator their ethical job is to check and ensure the software
being provided by the company is indeed useful for the student or not. In this case the
administrator checks to ascertain if the software actually offer security and all functionalities that
are helpful for the learner (Ljungblom, & Lennerfors, 2018). This is the ethical responsibility of
a university administrator. Hence the administrator should not bother about other things that the
software company is offering. Ethically, the administrator has the responsibility to choose the
functionality of the software over the software company offer being offered.

COMPREHENSIVE IT PROJECT 6
References
Aga, D. A., Noorderhaven, N., & Vallejo, B. (2016). Transformational leadership and project
success: The mediating role of team-building. International Journal of Project
Management, 34(5), 806-818.
Eskerod, P., Huemann, M., & Ringhofer, C. (2015). Stakeholder Inclusiveness: Enriching Project
Management with General Stakeholder Theory1. Project Management Journal, 46(6),
42-53.
Eskerod, P., Huemann, M., & Savage, G. (2015). Project stakeholder management—Past and
present. Project Management Journal, 46(6), 6-14.
Joslin, R., & Müller, R. (2016). The relationship between project governance and project
success. International Journal of Project Management, 34(4), 613-626.
Kerzner, H. (2017). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Kristiansen, J. N., & Ritala, P. (2018). Measuring radical innovation project success: typical
metrics don’t work. Journal of Business Strategy, 39(4), 34-41.
Ljungblom, M., & Lennerfors, T. T. (2018). Virtues and Vices in Project Management Ethics:
An Empirical Investigation of Project Managers and Project Management
Students. Project Management Journal, 49(3), 5-16.
Paz, F., & Pow-Sang, J. A. (2016). A systematic mapping review of usability evaluation methods
for software development process. International Journal of Software Engineering and Its
Applications, 10(1), 165-178.

COMPREHENSIVE IT PROJECT 7
Serra, C. E. M., & Kunc, M. (2015). Benefits realization management and its influence on
project success and on the execution of business strategies. International Journal of
Project Management, 33(1), 53-66.
Todorović, M. L., Petrović, D. Č., Mihić, M. M., Obradović, V. L., & Bushuyev, S. D. (2015).
Project success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), 772-783.