Shiv Kumar Yadav CC7169NI May 9, 2025

Module Code & Module Title

CC7169NI Software Project Management

Assessment Weightage & Type

50% Individual Coursework

Year
AY 2025

Student Name: Shiv Kumar Yadav

London Met ID: 24059492
College ID: NP01MS7S250045
Assignment Due Date: May 9, 2025
Assignment Submission Date: May 9, 2025
Word Count: 7538

I confirm that I understand my coursework needs to be submitted online via My Second Teacher under the relevant
module page before the deadline for my assignment to be accepted and marked. I am fully aware that late
submissions will be treated as non-submission and a mark of zero will be awarded.
Shiv Kumar Yadav CC7169NI May 9, 2025

Page 1 of 72 - Cover Page

Software Project [Link]

Islington College,Nepal

Document Details

Submission ID trn:oid:::3618:95031070
65 Pages

Submission Date
7,538 Words
May 9, 2025, 11:06 AM GMT+5:45

48,501 Characters
Download Date

May 9, 2025, 11:08 AM GMT+5:45

File Name

Software Project [Link]

File Size
Shiv Kumar Yadav CC7169NI May 9, 2025

55.0 KB

Page 1 of 72 - Cover Page

Page 2 of 72 - Integrity Overview

13% Overall Similarity

The combined total of all matches, including overlapping sources, for each database.

0 Integrity Flags for Review

Our system's algorithms look deeply at a document for any inconsistencies that
would set it apart from a normal submission. If we notice something strange,
we flag it for you to review.

A Flag is not necessarily an indicator of a problem. However, we'd recommend

you focus your attention there for further review.
Shiv Kumar Yadav CC7169NI May 9, 2025

Page 2 of 72 - Integrity Overview

Page 3 of 72 - Integrity Overview

The sources with the highest number of matches within the submission. Overlapping sources will not be displayed.
Shiv Kumar Yadav CC7169NI May 9, 2025

Page 3 of 72 - Integrity Overview

Shiv Kumar Yadav CC7169NI May 9, 2025

Acknowledgement

I would like to express my sincere gratitude to everyone who contributed to the successful
completion of this report. My heartfelt thanks go to our module leader, Mr. Sanjish Wagle, whose
insightful advice and continuous encouragement were invaluable throughout this coursework.
Their unwavering support and expertise were instrumental in guiding me through the complexities
of Software Project Management.

I am also grateful for the enlightening lectures and tutorials provided by all faculty members
involved in this module. Their dedication to teaching and their commitment to student growth have
played a significant role in broadening my understanding of project management principles and
practices. Finally, I wish to thank my colleagues, friends, and family for their patience, motivation,
and moral support during this academic journey.
Shiv Kumar Yadav CC7169NI May 9, 2025

Abstract

The evaluation of project performance has traditionally relied on metrics such as cost, schedule,
and efficiency. However, recent academic and industry perspectives highlight the need to assess
project success through broader dimensions, including effectiveness, strategic alignment, and
stakeholder satisfaction. Software projects, in particular, are characterized by unpredictability and
complexity, often facing challenges like low-quality deliverables, budget overruns, and schedule
delays.

This report explores the domain of Software Project Management through a comprehensive case
study of the MedConnect project. It covers the formulation of a project management memorandum,
a comparative analysis of development methodologies, the construction of a RACI matrix, and the
development of a detailed project plan. The report also examines the integration of structured
(PRINCE2) and agile (Scrum) methods to address the multifaceted demands of modern software
projects.

By focusing on both quantitative performance measures and qualitative outcomes, this document
demonstrates how effective project management can drive organizational improvement, facilitate
stakeholder collaboration, and enable the successful delivery of innovative software solutions in a
rapidly evolving environment.
Shiv Kumar Yadav CC7169NI May 9, 2025

Table of Contents
1. Memorandum .......................................................................................................................... 1

2. Software Development Approach and Methods ..................................................................... 3

2.1. Traditional Software Development Approach – Waterfall Model ................................. 3

2.2. Agile Software Development Approach – Scrum Framework ....................................... 4

2.3. Comparison of Traditional Approach (Waterfall) and Scrum (Agile Approach) ........... 6

2.4. Selected Methodology: Scrum – Justifications ............................................................... 6

2.5. Rejected Methodology: Waterfall – Justification ........................................................... 9

3. RACI MATRIX .................................................................................................................... 11

3.1. Process Stages with PRINCE2 for RACI Matrix ......................................................... 12

3.2. RACI Matrix at Phase Level ......................................................................................... 14

3.3. RACI Matrix at Activity Level ..................................................................................... 15

4. Development Plan ................................................................................................................. 16

4.1. Team Structure .............................................................................................................. 16

4.2. User Stories Planning (Prioritizations and Estimations) ............................................... 18

4.2.1. Must Have (M) – Essential for MVP and Compliance ......................................... 18

4.2.2. Should Have (S) – Valuable Enhancements ......................................................... 18

4.2.3. Could Have (C) – Optional or Nice to Have......................................................... 18

4.2.4. Won’t Have (W) – Deferred for Future ................................................................ 19

4.2.5. Assumptions made for software development project plan .................................. 19

4.3. Product Backlog ............................................................................................................ 19

4.3.1. Features Provided by MedConnect (HealthSync Solutions lnc.).......................... 19

4.4. Sprint Planning.............................................................................................................. 20

4.4.1. Sprint 0:................................................................................................................. 20

4.4.2. Sprint 1 .................................................................................................................. 21

Shiv Kumar Yadav CC7169NI May 9, 2025

4.4.3. Sprint 2 .................................................................................................................. 21

4.4.4. Sprint 3: Testing, Quality Assurance, and Deployment ....................................... 22

4.5. Cost Breakdown for MedConnect Project .................................................................... 23

5. Project Brief .......................................................................................................................... 26

5.1. Document Information .................................................................................................. 26

5.1.1. Project Brief History ............................................................................................. 26

5.1.2. Project Distribution ............................................................................................... 27

5.2. Project Definition .......................................................................................................... 27

5.2.1. Background ........................................................................................................... 27

5.2.2. Project Objectives ................................................................................................. 27

5.2.3. Desired Outcomes ................................................................................................. 27

5.2.4. Project Scope and Exclusions ............................................................................... 28

5.2.5. Constraints and Assumptions................................................................................ 28

5.2.6. Project Tolerance .................................................................................................. 28

5.2.7. The users and Other Interested Parties.................................................................. 29

5.2.8. Interfaces ............................................................................................................... 29

5.3. Outline Business case ................................................................................................... 29

5.3.1. Reasons ................................................................................................................. 29

5.3.2. Expected Benefits ................................................................................................. 29

5.3.3. Time ...................................................................................................................... 29

5.3.4. Cost ....................................................................................................................... 29

5.3.5. Major Risks and Mitigation .................................................................................. 30

5.4. Project Product Description .......................................................................................... 31

5.4.1. Title ....................................................................................................................... 31

5.4.2. Purpose.................................................................................................................. 31
Shiv Kumar Yadav CC7169NI May 9, 2025

5.4.3. Composition .......................................................................................................... 31

5.4.4. Development Skills Required ............................................................................... 31

5.4.5. Customer’s Quality Expectations ......................................................................... 31

5.4.6. Acceptance Criteria, Methods, and Responsibilities ............................................ 31

5.5. Project Approach .......................................................................................................... 32

5.6. Project Management Team Structure............................................................................ 32

5.7. Roles Description .......................................................................................................... 32

6. Lifecycle Integration – PRINCE2 and Scrum for MedConnect ........................................... 33

6.1. PRINCE2 Overview...................................................................................................... 33

6.2. SCRUM Overview ........................................................................................................ 37

6.3. Comparative Analysis of PRINCE2 and SCRUM........................................................ 41

6.3.1. In terms of phases ................................................................................................. 42

6.3.2. In terms of Roles ................................................................................................... 43

6.3.3. In terms of Deliverables ........................................................................................ 44

6.4. Conclusion .................................................................................................................... 45

