Scribd
Upload
416 views8 pages

Pharmacy System Project Plan

This document provides a project plan for a pharmacy system with the following key points: 1) The plan outlines phases for software requirements, development, testing, and training. 2) The scope will cover inventory, dispensing, cash collection, administration, and integration with other systems. 3) A project timeline of 10 months is estimated, and roles including sponsors, mentors, managers, developers and implementors are defined.

Uploaded by

kkumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
416 views8 pages

Pharmacy System Project Plan

This document provides a project plan for a pharmacy system with the following key points: 1) The plan outlines phases for software requirements, development, testing, and training. 2) The scope will cover inventory, dispensing, cash collection, administration, and integration with other systems. 3) A project timeline of 10 months is estimated, and roles including sponsors, mentors, managers, developers and implementors are defined.

Uploaded by

kkumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

PHARMACY PROJECT PLAN

Project plan

Pharmacy system

Technology project

Author: Bore Nelson

Creation Date: 17/01/2012

Last Revised: 17/01/2012

Version: 1.0
INTRODUCTION

Purpose of Plan

Pharmacy Project Plan will provide project’s goals and objectives. Additionally, the Plan
will serve as an agreement between the following parties: Stakeholders, Project
Manager, Project Team, and other personnel associated with and/or affected by the
project.
Background Information/Available Alternatives

Refer to page 1 of AMPATH Pharmacy project vision scope document.


Project Approach
Pharmacy System will be rolled out in this manner.

Phase I: Software requirements documentation


Phase II: Software development
Phase III: Test Software
Phase IV: Conduct Training
Tools

• Wiki- General documentation

• Jira -work in progress

• Asana- Scope summaries to the management

GOALS AND OBJECTIVES

Refer to page 1 of AMPATH Pharmacy project vision scope document.


SCOPE AND EXECUTION

Scope

Pharmacy system will cover the following areas

• Inventory

• Dispensing

• Cash collector

• Administrative functions

• Reports

• Integration with other systems(Mobile)

• Use of bar code and bar code readers

Execution

Phase 1. Requirements (Done)

Phase 2 .Development plan(Due to start)

For details refer to Asana.

Phase 3. Implementation
Project team
The following are stakeholders in this project .

Project owners/Sponsors

Ampath pharmacy

Mentors
Paul

Burke

Win

Jeremy

Management

Ampath management

Implementors

System administrators.

Infrastructure

Infrastructure team

Developers

Ampath programming team

Project schedule
The project Schedule will be posted in Asana and updated as tasks are completed.

Any changes to the schedule shall be reviewed through a technical call presentation,
documented and approved.

Refer to Asana for Project Tasks with Estimated Completion Dates.


PROJECT MANAGEMENT APPROACH

Project Timeline

Tentatively 10 months as approximated in Asana

Project Roles and Responsibilities

Role Responsibilities Participant(s)


Project Sponsor  Provide project oversight and
Ampath pharmacy
guidance
 Evaluate requirement related
project user requirements
Mentors Burke
 Give advisory on the project Paul
 Review project deliverables Jeremy
Win

Project Manager  Manages project in Nelson


accordance to the project plan
 Serves as liaison to the Steer
the project
 Provide overall project
direction
 Direct/lead team members
toward project goals
Project  Execute the project Development team
Implementors System administrators
Infrastructure
Issue Management
The decision by which to make modifications to the Project Plan (including project
scope and resources) should be coordinated using the following process:

Step 1: As soon as a change which impacts project scope, schedule, staffing or


spending is identified, the Project Manager will document the issue.

Step 2: The Project Manager will review the change and determine the
associated impact to the project and will forward the issue, along with a
recommendation, to the weekly technical call for review and decision.

Step 3: Upon receipt, the stakeholders should reach a consensus opinion on


whether to approve, reject or modify the request based upon the
information contained in the wiki. The decisions should be made in a
timely manner so as not to affect the time line.

Step 4: Following an approval or denial (by the stakeholders or Project Sponsor),


the Project Manager will notify the original requester of the action taken.
There is no appeal process.

Step 5: The project manager will notify the relevant stakeholders to include the
change.
Communications Plan

This plan provides a framework for informing, involving, and obtaining buy-in from all
participants throughout the duration of the project.

Audience This communication plan is for the following audiences:

− Project Sponsor
− Mentors
− Management
− Project Manager
− Developers
− Infrastructure
− Implementors

Communications Outreach The following is a list of communication events that are


established for this project:

Weekly Status Reports Relevant stakeholders will provide their status reports
in their weekly technical call. The reports shall include the following information
tracked against the Project Plan:

- Work in progress.
- Summary of issue status and resolutions
APPROVALS

Sign-off Sheet

The approval of this proposal will be done by stakeholders in the format below

Project Sponsor:

Date
Project Manager:

Date
Mentors:

Date
Developers:

Date
Implementors:

Date
Infrastructure:

You might also like