This document provides an overview of project management steps and templates for a smart adverse event processing management system project. The key steps and templates discussed include: 1. Project initiation, planning, baseline and execution, monitoring and control, reporting and communication, and closure. 2. A stakeholder analysis, requirements traceability matrix, work breakdown structure (WBS), responsibility assignment matrix (RAM), communication plan, and project charter template. 3. An overview of the smart adverse event processing management system which includes collecting adverse event messages from various sources, extracting information from the messages, storing the data in a database, hosting web pages to access the data, and providing a user experience to view and modify the data.

1. Project Management
Sample Exercise/Templates

2. Project Initiation
Project Planning
(Scope)
Project Planning
(Workflow)
Project Planning
(Resources)
Project Planning
(Finalization)
Project Baseline and
Execution
Project Monitoring and
Control
Project Reporting and
Communication
Project Closure
X470 Project Management - Steps

3. Smart Adverse Event Processing Management System
(SAEPMS)
Adverse Event Processing Engine
HTML
email
Text
email
SMS
adversevent@berkeley.edu
Extract following details from Email/SMS Message
 From / Sender
Attachments
Body / Contents
Timestamp / Date time when email was send
Database Cluster
Web Server
User Experience (UX)
Adverse Event
Messages
1
2 3 4
5

4. Smart Adverse Event Processing Management System
(SAEPMS)
1
2
3
4
5
User sends email or SMS text message to sample inbox i.e adversevent@berkeley.edu
Processing engine extracts meaningful information from the adverse event
messages and stores information in database.
Database stores all the information of adverse event and user details of the web
application.
Web Server host web pages so that admin users and other users can access the web
application.
User Experience is the web pages used by admin users and other users to
view/modify adverse event data.
PROJECT CHARTER

5. Stakeholder Analysis

6. Stakeholder Analysis

7. Requirements Traceability Matrix (RTM)

8. WBS

9. Sequencing Activities

10. Sequencing Activities

11. Sequencing Activities

12. Sequencing Activities

13. Sequencing Activities

14. Responsibility Assignment Matrix (RAM) in RACI format

15. Communication Plan

16. Project Charter Template
Submitted by: [Name] Page 1 of 2
PROJECT CHARTER
1. General Project Information
Project Name:
Executive Sponsors:
Department Sponsor:
Impact of project:
2. Project Team
Name Department Telephone E-mail
Project Manager:
Team Members:
3. Stakeholders (e.g., those with a significant interest in or who will be significantly affected by this project)
4. Project Scope Statement
Project Purpose / Business JustificationDescribe the business need this project addresses
Objectives (in business terms)Describe the measurable outcomes of the project, e.g., reduce cost by xxxx or increase quality to yyyy
DeliverablesList the high-level “products” to be created (e.g., improved xxxx process, employee manual on yyyy)

17. Project Charter Template
Submitted by: [Name] Page 2 of 2
Scope List what the project will and will not address (e.g., this project addresses units that report into the Office of Executive Vice
President. Units that report into the Provosts Office are not included)
Project MilestonesProposestart and end dates for Project Phases (e.g., Inception, Planning, Construction, Delivery) and other major
milestones
Major Known Risks (including significant Assumptions)Identify obstacles that may cause the project to fail.
Risk Risk Rating (Hi, Med, Lo)
ConstraintsList any conditions that may limit the project team’s options with respect to resources, personnel, or schedule (e.g.,
predetermined budget or project end date, limit on number of staff that may be assigned to the project).
External DependenciesWill project success depend on coordination of efforts between the project team and one or more other
individuals or groups? Has everyone involved agreed to this interaction?
5. Communication Strategy (specify how the project manager will communicate to the Executive Sponsor, Project Team members
and Stakeholders, e.g., frequency of status reports, frequencyof Project Team meetings,etc.
6. Sign-off
Name Signature Date
(MM/DD/YYYY)
Executive Sponsor
Department Sponsor
Project Manager
7. Notes

18. Requirements Traceability Matrix: Functional and Technical
Project Name:
ID
Requirement
Name
Short Description
Priority
(L,M,H)
Date
Registered
Requirement
Source
Owner
Validation
Method
Notes
000
(Example)
Exterior Surface Color
Product to be painted semi-glass weatherproof one-coat CMYK: Cyan 0%,
Magenta: 69%, Yellow: 100%, Black: 6%.
M 10/29/2014
Executive Steering
Committee.
Mary Jones,
Chairperson
James Smith,
Environmental
Protection Specialist
ColorSnap mobile
app, then
compliance with
ASTM E2808 - 11
International Orange, corresponds
to Pantone 180 (CYMK 19.4%,
77.9%, 79.6% 3.6%)
0001
0002
0003
0004
0005
0006
0007
0008
0009
0010

19. Thank You
hkbhadraa@gmail.com