Assignment 3 VoIP Part 1 Work Breakdown Structure Due Week 5

Assignment 3 Voip Part 1 Work Breakdown Structuredue Week 5 And Wor

This assignment contains two (2) deliverables: a summary document to be delivered in a word processor document format and a Work Breakdown Structure (WBS) to be delivered in a project file.

As the project manager for an IT department, you have been assigned to manage the project of deploying a new VoIP phone system to the company’s campus. The campus consists of three (3) different buildings, each with twenty to fifty (20 to 50) workstations. The project must be completed in ninety (90) calendar days starting on November 1.

Deliverable 1: Summary (MS Word or open source equivalent)

  1. Write a one to two (1-2) page summary document in which you:
    • Summarize the project requirements and other assumptions (e.g., budget, human resources, workload, environmental dependencies, etc.).
    • Define a work breakdown structure and describe the methodology behind constructing one.

Deliverable 2: WBS (MS Project or open source equivalent)

  1. Use Microsoft Project to create a WBS which:
    • Contains at least five (5) main tasks, one for each of the PMBOK® process areas.
    • Contains at least sixty (60) line items distributed in ten (10) or more work packages.
    • Contains Work Breakdown Structure Code for each task.
    • Presents a duration estimate for each task which results in a duration estimate for the project not to exceed the requirements described in the overview.

Formatting requirements for the summary document: Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Include a cover page with the assignment title, student name, professor’s name, course title, and date. The cover page and the reference page are not included in the page length requirement.

This assignment aims to demonstrate how project management enhances the success of IT projects and to explore the relationship between project scope and work breakdown structures. Use technology and information resources to research issues in IT project management, and write clearly and concisely, following proper writing mechanics and technical style conventions.

Paper For Above instruction

Introduction

Effective project management serves as a cornerstone for the successful deployment of technological solutions within organizations. In the context of deploying a Voice over Internet Protocol (VoIP) system across a university campus, meticulous planning, comprehensive work breakdown structures (WBS), and strategic resource allocation become critically important. This paper offers a detailed overview of the project requirements, assumptions, and methodology behind constructing a WBS, emphasizing the importance of structured project management in achieving timely and within-budget delivery of technological infrastructure expansions.

Project Overview and Requirements

The project involves deploying a VoIP phone system across a campus consisting of three distinct buildings, each occupied with 20 to 50 workstations, totaling approximately 90 to 150 workstations. The primary goal is to facilitate seamless, reliable, and cost-effective communication capabilities for the university's administrative and academic staff. The project duration is strictly set to 90 days, starting from November 1, with the requirement that all installations, configurations, testing, and staff training be completed within this timeframe.

Key requirements of the project include:

  • Procurement and installation of VoIP hardware and telephony infrastructure in each building.
  • Configuration of network settings and integration with existing IT infrastructure.
  • Training for staff on new communication systems.
  • Testing and troubleshooting of the system to ensure reliability and quality assurance.

Assumptions made for the project include sufficient budget allocation, availability of skilled technical personnel, and minimal environmental dependencies that could delay hardware delivery or installation. It is also assumed that existing network cabling and power supplies are adequate or can be upgraded without significant delays or additional costs.

Methodology of Constructing a Work Breakdown Structure

The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to accomplish project objectives and create deliverables. It serves as a foundation for planning, scheduling, resource allocation, and risk management.

The methodology for constructing a WBS involves:

  1. Defining the scope: Clarify project goals, deliverables, and boundaries.
  2. Identifying major tasks or phases: These tasks align with PMBOK® process groups—initiating, planning, executing, monitoring and controlling, and closing.
  3. Breaking down tasks into smaller work packages: Each work package contains specific, manageable activities with assigned resources and durations.
  4. Assigning codes: WBS codes facilitate tracking and reporting.
  5. Estimating durations and dependencies: Providing realistic timelines for each activity ensures the total project duration remains within 90 days.

Application of the WBS

The WBS for this project would include at least five main tasks, one per each of PMBOK® process areas:

  • Project Integration Management: Project initiation, stakeholder engagement.
  • Scope Management: Requirements gathering, scope definition.
  • Time Management: Scheduling, activity sequencing.
  • Cost Management: Budgeting, resource allocation.
  • Quality Management: Testing, quality assurance.

Each main task comprises multiple detailed activities or line items—aiming for at least 60—to address specific activities such as site assessment, hardware procurement, configuration, and training. Accurate duration estimates are essential to ensure the combined effort respects the 90-day deadline.

Conclusion

Delivering a VoIP system across a multi-building campus within a constrained timeframe underscores the importance of structured project management practices. A well-developed WBS not only delineates clear task responsibilities and dependencies but also facilitates effective resource management and schedule adherence. Ultimately, employing a disciplined approach rooted in the PMBOK® guidelines enhances the likelihood of project success, providing reliable communication infrastructure to support the university's operational needs.

References

  • Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). PMI.
  • Klastorin, T. D. (2003). Project management: Tools and trade-offs. Wiley.
  • Kerzner, H. (2017). Project management: A systems approach to planning, scheduling, and controlling (12th ed.). Wiley.
  • Heldman, K. (2018). Project management jumpstart (3rd ed.). Wiley.
  • Schwalbe, K. (2018). Information technology project management (9th ed.). Cengage Learning.
  • Larson, E. W., & Gray, C. F. (2017). Project management: The managerial process (7th ed.). McGraw-Hill Education.
  • Shenhar, A. J., & Dvir, D. (2007). Reinventing project management: The diamond approach. Harvard Business Review Press.
  • Zwikael, O., & Smyrk, J. (2011). Project planning and control: For construction and development. Gower Publishing.
  • Meredith, J. R., & Mantel, S. J. (2014). Project management: A managerial approach (8th ed.). Wiley.
  • PMI. (2021). Practice Standard for Work Breakdown Structures. Project Management Institute.

Related Assignments