Planning a Software Development Project

Scenario
Imagine that you have been hired as a project manager assisting in the development of an iOS application and cloud-based solution that is designed to streamline your organization's delivery operation. As the project manager, you are to manage the development and release of the mobile client platform in the cloud-based infrastructure that will use GPS to track the shipment and delivery of goods in airplanes across the United States.
The iOS mobile client will have three modules consisting of a search customer screen, a search address screen, and confirm delivery screen. Programmers have reviewed the requirements and estimate that each module will take one programmer 300 hours to complete.
In addition to delivering the iOS mobile application, your project will require upgrading the internal network and application infrastructure to a cloud-based model to support the new iOS mobile platform. This effort will require your team to procure network appliances to optimize the security factors of the cloud-based platform.
One last component of the project scope is to provide training to operation support staff and 30 cargo airplane pilots staffed across four regions of the United States. Your project team consists of three programmers, a technical writer, three technical trainers, two network engineers, and one system administrator.

Instructions
Section 1: Written Project Plan
Write a 4–6-page paper in which you:

  1. Determine the factors that must be considered and observed throughout the work breakdown structure (WBS) development process and explain why.
  2. Create a work breakdown structure for the scope of the project. Note: The WBS must be in the indented format as shown in Figure 5-3 in Chapter 5 of the text. (See below)
  3. Analyze the various activities required for this project and provide an estimate of the duration for each activity based on the number of resources available for the project. Include assumptions and basis for each estimate.
  4. Recommend the estimation technique that should be used for each activity (that is, PERT, Delphi, analogy, expert judgment, or rule of thumb).
  5. Determine the major milestones that the project will encounter.
  6. Describe the logical sequence of planned activities required to achieve the project and analyze how monitoring durations on the critical path influences the success of the project.

Full Answer Section

 
  • Project risks: The WBS should identify and mitigate any potential risks to the project.
  • Project budget: The WBS should be developed within the constraints of the project budget.
By considering and observing these factors, the WBS can be developed in a way that is comprehensive, accurate, and realistic. Create a work breakdown structure for the scope of the project. The following is a work breakdown structure for the scope of the project:
  • Project Management:
    • Develop project plan
    • Manage project budget
    • Communicate with stakeholders
    • Track project progress
    • Mitigate risks
  • iOS Mobile Application Development:
    • Design user interface
    • Develop software modules
    • Test software modules
    • Deploy software modules
  • Cloud Infrastructure Development:
    • Design cloud infrastructure
    • Procure network appliances
    • Configure cloud infrastructure
  • Training:
    • Develop training materials
    • Deliver training to operation support staff
    • Deliver training to cargo airplane pilots
This WBS is just a starting point, and it may need to be further refined as the project progresses. However, it provides a good foundation for planning and managing the project. Additional Notes
  • The WBS should be updated as the project progresses to reflect changes in scope, budget, or schedule.
  • The WBS can be used to create a Gantt chart or other project schedule.
  • The WBS can be used to track project progress and identify potential risks.
  The WBS can be used to communicate with stakeholders about the project.

Sample Answer

  The following factors must be considered and observed throughout the work breakdown structure (WBS) development process:
  • Project scope: The WBS should be aligned with the project scope statement, which defines the work that is and is not included in the project.
  • Project deliverables: The WBS should identify all of the project deliverables, both tangible and intangible.
  • Project complexity: The WBS should be tailored to the complexity of the project. For more complex projects, the WBS may need to be more granular.
  • Project team expertise: The WBS should be developed in consultation with the project team to ensure that it is realistic and achievable.