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: Determine the factors that must be considered and observed throughout the work breakdown structure (WBS) development process, and explain why. 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. 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. Recommend the estimation technique that should be used for each activity (that is, PERT, Delphi, analogy, expert judgment, or rule of thumb). Determine the major milestones that the project will encounter. Describe the logical sequence of planned activities required to achieve the project and analyze how monitoring durations on the critical path influence the success of the project.

100% Rule Adherence: The 100% rule dictates that the WBS must include 100% of the work defined by the project scope and capture all deliverables – internal, external, and interim – in terms of the work to be completed, including project management. It also states that a WBS level should not include any work that falls outside the actual scope of the project. Observing this rule prevents scope creep and ensures that all necessary work is accounted for.
Mutually Exclusive and Collectively Exhaustive (MECE): At each level of the WBS, the elements should be mutually exclusive, meaning there should be no overlap between the work defined in different branches. They should also be collectively exhaustive, ensuring that all the work required for the parent deliverable is included in its child elements. Observing MECE helps to avoid confusion, duplication of effort, and ensures that all aspects of the deliverable are addressed.
Level of Detail Appropriateness: The level of detail in the WBS should be sufficient to allow for effective planning, scheduling, budgeting, and monitoring of the project. However, it should not be so granular that it becomes overly complex and difficult to manage. The appropriate level of detail often depends on the size and complexity of the project, the experience of the team, and the control requirements. Observing this balance ensures that the WBS is a useful management tool without becoming an administrative burden.
Stakeholder Involvement: Engaging key stakeholders, including the project team members who will be performing the work, is crucial for creating an accurate and comprehensive WBS. Their input provides valuable insights into the tasks involved, potential challenges, and the logical flow of work. Observing active stakeholder participation fosters buy-in and ensures that the WBS reflects a realistic understanding of the project.
Alignment with Project Scope Statement: The WBS must directly align with and reflect the scope defined in the project scope statement. The scope statement outlines the project objectives, deliverables, exclusions, and assumptions. Observing this alignment ensures that the WBS addresses all aspects of the agreed-upon scope and does not include any work outside of it.

2. Work Breakdown Structure (Indented Format)

1.0 Streamline Delivery Operations
    1.1 iOS Mobile Application Development
        1.1.1 Search Customer Screen Module
            1.1.1.1 Requirements Gathering & Analysis (iOS)
            1.1.1.2 Design (UI/UX) - Search Customer
            1.1.1.3 Development - Search Customer
            1.1.1.4 Unit Testing - Search Customer
            1.1.1.5 Integration Testing - Search Customer
        1.1.2 Search Address Screen Module
            1.1.2.1 Requirements Gathering & Analysis (iOS)
            1.1.2.2 Design (UI/UX) - Search Address
            1.1.2.3 Development - Search Address
            1.1.2.4 Unit Testing - Search Address
            1.1.2.5 Integration Testing - Search Address
        1.1.3 Confirm Delivery Screen Module
            1.1.3.1 Requirements Gathering & Analysis (iOS)
            1.1.3.2 Design (UI/UX) - Confirm Delivery
            1.1.3.3 Development - Confirm Delivery
            1.1.3.4 Unit Testing - Confirm Delivery
            1.1.3.5 Integration Testing - Confirm Delivery
        1.1.4 Mobile Application Integration & Testing
            1.1.4.1 System Integration Testing (All Modules)
            1.1.4.2 User Acceptance Testing (UAT)
            1.1.4.3 Bug Fixing & Retesting
            1.1.4.4 Mobile Application Release Preparation
    1.2 Cloud-Based Infrastructure Development
        1.2.1 Network and Application Infrastructure Upgrade
            1.2.1.1 Requirements Gathering & Analysis (Cloud Infrastructure)
            1.2.1.2 Cloud Platform Selection & Setup
            1.2.1.3 Network Appliance Procurement & Configuration
            1.2.1.4 Network Infrastructure Upgrade & Integration
            1.2.1.5 Application Infrastructure Setup & Configuration
            1.2.1.6 Security Configuration & Testing
        1.2.2 GPS Tracking Integration (Cloud)
            1.2.2.1 GPS Data Interface Development
            1.2.2.2 Data Storage & Management Setup
            1.2.2.3 API Development for Mobile Client
            1.2.2.4 Integration Testing (GPS & Cloud)
    1.3 Training
        1.3.1 Operation Support Staff Training
            1.3.1.1 Training Material Development (Support Staff)
            1.3.1.2 Training Session Delivery (Region 1 & 2)
            1.3.1.3 Training Session Delivery (Region 3 & 4)
            1.3.1.4 Post-Training Support & Documentation
        1.3.2 Cargo Airplane Pilot Training
            1.3.2.1 Training Material Development (Pilots)
            1.3.2.2 Training Session Delivery (Region 1)
            1.3.2.3 Training Session Delivery (Region 2)
            1.3.2.4 Training Session Delivery (Region 3)
            1.3.2.5 Training Session Delivery (Region 4)
            1.3.2.6 Post-Training Support & Documentation
    1.4 Project Management
        1.4.1 Project Planning & Initiation
        1.4.2 Project Monitoring & Controlling
        1.4.3 Risk Management
        1.4.4 Communication Management
        1.4.5 Stakeholder Management
        1.4.6 Project Closure

Section 1: Written Project Plan

Project Title: Streamlining Delivery Operations with iOS Application and Cloud-Based Solution

Project Goal: To develop and deploy an iOS mobile application and a supporting cloud-based infrastructure with GPS tracking capabilities to streamline the organization's delivery operations for air cargo shipments across the United States. This includes developing three key iOS application modules, upgrading the internal network and application infrastructure to a secure cloud-based model, and providing comprehensive training to operational support staff and cargo airplane pilots.

1. Factors for Consideration and Observation in WBS Development

The Work Breakdown Structure (WBS) is a crucial hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. Throughout the WBS development process, several critical factors must be considered and observed to ensure its effectiveness and accuracy:

Deliverable-Oriented Focus: The WBS must be organized around the key deliverables of the project, not just the tasks. Each level should represent a tangible output or result that contributes to the overall project goal. This ensures that the scope is clearly defined and that progress can be objectively measured against these deliverables. Observing this focus prevents the WBS from becoming a simple task list that lacks a clear connection to the project's objectives.

Planning a Software Development Project

Section 1: Written Project Plan

Aced Essays

Free Resources

Recent Posts

Let us help

Contact Us