Select Page

Categories

Duties of the Project Manager During the Implementing Phase

Duties of the Project Manager During the Implementing Phase
By John Filicetti

  • Ensure Client notifies end-users of all deployment dates.
  • Creates Project Status Report on a regular basis, distributes the report to stakeholders, and posts the report to the project workspace.
  • PM assigns tasks to resources and gathers information from the team when updates are made. PM approves all work and reviews/manages project schedule updates. (Note: It is a good idea to go over weekly tasks with team on Monday and have review of week with team on Friday.)
  • PM meets with other PMs and Resource Managers to review resource allocation and utilization.

  • PM chairs all Status Meetings:
    • PM fills out Meeting Report for all meetings and distributes to team as agenda prior to meeting along with current RAIDCBT and Project Schedule.
    • PM updates Meeting Report with minutes during meeting and distributes to Client PM and project team.
    • Discuss week’s goals.
Read the Complete Article

Project Management Process – Phase 3 – Implementing – Information Distribution

Project Management Process – Phase 3 – Implementing – Information Distribution (#18 in the Hut Project Management Process)
By John Filicetti

Description

Information distribution involves making needed information available to project stakeholders in a timely manner and requires the project manager and team members to perform the following five tasks:

  • Review and implement the communications management plan
  • Conduct project meetings as needed to keep people informed
  • Communicate all relevant project information informally and formally as needed through the project manager, the project focal point
  • Identify and communicate barriers to project execution
  • Attempt to respond to special requests for information from key stakeholders

Project team members are responsible for communicating effectively with one another as the project requires and forwarding all relevant project information to the project manager for disposition and broader distribution. Team meetings, e-mail, networked databases, enterprise document management systems, project management software, and the organization’s intranet can all be used to facilitate easy, effective, and timely distribution and recording of project information. Read the Complete Article

Project Management Process – Phase 3 – Implementing – Project Management Plan Execution (Build)

Project Management Process – Phase 3 – Implementing – Project Management Plan Execution (Build) (#16 in the Hut Project Management Process)
By John Filicetti

Description

During this step, the Project Team, under the direction of the Project Manager, will perform the project tasks as outlined in the Project Schedule, the Project Management Plan, and the project designs to fulfill the project objectives. Prior to the start of this step, hold a meeting with your project team to ensure everyone understands the current project environment along with roles and responsibilities. Review all the accepted project documentation to date. During this step, the Project Manager must coordinate and direct the various technical and organizational interfaces that exist in the project. The project product is actually created during this step.

If this is an application development project, the project team will follow the cycle outlined in the graphic to the left. In order to keep the development flowing smoothly, the developers will be building while the Quality Assurance (QA) team is testing. Read the Complete Article

Project Management Process – Phase 3 – Implementing Overview

Project Management Process – Phase 3 – Implementing Overview (#15 in the Hut Project Management Process)
By John Filicetti

The next phase is the Implementing Phase. The focus of the Implementing Phase is to:

  • Complete the solution according to the project design and plan following the project schedule and managing change
  • Monitor and review the project’s progress against the plan; identifying when the project is off track and taking corrective actions as required
  • Gain project acceptance
  • Transition the customer to the new solution

Inputs

  • Project Charter
  • Concept Business Case
  • Actual Business Case
  • Industry Best Practices
  • Finalized Project Requirements
  • Project Plan which includes:
    • Project Scope
    • Project Assumptions and Constraints
    • Staffing Plan
    • Cost Plan
      • Communication Plan
      • Risk Assessment and Mitigation Plan
      • Quality Plan
      • Procurement Plan
  • Project Schedule
  • Risk Assessment and Issues/Action Item Matrix
  • Meeting Reports

Outputs

  • Issues/Action Item Matrix
  • Change Control Documents
  • Timesheets
  • Status Reports
  • Meeting Reports

Next in the Hut Project Management Process:

Project Management Process – Phase 3 – Implementing – Project Management Plan Execution (Build)

Previously in the Hut Project Management Process:

Project Management Process – Phase 2 – Planning – Equip Project (Optional)

John F. Read the Complete Article

Project Management Process – Phase 2 – Planning – Develop Project Design

Project Management Process – Phase 2 – Planning – Develop Project Design (#12 in the Hut Project Management Process)
By John Filicetti

Description

The Subject Matter Experts (SMEs) and Architect on the project team will complete the project design with information gathered during the requirements phase along with additional detailed information from the customer team and customer environment. The designs will progress from Conceptual, through Logical, to Physical for many project types.

The design will be reviewed and validated before a final project design is created. All versions of the design should be placed in the project repository for reference. All design meetings should be documented and the Meeting Reports placed in the project repository.

In some cases, equipment will be required for project execution. If you project calls for equipment, obtain the equipment and track the equipment via an inventory list.

Steps

  • Analyze the business activities, needs, and data associated with the proposed solution
  • Develop the solution in terms of the automated and manual procedures
  • Develop proposed formats for input and output
  • Prepare the design to ensure a seamless transition to the new solution
  • Create Conceptual Design
  • Validate design with client
  • Create Logical Design
  • Validate design with client
  • Create Physical Design
  • Validate design with client
  • Obtain signoff for all designs
  • Identify any Issues

Templates

  • None

Owner of This Step

  • Project Manager with Project Team

Next in the Hut Project Management Process:

Project Management Process – Phase 2 – Planning – Submit Documents for Approval

Previously in the Hut Project Management Process:

Project Management Process – Phase 2 – Planning – Develop Project Management Plan

John F. Read the Complete Article

Project Management – Product Description

Project Management – Product Description (#12 in the series Project Management Guide)
By Lasa Information Systems Team

While the Project Definition Document provides an overview of the project, it is necessary to go into more detail about the key deliverables – the things that the project will produce. A Product Description is used to do this, spelling out the purpose of the product, details of what it will consist of, and set quality criteria.

The “product” may be a tangible thing like a printed publication or a website, or it may be a less concrete entity such as a training course or some form of service.

The Product Description is a separate document from the Project Initiation Document.

The Product Description will go into more detail: for example, the Product Description for a publication will describe its content, the different sections, its format etc. The two documents have different purposes – the Product Description should be able to stand alone. Read the Complete Article

Project Management – Project Initiation Document

Project Management – Project Initiation Document (#11 in the series Project Management Guide)
By Lasa Information Systems Team

Summarise your project in one document which can be referred to when the details get confusing.

Project Initiation Document Headings

Background

  • Context
  • Origins
  • How we got where we are

Project Definition

  • Vision
  • Outcomes
  • Objectives
  • Deliverables
  • Method of approach
  • Scope
  • Constraints
  • Exclusions
  • Interfaces (how the project fits into overall organisation management – and relationships with partners)
  • Assumptions

Initial Business Case

  • Needs assessment
  • Benefits
  • Users (who)
  • Numbers
  • Marketing and access
  • Other players (voluntary and statutory)
  • Sustainability

Initial Project Plan

  • (Can use software like MS Project)
  • Assignments (tasks)
  • Timings
  • Estimated Effort (Staff time)

Budget Quality Plan

  • How products will be tested
  • (Monitoring, performance indicators)
  • Evaluation

Risks

Contingency Plan

Project organisation structure

  • (People, roles etc.)

Project Controls

  • (Running the project)

Exception Process

  • (Under what circumstances we make what changes when things go wrong – who decides.)

What the headings mean

Background

Background is a brief account of how the project got to where it is. Read the Complete Article

Recommended PM App

Recommended PM App

Categories