Southern New Hampshire University IT 510 4-2 Final Project Milestone Two

Southern New Hampshire University
IT 510 4-2 Final Project Milestone Two: Project Plan
Spring-Summer 2018
Ivan Cruz Morales

IV. Project Plan: Illustrate your recommended implementation and management strategies. Be sure to include screenshots of all relevant diagrams, charts, and tables.

Best services for writing your paper according to Trustpilot

Premium Partner
From $18.00 per page
4,8 / 5
Writers Experience
Recommended Service
From $13.90 per page
4,6 / 5
Writers Experience
From $20.00 per page
4,5 / 5
Writers Experience
* All Partners were chosen among 50+ writing services by our Customer Satisfaction Team

Project Scope
Determining the scope of this project means defining the specific boundaries, or extent, of the project (Tilley & Rosenblatt, 2017). In the presented case study, UR’s Covered Inc. management team has come up with the idea of developing a mobile application to improve customer service in the area of claim management. Although, the current claims management system is well integrated, the management team has agreed that, the application screens are not fully accessible for users as they require computer access. As a result, the case managers have ended up receiving numerous customer’s follow up calls on claims instead of continue processing those claims through the existing web application.
The main causes of this problem are the required user’s computer access to access the claims management system and the communication quality between case managers and claimants. A cause and effect diagram, also known as fishbone diagram, is an effective tool for categorizing the potential causes of a problem (Fig. 1). Hence, the project scope is to develop a mobile application compatible with iOS mobile devices to provide customers a two-way communication option with their case managers that doesn’t require computer access. The focus of the new mobile application is to improve the end user experience through a more effective communication structure.
Figure 1: UR Covered Fishbone Diagram Example

a) Work Breakdown Structure:
According to the Project Management Body of Knowledge (PMBOK), a Work Breakdown Structure (WBS) (Fig. 2) is the hierarchical decomposition of the deliverables associated with the work of the project team. In other words, it involves breaking a project down into a series of smaller tasks. The WBS is considered as the foundation of project planning and is associated with higher productivity, increased accountability, transparency, and a better allocation of time and cost estimates for all of the specific work packages (Tripathi, 2016).

Figure 2: UR Covered Work Breakdown Structure Example (WBS)

Southern New Hampshire University (2018)
Describe all of the essential roles and functions required for implementing the solution.
A successful development project only move forward if the stakeholders are properly identified and documented. The current solution, involves the participation of many people at different levels within the organization. Through the Software Development Life Cycle (SDLC) Iterative Model, the stakeholders would be formally involved on the plan, design, development, test, and deployment of the mobile application (if approved). By using the iterative model, the mobile app development is faster and can properly address any chances of incorrect interpretation. Amongst the stakeholders of the mobile development project are the following five key roles and their corresponding responsibilities: System Analyst, Project Manager, Mobile Developer, Validation and Verification Team, and the Change Control Board.
Who will be doing the work and what, specifically, will they need to do?
System Analyst
The Systems Analyst plays a key role in de development of the mobile app. From the beginning to the end the Systems Analyst works as a liaison between all stakeholders and is involved in every phase of the SDLC cycle. In the beginning, the System Analyst would work with the stakeholders to figure out the vision and purpose of the app, map out the requirements, understand the overall scope of the project, and ultimately, to translate their requirements into something realistic. The Systems Analyst would be also involved with cost-benefit analysis, the collection of some data, and the evaluation of business processes to effectively determine the benefits of enterprise mobility within the organization. Another of the main contributions of the Systems Analyst is adhering to security and testing. The analyst would be involved in testing the application’s user experience, and make sure that the requirements are implemented throughout the testing process (Martin, 2014).
Project Manager
The Project Manager is responsible for accomplishing the individual objectives of the mobile app development. The Project’s Manager main responsibilities include creating clear and attainable objectives, tracking progress against objectives, and implementing corrective action when necessary to ensure that the project achieves its goals. The Project Manager would also effectively manage resources as and when needed to keep the project on track and within budget. The Project Manager and the Systems Analyst are the primaries responsible for the success of the mobile app project (U.S. Department of Veteran Affairs, 2014).
Mobile Developer
The main task of the Mobile Developer is to actually develop the mobile application prototype. This includes retrieve the software’s requirement checklist, creating the app’s layout and user interface, as well as, submitting pre-artifacts for review and testing. The Mobile Developer would also build instructional material for training and user’s future reference (U.S. Department of Veteran Affairs, 2014).
Validation and Verification Team
The Validation and Verification Team would ensure that the mobile app is free of defects and provide with consolidated reports to the Systems Analyst and other key stakeholders. (U.S. Department of Veterans Affairs, 2014).
Change Board Control
If changes are requested, these will be approved by the Change Board Control entity and notified to the Systems Analyst and other key stakeholders. All changes related to the development phase must be captured to ensure that testing in these other environments are documented before the deployment phase. This entity must also manage future updates to the final product (U.S. Department of Veterans Affairs, 2014).
b) Project Monitoring and Control Plan:
How are you going to ensure that the project is going smoothly?
Monitoring and Controlling processes are necessary to keep track of the project’s progress and performance, as well as, to identify and initiate possible changes. According to the Project Management Body of Knowledge (PMBOK), these controls are applied to a more than one of the project areas. These areas include: scope, time, cost, quality, risk, and communications among others (Hayes Munson, 2012).
What is your plan of attack to ensure that all controls are adhered to?
Keeping a project on track doesn’t come easy. However, project managers can effectively manage resources and risk by establishing clear Key Performance Indicators (KPI’s) (Fig. 3) and promoting a strong communication network with key stakeholders. For example, creating progress reports that include cost, schedule, and costs (Hayes Munson, 2012). Other useful reports could track changes on tasks, model defects, and other potential risks that may affect the timeline of the project. Similarly, a Stakeholder Register (Fig. 4) is an effective tool where the Project Manager can rely on to obtain and share knowledge to all stakeholders and other parties involved in the project (Usman, 2015). Another effective tool to manage changes is a Project Change Log (Fig. 5). A Project Change Log would provide the project manager with the description of change requests, the resources involved, and the type impact of such request. Ultimately, following such procedures would ensure deliverables correspond to the approved project requirements (Hayes Munson, 2012).
Figure 3: UR Covered Key Performance Indicators (KPI) Example