References ..................................................................................................................................... 46
Shiv Kumar Yadav CC7169NI May 9, 2025

Table of Tables

Table 1 Comparative table: Waterfall vs Scrum ............................................................................. 6

Table 2 Justification of chosen methodology (1) ............................................................................ 6
Table 3 Justification of chosen methodology (2) ............................................................................ 7
Table 4 Justification of chosen methodology (3) ............................................................................ 7
Table 5 Justification of chosen methodology (4) ............................................................................ 7
Table 6 Justification of chosen methodology (5) ............................................................................ 8
Table 7 Justification of chosen methodology (6) ............................................................................ 8
Table 8 Justification of chosen methodology (7) ............................................................................ 8
Table 9 Justification of rejected methodology (1) .......................................................................... 9
Table 10 Justification of rejected methodology (2) ........................................................................ 9
Table 11 Justification of rejected methodology (3) ........................................................................ 9
Table 12 Justification of rejected methodology (4) ...................................................................... 10
Table 13 RACI Matrix (Phase Level) ........................................................................................... 14
Table 14 RACI Matrix (Activity Level) ....................................................................................... 15
Table 15 Roles and Responsibilities ............................................................................................. 17
Table 16 User Stories (Must Have) .............................................................................................. 18
Table 17 User Stories (Should Have) ........................................................................................... 18
Table 18 User Story (Could Have) ............................................................................................... 18
Table 19 User Story (Won't Have) ............................................................................................... 19
Table 20 Average Cost analysis .................................................................................................... 23
Table 21 Estimated total cost ....................................................................................................... 24
Table 22 Budget Range ................................................................................................................. 24
Table 23 Document information ................................................................................................... 26
Table 24 project brief history ....................................................................................................... 26
Table 25 Project distribution list ................................................................................................... 27
Table 26 Risk and its mitigation ................................................................................................... 31
Table 27 Perceived Limitations (PRINCE2) ................................................................................ 37
Table 28 Perceived Limitations (SCRUM)................................................................................... 40
Table 29 Comparative Analysis (PRINCE2 and SCRUM) .......................................................... 41
Shiv Kumar Yadav CC7169NI May 9, 2025

Table 30 Comparative Analysis (In terms of Phase) .................................................................... 42

Table 31 Comparative Analysis (In terms of role) ....................................................................... 43
Table 32 Comparative Analysis (In terms of Deliverables) ......................................................... 44

Table of Figures

Figure 1 Waterfall model - Traditional Approach (Mohideen & Mohideen, 2022) ....................... 3
Figure 2 Agile Development Cycle (Robinson, et al., 2024).......................................................... 4
Figure 3 Organizational Team Structure....................................................................................... 16
Figure 4 PRINCE2 and Scrum (Puscasu, 2025) ........................................................................... 33
Figure 5 PRINCE2 Process (INFINITY, 2025) ............................................................................ 34
Shiv Kumar Yadav CC7169NI May 9, 2025

1. Memorandum
To: John Cena, Director of Project Management, HealthSync Solutions Inc.

From: Shiv Kumar Yadav, Project Manager

Date: 26 April 2025

Subject: Official Commencement of MedConnect Project

Greetings Sir/Madam,

This memorandum serves to formally initiate the MedConnect project under the direction of
HealthSync Solutions Inc. Following strategic discussions between Mr. Michael Thompson
(CEO), Ms. Priya Sharma (Product Owner), and other key stakeholders, it has been agreed that the
SCRUM methodology, under the Agile approach, will be adopted for this project. This decision is
based on the suitability of SCRUM for dynamic, cross-functional, and compliance-driven
healthcare software development.

As per the project requirements, a diverse and skilled team has been assembled, comprising a
Product Owner, Scrum Master, developers (front-end and back-end), UI/UX designer, QA
engineer, Compliance Officer, and Clinical Advisor. The team structure and individual
responsibilities are detailed in the "Project Plan" section of this document.

Given the distributed nature of our team across the USA and Nepal, we have tailored some
SCRUM roles for remote collaboration. For MedConnect, the Scrum Master will also act as the
team manager, ensuring the facilitation of all SCRUM events and the removal of impediments.
During the testing phase, the Project Manager will actively participate in quality assurance to
ensure the highest standards are met.

The development process will be organized into four sprints, each lasting approximately two
weeks. The project is scheduled to commence on 1 May 2025, with a targeted delivery and
deployment by 25 June 2025, in line with agreed-upon requirements and milestones. The estimated
budget for MedConnect is $95,850, covering technology, human resources, compliance, and
operational expenses. A detailed breakdown of costs is provided in the budget section of this
report.

1
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Recognizing that effective communication is vital for project success, we will rigorously follow
all SCRUM ceremonies, including daily stand-ups, sprint planning, reviews, and retrospectives.
As Project Manager, I will maintain bi-weekly meetings with executive management to present
progress, demonstrate deliverables, and gather feedback. Additional communication and
collaboration will be facilitated through tools such as Slack, Jira, and Zoom to ensure seamless
coordination across time zones.

The MedConnect project aims to deliver a secure, scalable, and user-centric healthcare
management platform that meets the highest standards of clinical, technical, and regulatory
excellence. I look forward to your continued support and guidance as we embark on this critical
initiative.

2
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

2. Software Development Approach and Methods

A software development approach refers to a systematic and organized method for developing
software, providing a framework for planning, organizing, implementing, and testing. The choice
of methodology significantly impacts project outcomes, influencing quality, adaptability, and
stakeholder satisfaction. For MedConnect, an AI-driven healthcare platform, careful consideration
of methodologies is essential due to the complexity and regulatory nature of healthcare software.

2.1. Traditional Software Development Approach – Waterfall Model

The traditional approach, often exemplified by the Waterfall model, is characterized by a linear
sequence of phases: requirements, design, implementation, testing, deployment, and maintenance.
Each phase must be completed before the next beginning, and changes are difficult to
accommodate once a phase is finalized (KPI PARTNERS, 2025).

Figure 1 Waterfall model - Traditional Approach (Mohideen & Mohideen, 2022)

3
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Key Features:

• Linear process flow: Clear, sequential stages.

• Emphasis on documentation: Detailed records at every phase.
• Predictability: Well-suited for projects with stable requirements.

Applicability to MedConnect:

While the Waterfall model ensures thorough documentation and control, its rigidity poses
challenges for projects like MedConnect where requirements may evolve due to regulatory updates
or user feedback. This approach can lead to higher costs and delays if changes are needed after
initial phases.

2.2. Agile Software Development Approach – Scrum Framework

Scrum is an Agile framework that emphasizes iterative development, customer collaboration, and
adaptability. Unlike the rigid Waterfall model, Scrum fosters a collaborative environment through
defined roles (Product Owner, Scrum Master, Development Team), time-boxed sprints, continuous
feedback, and evolving deliverables. Agile values individuals and interactions, working software,
customer collaboration, and responsiveness to change (Robinson, et al., 2024).

Figure 2 Agile Development Cycle (Robinson, et al., 2024)

4
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Core Values:

• Individuals and interactions over processes and tools

• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Benefits:

• Flexibility: Easily accommodates evolving requirements.

• Stakeholder engagement: Continuous feedback and collaboration.
• Incremental delivery: Regular releases ensure early value realization.

Scrum is a widely adopted Agile framework designed for complex projects requiring frequent
adaptation and stakeholder engagement. Work is organized into sprints—short, fixed-length
periods (typically 2–4 weeks)—during which teams deliver potentially shippable increments of
the product.

Key Scrum Elements:

• Roles: Product Owner (prioritizes features), Scrum Master (facilitates process),

Development Team (cross-functional implementers).
• Events: Sprint Planning, Daily Standups, Sprint Review, Sprint Retrospective.
• Artefacts: Product Backlog, Sprint Backlog, Increment.

Scrum’s time-boxed sprints, regular feedback cycles, and clear accountability make it well-suited
for MedConnect, where requirements may evolve, and rapid iteration is essential for integrating
user and regulatory feedback.

Relevance to MedConnect:

Given the dynamic healthcare environment and the need for iterative AI development, Agile
methodologies offer the adaptability and stakeholder involvement necessary for MedConnect’s
success.

5
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

2.3. Comparison of Traditional Approach (Waterfall) and Scrum (Agile Approach)

Criteria Waterfall Model Scrum (Agile Framework)
Process Structure Linear and Sequential Iterative and Incremental
Requirements Fully defined upfront Evolve continuously during
sprints
Testing Post-development Continuous and during each
sprint
Change Management Difficult to accommodate Highly adaptive to changes
changes
Stakeholder Involvement Minimal after design phase Continuous throughout
project
Time-to-Market Delivery at end Frequent releases with each
sprint
Best suited for Static, low-risk projects Dynamic, evolving, user-
centric projects
Table 1 Comparative table: Waterfall vs Scrum

2.4. Selected Methodology: Scrum – Justifications

For the MedConnect platform development, Scrum is selected as primary methodology due to
several factors:

Justification 1

The MedConnect platform will feature AI-driven diagnostics, which require constant
Scenario refinement based on test results and patient feedback during development.

Attribute Iterative delivery

Scrum allows each feature—like a diagnostic module—to be developed, tested,

deployed, and improved over multiple sprints, enabling early delivery of a usable
Reasoning system and incremental enhancements based on real-world use.

Table 2 Justification of chosen methodology (1)

6
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Justification 2

The project team is distributed between Kathmandu (development) and Boston

Scenario (client-side clinical validation and AI input).

Attribute Collaboration & Communication

Scrum’s regular rituals—daily standups, sprint reviews, and retrospectives—ensure

clear communication and shared understanding across geographically dispersed
Reasoning teams, mitigating the risk of misalignment.

Table 3 Justification of chosen methodology (2)

Justification 3

Feedback from doctors, patients, and administrators will shape the evolution of
Scenario features like telemedicine integration, user interfaces, and automated alerts.

Attribute Continuous Stakeholder Engagement

By involving stakeholders at the end of each sprint, Scrum ensures their feedback is
incorporated early and frequently, reducing the risk of misaligned functionality or
Reasoning unusable designs.

Table 4 Justification of chosen methodology (3)

Justification 4

Health regulations (e.g., HIPAA, GDPR) can evolve during the development cycle,
Scenario requiring changes in data handling, storage, and user permissions.

Attribute Flexible Planning

Scrum’s flexible backlog and sprint planning allow the team to reprioritize work and
Reasoning accommodate regulatory updates without derailing the entire development lifecycle.

Table 5 Justification of chosen methodology (4)

7
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Justification 5

In Waterfall, discovering usability flaws or AI model errors late in the development

Scenario phase could lead to costly rewrites or project failure.

Attribute Time-boxed Execution with Early Validation

Scrum’s short sprints and iterative review cycles help identify issues earlier, enabling
Reasoning course correction and better time, cost, and quality control.

Table 6 Justification of chosen methodology (5)

Justification 6

The platform includes integration of third-party APIs and experimental AI

Scenario components, such as early diagnostic suggesters.

Attribute Support for Prototyping & MVP Development

Scrum allows quick prototyping of individual modules and validates their feasibility
through sprint reviews, which is crucial when dealing with innovative but uncertain
Reasoning components.

Table 7 Justification of chosen methodology (6)

Justification 7

HealthSync Solutions expects an early release of core functionalities like appointment

Scenario scheduling and patient management to beat market competitors.

Attribute Rapid Time-to-Market

Scrum enables delivery of minimum viable features early and adds enhancements
Reasoning progressively, giving the client a competitive edge while maintaining quality.

Table 8 Justification of chosen methodology (7)

8
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

2.5. Rejected Methodology: Waterfall – Justification

The reason for not choosing the waterfall model is mentioned below:

Justification 1

Government regulations for digital health platforms may change mid-development,

Scenario
requiring MedConnect to revise its data encryption and access control features.

Attribute Fixed Scope and Linear Progression

Waterfall’s rigid structure means changes introduced after the requirement phase can
Reasoning lead to extensive rework and delayed delivery, making it unsuitable for projects with
dynamic compliance factors.

Table 9 Justification of rejected methodology (1)

Justification 2

AI models integrated into the diagnostics module require iterative training and tuning
Scenario
based on patient data and validation metrics, which evolve during development.

Attribute Late Validation of Deliverables

Waterfall does not accommodate iterative experimentation; it pushes testing to the

Reasoning
end, potentially allowing undetected flaws to accumulate.

Table 10 Justification of rejected methodology (2)

Justification 3

HealthSync executives, clinicians, and patients all have ongoing feedback that needs
Scenario
to be incorporated in the evolving platform.

Attribute One-time Client Interaction

Waterfall only includes stakeholders during initial planning and final review, making
Reasoning
it impractical for projects that demand ongoing stakeholder engagement.

Table 11 Justification of rejected methodology (3)

9
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Justification 4

Modules like telemedicine and EHR (Electronic Health Record) integration need
Scenario
continuous testing, especially across different devices and compliance environments.

Attribute Sequential Development with Delayed QA

Waterfall schedules testing only after full implementation, creating high risk if early
Reasoning stages fail to meet quality or security expectations—especially for safety-critical
systems like healthcare platforms.

Table 12 Justification of rejected methodology (4)

10
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

3. RACI MATRIX
A RACI matrix is a practical tool used in project management to clarify and communicate the roles
and responsibilities of team members for each major task or deliverable within a project. The
acronym RACI stands for Responsible, Accountable, Consulted, and Informed. By mapping these
roles against project activities, the matrix helps prevent confusion, avoids task duplication, and
ensures that all necessary stakeholders are engaged at the right moments throughout the project
lifecycle (Matthews, 2024).

For the MedConnect platform, which involves cross-functional teams in both the USA and Nepal,
a well-structured RACI matrix is vital for aligning expectations and maintaining clear
communication across time zones and disciplines.

RACI Role Definitions

• Responsible (R):

The person(s) who actually complete the task. For MedConnect, this could include
software developers, business analysts, or QA engineers directly working on deliverables.

• Accountable (A):

The individual is ultimately answerable for the correct and thorough completion of the task.
There must be exactly one Accountable person per task, such as the Product Owner or
Project Manager, who signs off on work and ensures it meets standards.

• Consulted (C):

Subject matter experts or stakeholders who provide input and feedback. For example,
compliance officers or clinical advisors might be consulted on regulatory features.

• Informed (I):

Those who need to be kept up to date on progress but are not directly involved in execution
or decision-making. This could include senior management or external partners (Prokopets,
2020).

A clear RACI matrix prevents decision bottlenecks and ensures that each team member
understands their role, especially in a distributed, multidisciplinary healthcare project.
11
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

3.1. Process Stages with PRINCE2 for RACI Matrix

The PRINCE2 methodology divides project management into seven distinct process stages, each
with specific objectives, deliverables, and defined roles. For a complex healthcare platform like
MedConnect, this structure is crucial for maintaining control, ensuring compliance, and facilitating
clear communication across geographically distributed teams. Integrating the RACI matrix at each
PRINCE2 stage clarifies who is Responsible, Accountable, Consulted, and Informed, minimizing
ambiguity and supporting efficient project execution (ILX Group, 2025).

Overview of PRINCE2 Process Stages

1. Starting Up a Project (SU)

This initial phase ensures the project’s foundation is solid before significant resources are
committed. Key activities include developing a project mandate, outlining the business
justification, and assembling a preliminary project team. The project manager drafts an initial brief
while the project board reviews and approves the project’s strategic direction (Buehring, 2024).

2. Directing a Project (DP)

Throughout the project lifecycle, the project board provides oversight, strategic guidance, and key
approvals. They authorize project initiation, review progress at stage boundaries, and make
decisions on major changes or exceptions. The board is ultimately accountable for the project’s
alignment with business goals and value delivery (Buehring, 2024).

3. Initiating a Project (IP)

During this stage, the project manager develops a comprehensive project initiation document
(PID), detailing scope, quality, risk, cost, and time management plans. This stage establishes the
management baseline and confirms resource commitments. Input from senior users, suppliers, and
stakeholders is essential to ensure the project’s objectives are realistic and agreed upon (Buehring,
2024).

4. Controlling a Stage (CS)

The project manager takes charge of day-to-day management, assigning tasks, monitoring
progress, and addressing issues as they arise. Work packages are authorized for the team, progress

12
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

is tracked against the plan, and regular updates are provided to the project board. Any deviations
or risks are managed proactively at this stage (Buehring, 2024).

5. Managing Product Delivery (MP)

This process governs the relationship between the project manager and the delivery team. The
team accepts, executes, and completes work packages, ensuring deliverables meet agreed-upon
quality criteria. The project manager verifies completion and readiness for review, maintaining
clear accountability for outputs (Buehring, 2024).

6. Managing a Stage Boundary (SB)

At the end of each stage, the project manager and board review performance, update the business
case, and decide whether to proceed. This “decision gate” approach allows for iterative assessment
of risks, resource allocation, and alignment with strategic objectives. Plans for the next stage are
developed and approved at this point (Buehring, 2024).

7. Closing a Project (CP)

The final stage ensures all project objectives have been met, deliverables are accepted, and
documentation is complete. Lessons learned are captured, and the project is formally closed with
sign-off from the project board. This ensures a controlled and accountable handover to operations
or the client (Buehring, 2024).

Application to RACI Matrix

Each PRINCE2 stage involves specific roles and responsibilities that can be mapped using the
RACI model:

• Responsible: Individuals or teams executing tasks (e.g., project manager, development

team).
• Accountable: The person ultimately answerable for the stage outcome (e.g., project board,
executive).
• Consulted: Subject matter experts or stakeholders providing input (e.g., compliance
officer, clinical advisor).
• Informed: Those kept updated on progress (e.g., senior management, end users).

13
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

By aligning the RACI matrix with PRINCE2 stages, MedConnect’s project team ensures that every
phase—from initial planning to final delivery—has clearly defined ownership and communication
pathways. This minimizes confusion, supports regulatory compliance, and enables proactive risk
management, which is essential in healthcare software projects.

3.2. RACI Matrix at Phase Level

Below is a sample RACI matrix for MedConnect at the phase level, mapping key roles to project
management stages:

Dev
PRINCE2 Stage | Project Project Product Team Compliance Stakeholders
Role Board (A) Manager (R) Owner (C) (R) Lead (C) (I)

Starting Up a
Project A R C I C I

Directing a
Project A R I I C I

Initiating a Project C A R C C I

Controlling a
Stage I A C R I I

Managing
Product Delivery I C A R C I

Managing Stage
Boundary A R C I C C

Closing a
Project A R C I I I

Table 13 RACI Matrix (Phase Level)

Legend: A = Accountable, R = Responsible, C = Consulted, I = Informed

14
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

3.3. RACI Matrix at Activity Level

To provide further clarity, the RACI matrix can be broken down into specific activities within each
phase. Below is an example for key MedConnect deliverables:

Activity / Project Product Scrum Dev Compliance Clinical QA Stakeh

Deliverable Manager Owner Master Team Lead Advisor Engineer olders

Requirement
R A C C C C I I
s Gathering

System
Architecture A C I R C I I I
Design

Sprint
I R A C I I I I
Planning

Feature
A C C R I I I I
Development

Compliance
R C I I A C I I
Review

User
Acceptance C C I R I C A I
Testing

Deployment C A R R I I C I

Project
Closure &A C I I I I C R
Handover

Table 14 RACI Matrix (Activity Level)

15
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Importance for MedConnect

For MedConnect, a multinational, AI-driven healthcare platform, the integration of PRINCE2

process stages with a tailored RACI matrix ensures:

• Clear governance and accountability at every phase

• Efficient cross-border collaboration (USA and Nepal offices)
• Regulatory compliance through explicit consultation and informed roles
• Minimized risk of miscommunication or task duplication

This approach provides a robust foundation for successful delivery, stakeholder satisfaction, and
continuous improvement throughout the project lifecycle.

4. Development Plan
A comprehensive development plan is essential for ensuring the systematic delivery of the
MedConnect platform. Adopting the Scrum framework, the plan is structured into sprints, with
clear prioritization of features and tasks using the MoSCoW method (ProductPlan, 2024). This
approach allows for flexibility, iterative feedback, and the effective alignment of resources and
timeframes with stakeholder expectations and compliance requirements.

4.1. Team Structure

Figure 3 Organizational Team Structure

16
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

The MedConnect project is executed by a distributed, cross-functional team with members based
in both the USA and Nepal. The team structure is designed to promote collaboration, leverage
diverse expertise, and ensure regulatory compliance in healthcare technology.

Role Number Responsibilities

Project Manager 1 Overall coordination, reporting, resource management
Product Owner 1 Maintains product backlog, liaises with stakeholders
Scrum Master 1 Facilitates Scrum process, removes impediments
Regulatory 1 Advises on compliance (HIPAA/GDPR)
Compliance
CEO / Country 1 Strategic oversight, milestone approvals
Head
Clinical Advisor 1 or 2 Provides medical expertise, validates clinical workflows
Developers 5 Implement features, conducts code reviews
QA Engineer 1 Designs and executes test cases, ensures product quality
UI/UX Designer 1 Crafts user interfaces, ensures usability and accessibility
Table 15 Roles and Responsibilities

Key Points:

• Communication between departments is routed through respective leads.

• The Product Owner maintains the product backlog and acts as the primary liaison with
stakeholders.
• The Scrum Master ensures that Scrum ceremonies are followed and that the team remains
focused on sprint goals.
• Developers are cross-functional but may have specialized skills (front-end, back-end,
integration).
• Regular coordination meetings and digital collaboration tools (e.g., Jira, Slack, Zoom) are
used to bridge time zones and maintain alignment.

17
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

4.2. User Stories Planning (Prioritizations and Estimations)

User stories have been developed based on stakeholder interviews and healthcare workflow
analysis. Using the MoSCoW method (Must Have, Should Have, Could Have, Won’t Have),
stories are categorized according to criticality, regulatory requirements, and end-user value.

4.2.1. Must Have (M) – Essential for MVP and Compliance

ID User Story Points
M01 As a patient, I must be able to securely book appointments with clinicians. 5
M02 As a clinician, I must access and update patient records during consultations. 5
M03 As a user, the system must encrypt all personal health information. 8
M04 As an admin, I must manage user roles and permissions. 3
M05 As a user, the system must log all access and modifications for auditing. 4
M06 As a patient, I must be able to join telemedicine sessions. 5
Table 16 User Stories (Must Have)

4.2.2. Should Have (S) – Valuable Enhancements

ID User Story Points
S01 As a patient, I should receive appointment reminders via SMS/email. 2
S02 As a clinician, I should generate summary reports for patients. 3
S03 As a system, I should provide multilingual support (English, Nepali, etc.). 5
Table 17 User Stories (Should Have)

4.2.3. Could Have (C) – Optional or Nice to Have

ID User Story Points
C01 As a user, I could customize dashboard widgets. 2
C02 As an admin, I could view system analytics on usage and performance. 3
Table 18 User Story (Could Have)

18
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

4.2.4. Won’t Have (W) – Deferred for Future

ID User Story Points
W01 As a user, I won’t have direct integration with wearable devices in MVP.
Table 19 User Story (Won't Have)

4.2.5. Assumptions made for software development project plan

• The project duration is set at two months, with four sprints of two weeks each.
• Team velocity is estimated at 35 story points per sprint, based on prior experience.
• All regulatory requirements will be clarified before sprint 2.
• Stakeholder feedback will be incorporated at the end of each sprint.
• Saturdays and Sundays are non-working days.
• The budget allows for minor scope adjustments without formal approval.

4.3. Product Backlog

The product backlog is a living, prioritized list of all features, enhancements, and fixes required
for MedConnect. Managed by the Product Owner, it evolves throughout the project as new needs
emerge.

Sample Backlog Items:

• Secure authentication and access control

• Appointment scheduling module
• Electronic health record (EHR) integration
• Automated compliance reporting
• Patient messaging and notification system
• AI-powered symptom checker

Each item is assigned a relative effort estimate (e.g., story points) to aid in sprint planning.

4.3.1. Features Provided by MedConnect (HealthSync Solutions lnc.)

MedConnect is designed to offer a seamless healthcare management experience for both providers
and patients. Key features include:

• Secure patient data storage and retrieval

• Integrated appointment and calendar management

19
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

• Real-time messaging between patients and clinicians

• Compliance dashboards for regulatory reporting
• AI-driven symptom analysis and triage
• Multi-language support for global accessibility

4.4. Sprint Planning

In Scrum, sprints are a core element, often regarded as the framework's central component.
Typically lasting a month or shorter, sprints enable the Scrum team to deliver work incrementally
while gathering feedback. Each sprint begins with sprint planning, where essential tasks like
refining the sprint backlog and applying past insights are addressed (Agile Alliance, 2025).

Once a sprint begins, no changes can be made to the requirements until the sprint concludes and
its goal is achieved. After each sprint ends, the cycle restarts with fresh sprint planning. Key Scrum
events—such as daily stand-ups, sprint reviews, sprint retrospectives, and sprint planning—take
place during and after the sprint to ensure a smooth and continuous workflow.

This approach ensures consistent progress, adaptability, and continuous improvement throughout
the project lifecycle.

4.4.1. Sprint 0:
Duration: 2 Week

Start Date: 01/05/2025

End Date: 14/05/2025

Sprint Goal/Focus: Foundation and Backlog setup

User Stories (ID & Summary): Initial backlog creation, Environment setup Team onboarding

Key Activities: Backlog ready, tools configured, team aligned

20
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

4.4.2. Sprint 1
Duration: 2 Week

Start Date: 15/05/2025

End Date: 28/05/2025

Sprint Goal/Focus: Core MVP Features

User Stories (ID & Summary):

• M01: Patient books appointments (5)

• M02: Clinician manages records (5)
• M03: Encryption of health info (8)

Story Points: 18

Key Activities: Features designed, developed, tested, and reviewed

4.4.3. Sprint 2
Duration: 2 Week

Start Date: 29/05/2025

End Date: 11/05/2025

Sprint Goal/Focus: Feature Enhancements & Compliance

User Stories (ID & Summary):

• M04: Admin manages roles (3)

• M05: Audit logs (4)
• M06: Telemedicine sessions (5)
• S01: Appointment reminders (2)

Story Points: 14

Key Activities: Features designed, developed, tested, and reviewed

21
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

4.4.4. Sprint 3: Testing, Quality Assurance, and Deployment

Duration: 2 Week

Start Date: 12/06/2025

End Date: 25/06/2025

Sprint Goal/Focus: Finalization & Deployment

User Stories (ID & Summary):

• S02: Clinician summary reports (3)

• S03: Multilingual support (5)

• C01: Dashboard customization (2)

• C02: System analytics (3)

Story Points: 13

Key Activities: UAT, bug fixes, deployment, documentation, project closure

Legend:

• User Stories (ID & Summary): The prioritized stories planned for each sprint, with their
story points in parentheses.
• Key Activities & Deliverables: Each sprint includes requirements refinement, design,
development, testing, review, and retrospective.

22
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

4.5. Cost Breakdown for MedConnect Project

A comprehensive budget is critical to ensure the successful delivery of MedConnect within the
allocated resources and timeline. The budget covers human resources, technology, compliance,
and operational costs, distributed across all sprints. The following breakdown is based on estimated
story points, team velocity, and current market rates for a distributed team (USA and Nepal).

i. Total story points in product backlog

• Number of user stories: 20
• Average story points per story: 8
• total story points: 20 * 8 = 160 story points
ii. Estimated iteration based on team velocity
• Average team velocity: 40 story points per sprint
• Estimated sprints required: 160/40 = 4 sprints
iii. Average human resources and technical charges per sprint

Duration Per Day Human Per Sprint Human Technical Total Charges per
Sprint (days) Resource Charge Resource Charges Charges Sprint

0 7 $1,250 $8,750 $1,400 $10,150

1 10 $1,250 $12,500 $2,000 $14,500

2 18 $1,250 $22,500 $3,600 $26,100

3 18 $1,250 $22,500 $3,600 $26,100

Total $76,850

Table 20 Average Cost analysis

Note:

• Human resource charges include salaries for developers, QA, UI/UX, compliance, and
management.
• Technical charges cover infrastructure, cloud hosting, licenses, and tools.

23
Shiv Kumar Yadav CC7169NI May 9, 2025
 Shiv Kumar Yadav CC7169NI May 9, 2025

iv. Other Technical and operational Costs

• Infrastructure and cloud services: $8,000
• Licenses and Third-Party tools: $3,000
• Compliances and Legal: $6,000
• Miscellaneous: $2000
v. Estimated total cost

Category Cost (USD)

Total Human Resource Charges $66,250

Technical Charges (Sprints) $10,600

Other Technical/Operational $19,000

Total $95,850

Table 21 Estimated total cost

vi. Budget Range and Contingency

Scenario Calculation Total Budget (USD)

Actual Budget (100%) $95,850 * 1.00 $95,850

Best Price (80%) $95,850 * 0.80 $76,680

High End (120%) $95,850 * 1.20 $115,020

Table 22 Budget Range

Note:

• The budget excludes domain registration and ongoing hosting after project delivery.
• A 20% contingency is included for unforeseen requirements or risks.

Summary

The proposed budget ensures adequate funding for all critical activities, from initial planning and
development to compliance and deployment. Regular reviews will be conducted at the end of each

24
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

sprint to monitor expenditure and make necessary adjustments, ensuring the project remains within
scope and budget.

Rationale for Cost Allocation:

• Development Team: Assumes three to five full-stack engineers working for the duration
of the project, reflecting market rates for professional development in Nepal/regionally,
covering back-end, front-end, and integrations.
• QA Engineer: Involved from Sprint 1 for ongoing test automation, manual validation, and
regression testing.
• Scrum Master: Manages sprint ceremonies, agile tracking, and team support; costed as a
part-time engagement.
• Product Owner: Embedded domain expert, responsible for backlog prioritization,
requirement refinement, and sprint acceptance.
• Regulatory Consultant: Specialized compliance expert needed during initial compliance
mapping and final security review before go-live.
• UI/UX Design: Dedicated resource for key sprints focused on user interface/experience
improvements.
• Cloud Infrastructure: Covers cloud servers, storage, and bandwidth needed for
development, testing, and initial deployment.
• Software Tools/Licenses: Includes version control (Bitbucket/GitHub), CI/CD
(Jenkins/GitLab), design (Figma/Adobe), and testing suites.
• Compliance & Security Audit: Third-party review of system security, GDPR/HIPAA
readiness.
• Meetings, Communication, Miscellaneous: Accounts for cross-site coordination,
stakeholder engagement tools, and incidental costs.
• Contingency: Ensures budget resilience against unexpected requirements, sprint
extensions, or urgent technical debt.

25
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

5. Project Brief
The Project Brief is a foundational document that formally launches the MedConnect project for
HealthSync Solutions Inc. It outlines the key objectives, scope, stakeholders, constraints, and
business case, ensuring alignment and shared understanding among all parties before project
execution begins. This document serves as a contract between management and the project team.

5.1. Document Information

Field Details

Project Name MedConnect

Date 16/04/2025

Author Shiv Kumar Yadav

Owner Shiv Kumar Yadav

Client HealthSync Solutions Inc.

Document Code 24059492

Version 1

Table 23 Document information

5.1.1. Project Brief History

Name Signature Title Date of Issue Version

Shiv Kumar Yadav Project Manager 16/04/2025 1

Emily Carter Client Representative 16/04/2025 1

Table 24 project brief history

26
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

5.1.2. Project Distribution

Name Title Date of Issue Version

Michael Thompson CEO 26/04/2025 1

Priya Sharma Product Owner 26/04/2025 1

Alex Kim Scrum Master 26/04/2025 1

Dr. Susan Lee Compliance Officer 26/04/2025 1

Dr. Rajiv Pandey Clinical Advisor 26/04/2025 1

John Cena DOPM 26/04/2025 1

Table 25 Project distribution list

5.2. Project Definition

5.2.1. Background
HealthSync Solutions Inc. is a multinational healthcare technology company with its main offices
in the USA and Nepal. The company aims to transform healthcare delivery through innovative
digital solutions. MedConnect is envisioned as a secure, AI-powered healthcare management
platform that streamlines communication and workflows for patients, clinicians, and
administrators, while ensuring compliance with international healthcare standards.

5.2.2. Project Objectives

• Deliver a robust, scalable, and user-friendly healthcare management platform.
• Enable secure appointment scheduling, telemedicine, and EHR integration.
• Ensure full compliance with HIPAA, GDPR, and local healthcare regulations.
• Support multilingual access and accessibility standards.
• Complete the project within a two-month timeframe and an agreed budget.

5.2.3. Desired Outcomes

• A fully functional, compliant MedConnect platform ready for deployment.
• Streamlined workflows for all user groups.
• Enhanced patient engagement and satisfaction.

27
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

• Improved reporting and analytics to support regulatory and operational needs.

5.2.4. Project Scope and Exclusions

Scope Includes:

• Secure user authentication and role-based access.

• Appointment management and telemedicine modules.
• EHR integration and compliance dashboards.
• Patient messaging, reminders, and notifications.
• Multilingual support and accessibility features.

Exclusions:

• Integration with third-party insurance or billing systems (future phase).

• Advanced analytics and predictive modeling (not in initial MVP).
• Ongoing hosting and domain registration costs after project delivery.

5.2.5. Constraints and Assumptions

• Time: Project to be completed within two months.
• Budget: Total budget capped at $95,850, ±10% tolerance.
• Resources: Cross-functional team distributed between the USA and Nepal.
• Assumptions: All compliance requirements will be clarified before Sprint 2; stakeholder
feedback will be incorporated at the end of each sprint.

5.2.6. Project Tolerance

• Time: ±1 week flexibility on the delivery schedule.
• Cost: ±10% deviation from the agreed budget.
• Scope: Minor feature adjustments allowed without board approval.
• Quality: Must meet minimum MVP acceptance criteria; non-critical enhancements
deferred.
• Risk: Proactive risk management with regular reviews.
• Benefit: Early MVP deployment to gather user feedback and demonstrate value.

28
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

5.2.7. The users and Other Interested Parties

• Primary Users: Clinicians, patients, administrators.
• Other Stakeholders: Compliance officers, IT support, senior management, external
auditors.

5.2.8. Interfaces
• Integration with existing EHR systems.
• Secure APIs for telemedicine and messaging.
• Interfaces for compliance reporting and third-party audit tools.

5.3. Outline Business case

5.3.1. Reasons
The healthcare industry is rapidly digitizing, with increasing demand for secure, interoperable
platforms that enhance patient care and streamline operations. MedConnect addresses these needs
with a modern, AI-driven solution that supports regulatory compliance and improves user
experience.

5.3.2. Expected Benefits

• Improved patient satisfaction and engagement.
• Reduced administrative burden for clinicians and staff.
• Enhanced compliance and risk management.
• Data-driven insights for operational improvement.

5.3.3. Time
• Project start: 01/05/2025
• Project end: 30/06/2025 (deployment and handover)

5.3.4. Cost
• Estimated total cost: $95,850

29
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

5.3.5. Major Risks and Mitigation

Risk Description Mitigation Strategy

Changes in healthcare laws or Regular consultation with compliance

Regulatory Changes standards may require design experts; build flexibility into system
alterations or rework. architecture.

Integration with legacy EHR Early technical assessment; allocate

EHR Integration
systems may cause delays or buffer time; use standardized APIs and
Complexity
technical issues. thorough testing.

Unauthorized access or data leaks Implement strong encryption, regular

Data Security
could compromise sensitive patient security audits, and strict access
Breaches
information. controls.

Time zone differences and remote Daily stand-ups, clear communication

Distributed Team
work may hinder coordination and protocols, and use of collaboration
Communication
slow decision-making. tools (e.g., Slack, Jira).

Key personnel may become Cross-training, maintain a skills

Resource
unavailable due to illness, turnover, matrix, and have backup resources
Availability
or other commitments. identified in advance.

Additional feature requests may Strict change control process; prioritize

Scope Creep arise, threatening deadlines and backlog using MoSCoW; regular
budget. stakeholder alignment.

Cloud outages or third-party service Use redundant systems, regular

Technology Failures failures could disrupt development backups, and robust disaster recovery
or deployment. planning.

Early user involvement,

User Adoption Users may resist adopting the new
comprehensive training, and
Challenges platform or underutilize features.
responsive support channels.

30
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Table 26 Risk and its mitigation

5.4. Project Product Description

5.4.1. Title
MedConnect – AI-Driven Healthcare Management Platform

5.4.2. Purpose
To provide a secure, efficient, and user-friendly digital platform for healthcare providers and
patients, supporting clinical workflows, patient engagement, and regulatory compliance.

5.4.3. Composition
• Web-based application accessible via browser and mobile devices.
• Modular architecture for future expansion.
• Core modules: appointment scheduling, telemedicine, EHR integration, compliance
dashboard, messaging.

5.4.4. Development Skills Required

• Full-stack web development (Python, Django, React)
• Cloud infrastructure management (AWS/Azure)
• UI/UX design for accessibility
• Healthcare compliance expertise
• Quality assurance and automated testing

5.4.5. Customer’s Quality Expectations

• Intuitive and accessible user interface.
• High system reliability and uptime.
• Robust data security and privacy.
• Responsive support and clear documentation.

5.4.6. Acceptance Criteria, Methods, and Responsibilities

• All MVP features delivered and tested.
• Compliance with HIPAA/GDPR verified by Compliance Officer.
• User acceptance testing completed by clinicians and administrators.
• Documentation and training materials provided.

31
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

5.5. Project Approach

MedConnect will be developed using the Scrum framework, enabling iterative delivery and regular
stakeholder feedback. PRINCE2 principles will guide project governance, risk management, and
quality assurance. The cross-functional team will use digital collaboration tools (Jira, Slack, Zoom)
to coordinate across time zones.

5.6. Project Management Team Structure

• Project Board: Michael Thompson (CEO), Priya Sharma (Product Owner), Dr. Susan Lee
(Compliance Officer)
• Project Manager: Shiv Kumar Yadav
• Scrum Master: Alex Kim
• Development Team: Developers, QA, UI/UX, Clinical Advisor

5.7. Roles Description

• CEO (Michael Thompson): Oversees project direction and resource allocation.
• Product Owner (Priya Sharma): Defines vision, manages backlog, prioritizes features.
• Scrum Master (Alex Kim): Facilitates Scrum events, removes impediments.
• Developers: Implement features, conduct code reviews.
• QA Engineer: Ensures product quality through testing.
• Compliance Officer (Dr. Susan Lee): Verifies regulatory adherence.
• Clinical Advisor (Dr. Rajiv Pandey): Validates clinical workflows and requirements.

32
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

6. Lifecycle Integration – PRINCE2 and Scrum for MedConnect

MedConnect’s delivery leverages the strengths of both PRINCE2 (structured, stage-based
governance) and Scrum (iterative, Agile development). This hybrid model ensures robust project
control, regulatory alignment, rapid delivery, and ongoing stakeholder value.

6.1. PRINCE2 Overview

PRINCE2 (Projects IN Controlled Environments) is a process-based project management
methodology offering a structured approach to project governance, while Scrum is an agile
framework focusing on iterative delivery. For MedConnect, a healthcare platform requiring both
compliance rigor and adaptive development, understanding how these methodologies can
complement each other is essential for project success.

PRINCE2 provides an overarching governance framework, focusing on business justification,

organized stages, and clear accountability. It doesn't dictate how teams should complete work, but
rather establishes guidelines for when work should be done, how it should be tracked, and how
quality is ensured. This makes it particularly valuable for healthcare software projects where
regulatory compliance and formal documentation are critical (Axelos, 2023).

Figure 4 PRINCE2 and Scrum (Puscasu, 2025)

33
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

The PRINCE2 Process offers a practical framework for product development. Scrum's emphasis
on incremental delivery, stakeholder feedback, and team self-organization aligns well with
MedConnect's need to adapt to evolving healthcare requirements and AI capabilities.

For HealthSync Solutions, integrating PRINCE2 for overall management with Scrum for delivery
can create a balanced approach that satisfies both governance requirements and development
flexibility. PRINCE2 can provide the high-level roadmap and management structure, while Scrum
can efficiently manage complex, uncertain aspects of healthcare software delivery.

Figure 5 PRINCE2 Process (INFINITY, 2025)

PRINCE2 project management methodology based on seven principles, seven themes, and seven
processes. Its process-based approach provides a comprehensive framework applicable to projects
of any size or complexity, making it particularly valuable for regulated environments like
healthcare.

34
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

The Seven Principles of PRINCE2:

I. Continued Business Justification: Projects must remain viable from a business

perspective throughout their lifecycle. For MedConnect, this means continually ensuring
the platform delivers value to healthcare providers and patients while meeting regulatory
requirements.
II. Learn from Experience: PRINCE2 emphasizes capturing lessons from past projects and
applying them to current work. For healthcare technology, where patient safety and data
security are paramount, this principle ensures continuous improvement in quality and
compliance.
III. Defined Roles and Responsibilities: PRINCE2 clearly defines who is responsible for
what, creating a transparent governance structure. For MedConnect, this clarity ensures
that clinical, technical, and compliance aspects all receive appropriate oversight.
IV. Manage by Stages: Breaking the project into manageable stages allows for controlled
progress and regular evaluation. Each stage of MedConnect's development can be assessed
for quality, compliance, and alignment with business objectives before proceeding.
V. Manage by Exception: PRINCE2 establishes tolerance levels for various project
parameters. This allows MedConnect's management to focus attention where needed most,
while empowering teams to proceed independently within established boundaries.
VI. Focus on Products: Emphasis on clearly defined outputs ensures that everyone
understands what needs to be delivered. For MedConnect, this means detailed
specifications for each module, from appointment scheduling to AI-driven diagnostics.
VII. Tailor to Suit Project Environment: PRINCE2 can be adapted to the specific needs of
each project. For MedConnect, this flexibility allows for integration with Scrum while
maintaining compliance with healthcare regulations.

The Seven Themes of PRINCE2:

• Business Case: Establishing and maintaining justification for the project

• Organization: Defining project roles and responsibilities
• Quality: Ensuring outputs meet requirements
• Plans: Developing and maintaining project plans
• Risk: Identifying, assessing, and controlling risks

35
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

• Change: Identifying, assessing, and controlling changes

• Progress: Monitoring and controlling project progress

The Seven Processes of PRINCE2:

1) Starting Up a Project (SU): Initial evaluation and setup

2) Directing a Project (DP): Strategic guidance throughout the project
3) Initiating a Project (IP): Detailed planning and documentation
4) Controlling a Stage (CS): Day-to-day management
5) Managing Product Delivery (MP): Coordinating work packages
6) Managing Stage Boundaries (SB): Transitioning between stages
7) Closing a Project (CP): Formal project conclusion and evaluation

