Scribd
Upload
141 views

Agile Software Development

Scrum is an iterative, incremental process for managing product development. It uses sprints (typically 4 weeks) where a prioritized backlog of work items is completed. A scrum team includes a product owner, development team, and scrum master. At the end of each sprint, completed work should be in a potentially shippable state for review. Daily stand-ups help coordinate work, while retrospectives aid process improvement.

Uploaded by

Zainab Noorain
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
141 views

Agile Software Development

Scrum is an iterative, incremental process for managing product development. It uses sprints (typically 4 weeks) where a prioritized backlog of work items is completed. A scrum team includes a product owner, development team, and scrum master. At the end of each sprint, completed work should be in a potentially shippable state for review. Daily stand-ups help coordinate work, while retrospectives aid process improvement.

Uploaded by

Zainab Noorain
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

Agile Method:

SCRUM
By,
Zainab Noorain
SCRUM - Introduction
• Iterative, Incremental Process
• Theme - “inspect and adapt”
• Sprint – Cycles of work / Iteration
Approx. 4 weeks
Items or jobs are prioritized.
No job additions later

• Popular Scrum software development tools


Jira by Atlassian, Axosoft OnTime, etc.
Sprint
Sprint Features
Scrum Team
• Product Owner - Identifying product features,
translating these into a prioritized list. Also referred to
as Project Manager. Manages Product Backlog

• Development Team – Builds the product. Cross


functional – Includes all expertise and demonstrate
multi learning – Professionals with many skills.

• Scrum Master – Help the Scrum team skilfully use


Scrum.
Backlog
• Product Backlog, a prioritized list of customer-
centric features
Backlog - Features
• Detailed appropriately – Top priority items are detailed
• Estimated Release – Items necessary for current Release
• Emergent – changes to be made
• Prioritized – higher business value items are top priority
• Story points – Sequence of events encountered –
complexities, hurdles.
Potentially Shippable Product
• Output of a Sprint.
• Scrum Team agree on Definition of Done.

Review Requirements for


Product Backlog

Plan Sprint work

Prioritize items

Complete item - DONE


Sprint Planning
• Part One: (What?) – Sprint Goal (2 hrs)
Review the high-priority items in the Product
Backlog that the Product Owner is interested in
implementing this Sprint

• Part Two: (How?) – (2 hrs)


How to implement the items that the Team
decides to take on, by the end of the Sprint?
Daily Scrum
• Update and coordination between the Team
members.
• Team members synchronize their work and report to
each other on obstacles
• 3 Questions
1.What has been accomplished since the last
meeting?
2.What will be done before the next meeting?
3.What obstacles are in the way?
Tracking progress of Sprint
• Sprint Burndown Chart - estimate of how much work
remains until the End of the Sprint.
Product Backlog Refinement
• Split big items, analyse items, re-estimate, and re-
prioritize, for future Sprints

Sprint Review
• 2 Hour meeting (Clients may be present)
• Reviewing completed work
• Discussion on risks and constraints.
• Includes using the actual live software demonstration
that the Team built during the Sprint only if completed.
Sprint Retrospective
• Inspection and adaption related to the process and
environment.
• Team discuss on what’s working and what’s not
working, and agree on changes to be tried.
End of Sprint
• Following the Sprint Review, the Product Owner
updates the Product Backlog with any new insight –
adding new Items, removing obsolete ones, or
revising existing ones.

• At the end of each sprint, the product has to be


potentially shippable. No testing or documentation
must be left.
• “Release Sprint” is required in case of unfinished
work at the end of the sprint. Team has to improve
their development tools and skills.
Acknowledgement
• The SCRUM Primer, Ver 2.0,
http://www.goodagile.com/scrumprimer/scrumpri
mer20.pdf
• Jira By Atlassian
Thank You

You might also like