Seminar 4

14. Project Team Structure, Roles, and Responsibilities

 Project Team Structure:
 Project Manager
 Design Team
 Development Team
 Testing Team

 Roles and Responsibilities:

 Project Manager
 Overseeing the project to ensure it meets its goals on time and within budget.
 Coordinating between different teams and stakeholders.
 Risk management and mitigation.
 Design Team
 Creating a user-friendly interface.
 Ensuring the design aligns with the clinic’s brand identity.

 Development Team
 Developing the website’s frontend and backend.
 Ensuring the website is functional and meets specified requirements.
 Testing Team
 Conducting functional and security testing.
 Identifying bugs and working with the development team to resolve them.

15. Change Management Process and Analysis

The activity of the fourth week is code homepage
 Change Management Process
 Identification of Change: Recognize the need for change, either from internal feedback
or external factors.
 Formal Request for Change: Submit a detailed change request form that outlines the
nature of the change, its impact, and the reason for the change.
 Review and Approval: A change control board or project manager reviews the change
request. They assess the impact, feasibility, and implications of the change.
 Planning and Implementation: If approved, the change is planned and executed. This
might involve adjusting schedules, reallocating resources, or revising budgets.
 Verification: After implementation, the change is reviewed to ensure it was executed
correctly and is having the desired effect.
 Documentation: All changes and their impacts are documented for future reference.

 Change Request
 Activity Name: Code Homepage
 Originator:
 Date:
  Description of change: This activity and its duration increased by 50%
 Current Duration: [5 days]
 Proposed Duration: [7.5 days]
 Reason for Change: Additional features requested by the client for the homepage.
 Impact of Change:
Potential delay in subsequent activities.
Possible need for additional resources or budget adjustments.
Approval:
Date approved:
Reviewed By:
Decision: Approved/Rejected
Comments: [Any additional notes or feedback]

16. Stakeholder Engagement Assessment Matrix

Current Target Barriers to
Stakeholder Strategy
Position Position Change

Allocate
Project additional
Supportive Engaged Limited resources
Manager resources if
needed

Provide
Development Lack of training
Neutral Engaged necessary
Team on new tools
training sessions

Schedule
Lack of regular
Clients Unaware Supportive regular update
communication
meetings

Conduct user
Not involved in
End Users Unaware Supportive testing and
the process
gather feedback

Review and
Contractual renegotiate
Suppliers Neutral Cooperative
issues contracts if
necessary

Provide regular
Senior Concerns about budget updates
Supportive Engaged
Management budget and
justifications

17. Stakeholder Communication Plan

 Messag
Communicat Method of
Stakeholde e Frequen Responsib
ion Communicati
r Conten cy le Person
Objective on
t

Progres
Project Project s, Email, Team
Weekly
Manager updates issues, Meetings Leads
changes

Tasks, Email, Project

Developme Task Project
deadlin Management Daily
nt Team assignments Manager
es Software

Progres
Project s, Esmail, Bi- Project
Clients
updates approva Meetings weekly Manager
ls

Website
Feedback Surveys, Focus As UX
End Users usabilit
collection Groups needed Designer
y

Deliver
Procureme
ables, Email, Phone As
Suppliers Coordination nt
deadlin Calls needed
Manager
es

Progres
Senior
Project s, Email, Formal Project
Managemen Monthly
updates budget Reports Manager
t
status

18. In Excel.
19. In Excel.

20. Project Risks

Ris
Likelihoo
k Risk Description Impact Mitigation Strategy
d
ID

Project delays due to Regular progress

R1 High High
unforeseen issues monitoring

R2 Budget overruns Medium High Strict budget

Ris
Likelihoo
k Risk Description Impact Mitigation Strategy
d
ID

monitoring

Lack of stakeholder Regular stakeholder

R3 Low High
engagement communication

Mediu Having a skilled

R4 Technical difficulties Medium
m technical team

Security Rigorous security

R5 Low High
vulnerabilities testing

Mediu Clear project scope

R6 Scope creep Medium
m definition

Mediu Proper resource

R7 Lack of resources Low
m planning