Agile 2012

7/31/2019 Agile 2012

http://slidepdf.com/reader/full/agile-2012 1/24

A Project Synopsis on

“Implementation of Agile Methodology in

Healthcare IT Industry” Internal Guide, By,Dr. K V A BALAJI ARAVINDA H S

Professor and HOD (4JC10MEM01)

Department of Mechanical Engineering

External Guide,

KRISHNARAJ C KSenior Design Engineer

GE-HCIT

7/31/2019 Agile 2012


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.

DEFINITION

7/31/2019 Agile 2012


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

methodology.

Objectives of the study

7/31/2019 Agile 2012


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.

Present Methodology

7/31/2019 Agile 2012


7/31/2019 Agile 2012


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

7/31/2019 Agile 2012


A Framework within which people can address complex

adaptive problems,while productively and creatively

delivering products of the highest possible value

Scrum

7/31/2019 Agile 2012


Roles : Product Owner, ScrumMaster, Team

Meetings : Sprint Planning, Sprint Review, Sprint

Retrospective, & Daily Scrum Meeting

Artifacts : Product Backlog, Sprint Backlog, and

Burndown Chart

Scrum Framework

7/31/2019 Agile 2012


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.

Product Owner

7/31/2019 Agile 2012


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

The Scrum Master

7/31/2019 Agile 2012


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

Scrum Team

7/31/2019 Agile 2012


1. Sprint Planning Meeting

2. Sprint

3. Daily Scrum

4. Sprint Review Meeting

Meetings

7/31/2019 Agile 2012


7/31/2019 Agile 2012


Sprint Planning

Meeting

Sprint Planning Meeting

Product Backlog

Team Capabilities

Business Conditions

Technology

Sprint Backlog

Sprint Goal

7/31/2019 Agile 2012


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

Daily Scrum

7/31/2019 Agile 2012


Team presents “done”code 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 Review Meeting

7/31/2019 Agile 2012


Questions- What went well and what can be improved?

Participants

- Scrum Master

- Team

- Product owner

Sprint Retrospective Meeting

7/31/2019 Agile 2012


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

Product Backlog

7/31/2019 Agile 2012


A subset of Product Backlog Items, which define the

work for a Sprint

Is created ONLY by Team members

Each Item has it’s own status

Should be updated every day

Sprint Backlog

7/31/2019 Agile 2012


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

Sprint Burn down Chart

7/31/2019 Agile 2012


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

Scrum values

7/31/2019 Agile 2012


How Scrum Works?

7/31/2019 Agile 2012


% COMPLETED PROJECT ACTIVITIES February March April May June

05 % Statement of problem

10 %Synopsis evaluation

15 % Literature review

30 % Questionnaires design

35 % 2nd phase presentation

50% Data collection

55 % Data interpretation

70% Data processing

80% Report writing

85 % 3rd Phase presentation

95 % Draft Report 1,2,3 submission

100 % Final report submission

PROJECT ACTIVITIES TIME CHART 1 unit = 1 week

7/31/2019 Agile 2012


Documents

Agile 2012