Features of PRINCE2:

• Business case-driven decision making

• Defined organizational structure
• Product-based planning approach
• Management by stages and exception
• Flexibility to adapt to project requirements

Advantages of PRINCE2 for MedConnect:

• Provides robust governance essential for healthcare software

• Clearly defines roles and responsibilities
• Offers a well-documented approach for regulatory compliance
• Establishes systematic escalation and problem-solving procedures
• Supports business-oriented, user-centered product development
• Enables controlled, coordinated project stages.

36
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Perceived Limitations of PRINCE2:

Limitation Description Relevance to MedConnect

Documentation Can create extensive May add burden to development teams but
Overhead documentation requirements supports regulatory compliance

Implementation Requires significant setup and Initial investment pays off through reduced
Time training risks and compliance issues

Flexibility May appear too rigid for rapidly Needs tailoring to accommodate healthcare
Concerns changing requirements innovation while maintaining structure

Focuses on processes rather Needs complementary approaches to

than leadership or team address team collaboration across US and
Soft Skills Gap dynamics Nepal offices

Requires training and

experience to implement Investment in training necessary for
Learning Curve effectively distributed teams

Table 27 Perceived Limitations (PRINCE2)

6.2. SCRUM Overview

Scrum is an agile framework designed for complex product development, emphasizing iterative
progress, team collaboration, and rapid adaptation to change. It provides a structured yet flexible
approach to delivering value incrementally, making it well-suited for MedConnect's evolving
healthcare requirements (MOUNTAIN GOAT SOFTWARE, 2024).

