You are on page 1of 24

A Project Synopsis on Implementation of Agile Methodology in Healthcare IT Industry

Internal Guide, Dr. K V A BALAJI Professor and HOD Department of Mechanical Engineering External Guide, KRISHNARAJ C K Senior Design Engineer GE-HCIT By, ARAVINDA H S (4JC10MEM01)


Agile software development is a group of Software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between Self-organizing, Cross functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change.

Objectives of the study

Understand the current software development methodologies like waterfall and its shortcomings. To explain the principles and practices of Agile Scrum Methodology.

Advantages of Agile methodology over Waterfall method.

To explain how an agile methodology leads to faster delivery of more useful software

To study how product quality can be improved by adopting agile


Present Methodology
Classical methods of software development have many disadvantages:

Huge effort during the planning phase at the start of the project.

Poor requirements conversion in a rapid changing environment

Long release cycle (1 to 2 year) Customer feedback only at the end of product development. Product delivery only when all the product features are complete. Poor product quality and large number of bugs reported from customer.

Agile methods: Scrum Extreme Programming Adaptive Software Development (ASD) Dynamic System Development Method (DSDM)

Proposed Methodology

Agile methods provide early and constant feedback

Short release cycle (1 to 6 months) Issues are identified well in advance through the daily meetings and hence can be resolved in speedily Agile methods adapt to change, as at the end of each stage, the logical programme, designed to cope and adopt to new ideas from the outset, allows changes to be made easily. With Agile, changes can be made if necessary without getting the entire programme rewritten. Agile scrum helps the company in saving time and money


A Framework within which people can address complex

adaptive problems,while productively and creatively

delivering products of the highest possible value

Scrum Framework

Roles : Product Owner, ScrumMaster, Team

Meetings : Sprint Planning, Sprint Review, Sprint

Retrospective, & Daily Scrum Meeting Artifacts : Product Backlog, Sprint Backlog, and Burndown Chart

Product Owner

Define the features of the product Decide on release date and content Be responsible for the profitability of the product (ROI) Prioritize features according to market value

Adjust features and priority every iteration, as needed

Accept or reject work results.

The Scrum Master

Represents management to the project Responsible for enacting Scrum values and practices Removes impediments

Ensure that the team is fully functional and productive

Enable close cooperation across all roles and functions

Scrum Team
Team is cross-functional and consists of 5-9 people

Team is self-organizing and self-managing

Team defines tasks and assignments Maintains the sprint Backlog Conducts the sprint Review


1. Sprint Planning Meeting

2. Sprint
3. Daily Scrum 4. Sprint Review Meeting


A month-long iteration, during which is incremented a

product functionality
NO outside influence can interfere with the Scrum team during the Sprint Each Sprint begins with the Daily Scrum Meeting

Sprint Planning Meeting

Product Backlog Team Capabilities Business Conditions Technology

Sprint Planning

Sprint Goal Sprint Backlog

Daily Scrum
Held every day(15minutes) during a Sprint
Asks Three questions during meeting: What did you do yesterday? What will you do today? What obstacles are in your way?

Opportunity for team members to synchronize their work

Sprint Review Meeting

Team presents donecode to product owner and stakeholders Functionality not done is not shown

Scrum Master Sets next Sprint Review

Done=Potentially Shippable! Participants Customers Management

Product Owner
Other engineers

Sprint Retrospective Meeting

Questions- What went well and what can be improved? Participants - Scrum Master - Team - Product owner

Product Backlog

A list of all desired work on the project List is prioritized by the Product Owner Typically a Product Manager, Marketing, Internal Customer, etc. Requirements for a system, expressed as a prioritized list of Backlog Items Is managed and owned by a Product Owner

Sprint Backlog

A subset of Product Backlog Items, which define the

work for a Sprint

Is created ONLY by Team members Each Item has its own status Should be updated every day

Sprint Burn down Chart

Depicts the total Sprint Backlog hours remaining per day

Shows the estimated amount of time to release

Ideally should burn down to zero to the end of the Sprint Maintained by Scrum Master daily

Scrum values

Transparency - visibility to everyone Commitment - willing to commit to a goal Courage - courage to commit, open, and to embrace change Focus focus on the work you have committed

Respect - respect and trust people

How Scrum Works?


1 unit = 1 week

% COMPLETED 05 % 10 % 15 % 30 % 35 % 50%

Statement of problem Synopsis evaluation Literature review Questionnaires design 2nd phase presentation Data collection






55 %
70% 80% 85 % 95 % 100 %

Data interpretation
Data processing Report writing 3rd Phase presentation
Draft Report 1,2,3 submission

Final report submission