PMIS Test Plan, BCP, Stakeholder Communication, and Project Closure

This report presents a comprehensive PMIS test plan, outlining testing processes, types (system and usability), schedule, and assumptions. It also details a Business Continuity Plan (BCP) with objectives to mitigate risks and ensure business continuity, including phases like Business Impact Analysis and Recovery. The report emphasizes stakeholder communication, project task tracking via Gantt charts, and risk & change management. It provides recommendations on effective PMIS usage, including project closure procedures, evaluation, and future PMIS implementation considerations. The document covers various aspects of project management, from initial planning to final evaluation, offering insights into system testing, risk management, and stakeholder engagement to enhance project success and organizational efficiency. The plan also covers the importance of tracking project tasks, risk and change management, and project closure, providing a holistic view of the project's lifecycle.

PMIS
Part 3

Test Plan - Objectives
 To illustrate the testing processes that
shall be conducted on the PMIS
 To make sure that the testing scope and
strategy is clear among all the project
resources
 To define the acceptance criteria for the
testing processes

Test Plan – Testing Types
 System testing
 Usability Testing
 The user interface attributes, content, and the overall look &
feel of the PMIS will be determined for the general usability.
 The goal will be to ensure that the navigation of the PMIS is
smooth and the users succeed in accessing all of the functions
 Functional Testing
 The primary objective of the testing type will be to make sure
that all of the components are designed as per the functional
aspects.
 The testing process shall compare the functionalities
implemented in the PMIS with the business specifications and
rules.

Test Plan – Schedule &
Assumptions
 Test Schedule
 The overall duration for the testing process will be 65 days.
 It will run in parallel with the development process.
 The resolution dates on the defects may change as per the
response provided by the development team.
 The number of open defects at the end of the testing
process shall be nil.
 Assumptions
 The testing tools required by the testing resources will be
available to the team before the initiation of the process.
 The test reports will be shared with the stakeholders during
the testing phase

BCP - Objectives
 To make sure that the risks associated with the
PMIS are identified and prevented to maintain
business continuity
 To minimize the impact of any interruption
 To determine the points of failure and work on
the same for continued execution
 To have a recovery plan in place in the case of
occurrence of a disaster
 To streamline the PMIS business operations for
achieving market and competitive advantage

Phases of BCP
 Project Management and Initiation
 Business Impact Analysis
 Recovery Phase
 BCP Development Phase
 Final Phase

Recommendations on how to
effectively use PMIS in the
organization

Recommendations on how to
effectively use PMIS in the
organization
 Stakeholders
 It is necessary that enhanced level of communication is maintained among the
stakeholders so as to achieve project success.
 The Project Manager must ensure that the project information shared with the internal
and external stakeholder is relevant.
 Not all the stakeholders are interested in detailed documents.
 There shall be use of statistics done to support the reports so that the quick look may
provide the project updates.
 There shall be summary section included to highlight the key points.
 Project communication plan and reporting
 The communication guidelines shall be shared with all the resources.
 The Project Manager shall make sure that the reports on the schedule and budget
estimations and tracking are prepared and regularly shared.
 There may be numerous changes that may come up in the PMIS functionalities.
 The change reports shall be prepared and shared with the stakeholders to manage
the PMIS scope and processes.

Recommendations on how to
effectively use PMIS in the
organization
 Tracking Project Tasks
 Gantt chart provides the ability to keep a track of the project activities and determine
the schedule of each of these activities.
 Risk & Change Management
 It will be necessary to identify the risks and take preventive and controlling actions
accordingly.
 The tasks list shall be updated regularly so that the risks around schedule and
resources are identified.
 A custom list must be prepared followed by the customization of the three-state
workflow. The testing of the workflow shall be carried out thereafter.
 Project Closure
 The phase shall include the determination and comparison between the activities
planned and the ones that are carried out.
 The identification of the gaps between the estimated and actual values will provide a
brief on the project performance.
 The evaluation of the project will be effectively done and the usage of the PMIS by the
project stakeholders will be determined as well.
 The information on the usage of the similar PMIS in the future will also be obtained.