Scrum Roles:

1. Product Owner: In MedConnect, the Product Owner maintains the product backlog,
prioritizes features based on business value, clinical needs, and regulatory requirements,
and ensures the development team understands the requirements. They represent
stakeholders including clinicians, patients, and administrators.

37
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

2. Scrum Master: The Scrum Master facilitates the Scrum process, removes impediments,
and coaches the team on agile practices. For MedConnect, they help navigate the
complexity of healthcare software development while ensuring adherence to both Scrum
practices and regulatory requirements.

3. Development Team: A cross-functional group of professionals who deliver potentially

releasable increments of the product. MedConnect's development team includes software
engineers, UI/UX designers, QA specialists, and domain experts who collectively possess
the skills to implement all aspects of the healthcare platform.

Scrum Events:

1. Sprint: A time-boxed period (typically 2-4 weeks) during which the team works to
complete a set of committed user stories. For MedConnect, each sprint delivers a
potentially releasable increment with features like appointment scheduling, telemedicine
capabilities, or compliance reporting.

2. Sprint Planning: At the start of each sprint, the team selects items from the product
backlog and determines how to accomplish the work. For MedConnect, this includes
understanding clinical workflows, compliance requirements, and technical dependencies.

3. Daily Scrum: A 15-minute daily meeting where team members synchronize activities and
plan for the next 24 hours. This is crucial for MedConnect's distributed team across the
USA and Nepal.

