PROJECT MANAGEMENT

PROJECT MANAGEMENT (PM)

PROJECT MANAGEMENT WORKSHOP

Course Length: 3 Days
Class Hours: 8 hours/day

GOAL

The goal of this workshop is to teach students how to be an effective Business Analyst and how to develop different types of requirements (Customer requirements, System Requirements, etc.) that are required in different phases of Software Development Life Cycle (SDLC). Students will also learn how to ensure the product quality by developing quality requirements and managing requirements growth or changes efficiently.

During this workshop, a standard set of tools, templates and techniques will be offered to all students so that they can start writing requirements as soon as they get back to work. Moreover, free on-line help will be available for all students who need to communicate to the instructor for some clarification or help to start writing the real requirements. This free on-line support will be available for 30 days after students complete this workshop successfully. If necessary, on-site consultation can be arranged based on the project type and the group size.

OBJECTIVES

Upon completing the 3 days hands-on workshop, students will learn:

  • What is Project Management?
  • How to be an effective Project Manager (i.e., roles/responsibilities).
  • What are the different types of activities/actions are required in different phases of Software Development Life Cycle (SDLC)?
  • How to plan, design, implement, execute, monitor and control any IT project from start to finish.
  • How to estimate each work products for budget and resource planning.
  • How to plan for unknowns (i.e., risks list) and how to handle them (i.e., mitigation plan & disaster recovery strategy).
  • How to build quality product by setting quality goals upfront.
  • How to manage resources effectively without compromising the software quality.
  • How to negotiate with customers, vendors, suppliers and other stakeholders effectively.

OVERVIEW

INTRODUCTION

  • Define Project Management
  • Present Software Development Process (SDP) overview
  • Introduce Software Development Life Cycle (SDLC).
  • Identify different project management activities that are required in different phases of SDLC
  • Define Project Manager’s roles and responsibilities in entire SDLC
  • Project Management and SEI’s CMMI model
  • Describe importance of SQA in Project Management process
  • Introduce Software Quality Review process in accordance with SQA
  • Mention importance of Configuration Management (CM) process in PM
  • Describe needs for Process Asset Library (PAL)
  • Introduce different PM methods and practices are used in the industry
  • Discuss major PM tools and technologies are available in the industry

Project Initiation Phase

Understanding project scope, objectives, deliverables and customer’s expectations from the Project Charter document.

  • Making sure that project is formally defined
  • Customer has agreed to fund the project
  • Project duration, start and end dates have been agreed by all stakeholders
  • Project resources are allocated
  • Project management procedures are identified and approved

Project Planning Phase

  • Develop project schedule based on Work Breakdown Structure (WBS)
  • Perform size and effort estimates
  • Develop training plan including cost, schedule, duration, etc.
  • Develop communication plan
  • Identify risk list and mitigation plan
  • Plan for resources including people, travel, training, hardware, software, lab, etc.
  • Develop Configuration Management plan
  • Develop quality plan, set quality metrics and quality audit schedules
  • Baseline project plan

Project Implementation Phase

  • Launch project according to the plan
  • Acquire resources as promised
  • Acquire requirements
  • Monitor project activities according to the plan Communicate with customers, team members and all stakeholders as planned
  • Update the plan for fine-tuning (if necessary)

Project Monitoring & Control Phase

  • Monitor project progress according to the plan
  • Manage changes in resources, cost and quality
  • Manage risks and utilize mitigation plan if necessary
  • Control overall project and manage changes without impacting budget, quality and schedule (ideal case)

Project Closing Phase

  • Deliver product to the client
  • Manage post-delivery activities
  • Conduct lesson learned session