Southern New Hampshire University (2018)
Figure 4: Stakeholder Register Example

Snyder, C. (n.d)

Figure 5: Project Change Log Example

PM Tips (2011)
What is the defined critical path? Be sure that you frame your response for communicating effectively to your target audiences.
The critical path of the mobile app project would be defined by the Work Breakdown Structure (WES), the expected completion time of key tasks, task dependencies, as well as, the contribution of people and entities involved in the project. The mobile app development would encompass five main stages planning, designing, development, testing and deployment (if approved). Subdividing the project into small “packages” allows improving the effectiveness of communications in general, including frequency and quality (Abudi, 2013). The tasks, activities, people, and entities involved in each stage are shown below (Fig.4 & 5).
Elaborate more here.
Fig. 4 UR Covered Critical Path Tasks and Activities Diagram (Detailed grant Chart) Example

Fig. 5 UR Covered Critical Path Tasks, Activities, and Stakeholders Example

c) Timeline:
What is the estimated amount of time for implementation? Create a visual representation that captures your timeline (e.g., Gantt chart) based on the systems development life cycle.
The estimated time from planning to implementation is 669 days comprising 768 hours. The start through completion date would be 08/08/2014 to 12/02/2014. The UR Covered mobile app Project Plan and Timeline are shown below (Fig.6 & Fig. 7).
Fig. 6: UR Covered Mobile App Project Plan Example (Gantt chart).

Figure 7: UR Covered Mobile App Timeline Example

The work and cost resources of the UR mobile app are shown below (Fig. 8). For example, these include people, equipment, and other financial costs associated with completing any given specific tasks.
Fig. 8: UR Covered Resource Sheet Example

Abudi, G. (2013). Managing communications effectively and efficiently. Paper presented at PMI® Global Congress 2013—North America, New Orleans, LA. Newtown Square, PA: Project Management Institute. Date accessed May 22, 2018.
Hayes Munson, K. A. (2012). How do you know the status of your project?: Project monitoring and controlling. Paper presented at PMI® Global Congress 2012—North America, Vancouver, British Columbia, Canada. Newtown Square, PA: Project Management Institute. Date accessed: May 10, 2018, from
Marti, E. (2014, April 21) Why Business Analysts are Important for Mobile App Development. Catavolt, Inc., Retrieved May 10, 2018, from
Tripathi, B. (2016, Mar 18) Project Management Advantages of Work Breakdown Structure in Project Management. Retrieved May 9, 2018, from
Team Solve (2015, August 17) Five Key Roles and Responsibilities for Software Development Projects Success. Retrieved May 9, 2018, from
Usman, F. (2015) Stakeholder Register in Project Management. Retrieved May 11, 2018, from
U.S. Department of Veteran Affairs (2014, Aug 6) Mobile Applications Governance Board (MAGB): Roles and responsibilities. Retrieved May 9, 2018, from
BuildFire. (2018, January 29). Mobile App Development Timeline: A Realistic Perspective. Retrieved May 11, 2018, from
Southern New Hampshire University (2018) IT 510 Module Two Homework Project File. Date accessed: May 11, 2018.
PM Tips (2011, May 14). More on Change Management – The Change Log. Retrieved May 11, 2018, from
Snyder, C. (n.d) A Project Manager’s Book of Forms. Retrieved May 11, 2018, from

You Might Also Like

I'm Alejandro!

Would you like to get a custom essay? How about receiving a customized one?

Check it out