4. Sprint Review: At the end of the sprint, the team demonstrates the completed work to
stakeholders. For MedConnect, this might include demonstrating new features to clinicians
and administrators to gather feedback.

5. Sprint Retrospective: A meeting where the team reflects on the past sprint and identifies
improvements. For MedConnect, this helps continuously refine both the product and the
development process.

38
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Scrum Artifacts:

1. Product Backlog: An ordered list of everything needed in the product. MedConnect's

product backlog includes features like secure patient data storage, appointment scheduling,
and AI-driven symptom analysis.

2. Sprint Backlog: The set of product backlog items selected for the sprint, plus a plan for
delivering them. For MedConnect, this might include specific user stories related to a
particular module or feature.

3. Increment: The sum of all completed product backlog items at the end of a sprint. Each
increment of MedConnect must meet the "Definition of Done," including security and
compliance requirements.

Advantages of Scrum for MedConnect:

• Enables rapid adaptation to changing healthcare requirements and regulations

• Provides regular feedback cycles to ensure alignment with user needs

• Supports incremental delivery of value

• Promotes transparency and collaboration across distributed teams

• Facilitates continuous improvement of both product and process

39
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

Perceived Limitations of SCRUM:

Limitation Description Relevance to MedConnect

Scope Potential for scope creep Requires integration with PRINCE2 to

Management without strong governance manage healthcare compliance requirements

Limited emphasis on formal May need augmentation for healthcare

Documentation documentation regulatory compliance

Originally designed for small, Requires adaptation for distributed teams

Scalability co-located teams across USA and Nepal

Can be challenging to provide Healthcare stakeholders may need more

Predictability long-term forecasts certainty for planning

Heavily dependent on team Cross-cultural and geographic distribution

Team Dynamics cohesion and skills may present challenges

Table 28 Perceived Limitations (SCRUM)

40
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

6.3. Comparative Analysis of PRINCE2 and SCRUM

Understanding the similarities, differences, and potential integration points between PRINCE2 and
Scrum is crucial for effectively managing MedConnect's development.

Aspect PRINCE2 Scrum Implications

for MedConnect

Principles Seven principles focusing on Emphasizes transparency, Complementary

business justification, defined inspection, and adaptation philosophies supporting both
roles, and product focus governance and flexibility

Budgets Fixed before project initiation Evolves with project Need for flexible budgeting
progression within governance
constraints

Documentation Structured and comprehensive Minimal, emphasizing Balance required for

working software regulatory compliance and
development agility

Basis Plan-driven approach Product and value- Integration needed to

oriented maintain both direction and
adaptability

Adaptability Changes managed through Embraces change and Structured flexibility

formal control rapid adaptation essential for healthcare
innovation

Implementation Work packages Sprints and increments Work packages can be

delivered via sprints

Roles Comprehensive role structure Three core roles: Product Clear mapping needed
including project manager Owner, Scrum Master, between governance and
Development Team delivery roles

Table 29 Comparative Analysis (PRINCE2 and SCRUM) (Eljayar & Busch, 2021)

41
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

6.3.1. In terms of phases

Phase PRINCE2 Scrum Integration for MedConnect

Initiation Starting up a project: Product Backlog Creation: Product backlog can be created
Gathering project mandate, Collecting and prioritizing during PRINCE2 initiation,
creating project brief user stories aligned with business case

Direction Directing a project: Board N/A Board oversight of product vision

review and approval of and strategic direction
business alignment

Planning Initiating a project: Detailed Sprint Planning: Selecting Project initiation documents
documentation and planning backlog items for establish boundaries for sprint
implementation planning

Execution Controlling a stage: Work Sprint: Implementation of Work packages can be

package management by selected backlog items implemented through sprints, with
project manager stage control providing
governance

Monitoring Managing Product Sprint Review: Regular reviews align with both
Delivery: Quality assurance Demonstration and methodologies, supporting quality
and progress tracking feedback and stakeholder engagement

Boundaries Managing Stage N/A (but Sprint Stage boundaries can align with
Boundaries: Review and Retrospective serves major releases, with retrospectives
decision on proceeding similar purpose) driving improvement

Closure Project Closure: Formal Sprint Retrospective: Team Project closure can incorporate
closeout and documentation evaluation and lessons from all retrospectives
improvement

Table 30 Comparative Analysis (In terms of Phase)

42
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

6.3.2. In terms of Roles

PRINCE2 Scrum Integration for MedConnect

Project Board (Executive, Product Owner Product Owner reports to Project Board,
Senior User, Senior Supplier) which provides strategic direction and
approval

Change Authority N/A Can be integrated with Product Owner role

for requirement changes

Project Assurance N/A Important for healthcare compliance; can be

assigned to specific team members

Project Manager Scrum Master Project Manager focuses on governance

(partially) while Scrum Master facilitates delivery

Team Manager Scrum Master Scrum Master takes on team facilitation

(partially) aspects

Development Team Development Direct mapping; the team doing the work
Team

Table 31 Comparative Analysis (In terms of role)

43
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

6.3.3. In terms of Deliverables

PRINCE2 Scrum Integration for MedConnect

Baseline Management Product Vision Statement Vision statement aligns with and supports
Products baseline documentation

Records and Logs N/A Important for healthcare compliance;

maintained alongside Scrum artifacts

Reports (Checkpoint, End Burndown Charts, Scrum visibility tools can feed into formal
Project, Issues) Information Radiators PRINCE2 reporting

Product Breakdown Product Backlog Product Backlog can be structured

Structure according to PBS

N/A Sprint Backlog Becomes the detailed plan for work

package delivery

N/A Product Increment Aligned with PRINCE2 product

descriptions and quality criteria

Incorporates PRINCE2 quality criteria and

N/A Definition of Done compliance requirements

Table 32 Comparative Analysis (In terms of Deliverables)

44
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

6.4. Conclusion
For HealthSync Solutions' MedConnect project, integrating PRINCE2 and Scrum offers
significant advantages. The structured governance of PRINCE2 provides the control and
compliance essential for healthcare software, while Scrum's flexibility and iterative approach
enable rapid adaptation to changing requirements and continuous stakeholder feedback.

An effective integration approach for MedConnect would involve:

1. Using PRINCE2 at the project governance level: Establishing business justification,

defining stages, managing risks, and ensuring compliance with healthcare regulations.

2. Implementing Scrum at the delivery level: Organizing development work into sprints,
maintaining product and sprint backlogs, and delivering incremental value through regular
releases.

3. Defining clear interfaces between methodologies: Mapping Project Board decisions to

Product Owner priorities, aligning stage boundaries with major releases, and ensuring
PRINCE2 reporting incorporates Scrum metrics.

4. Tailoring both methodologies: Adapting PRINCE2 documentation requirements to be

more agile while ensuring Scrum practices accommodate necessary compliance
documentation.

5. Balancing control and flexibility: Maintaining appropriate governance while

empowering teams to self-organize and respond to change within established boundaries.

This hybrid approach provides MedConnect with a robust management framework that satisfies
both organizational governance needs and the practical requirements of developing an innovative
healthcare platform in a rapidly evolving market.

45
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

References
• Agile Alliance, 2025. Agile Alliance. [Online]
Available at: [Link]
[Accessed 01 May 2025].

• Axelos, 2023. Managing Successful Projects with PRINCE2. 7th ed. s.l.:Stationery
Office.

• Buehring, S., 2024. whatisprince2. [Online]

Available at: [Link]
[Accessed 17 April 2025].

• Eljayar, A. & Busch, S. J., 2021. Agile-Stage-Gate Approach: Exploratory Research on the
Structure, Roles, and. Athens Journal of Technology and Engineering, 8(1), pp. 39-90.

• ILX Group, 2025. [Link]. [Online]

Available at: [Link]
[Accessed 17 April 2025].

• INFINITY, 2025. INFINITY. [Online]

Available at: [Link]
[Accessed 25 April 2025].

• KPI PARTNERS, 2025. Traditional vs. Agile Software Development Methodologies.

[Online]
Available at: [Link]
development-methodologies
[Accessed 16 April 2025].

• Matthews, B., 2024. Project-management. [Online]

Available at: [Link]
matrix-raci-matrix/
[Accessed 17 April 2025].

• Mohideen, I. & Mohideen, I., 2022. ibraheemsblog. [Online]

Available at: [Link]
46
Shiv Kumar Yadav CC7169NI May 9, 2025
Shiv Kumar Yadav CC7169NI May 9, 2025

methodologies/
[Accessed 16 April 2025].

• MOUNTAIN GOAT SOFTWARE, 2024. MOUNTAIN GOAT SOFTWARE. [Online]

Available at: [Link]
[Accessed 01 May 2025].

• ProductPlan, 2024. ProductPlan. [Online]

Available at: [Link]
[Accessed 01 May 2025].

• Prokopets, E., 2020. edvantis. [Online]

Available at: [Link]
[Accessed 17 April 2025].

• Puscasu, A., 2025. PRINCE2 and Scrum, Integration. [Online]

Available at: [Link]
[Accessed 25 April 2025].

• Robinson, S., Brush, K. & Silverthorne, V., 2024. TechTarget. [Online]

Available at: [Link]
software-development
[Accessed 16 April 2025].

47
Shiv Kumar Yadav CC7169NI May 9, 2025