Professional Documents
Culture Documents
Do You Agree ?
• Most projects have challenges meeting
timelines
• Most projects have defects
• Most projects are inflexible to change
• Business need change by the time product
is ready for market
12/08/21 2
Iterative Development – Scrum can
• Reduce development time – hence better
productivity
• Reduce defects – better quality
• Reduce time to market – Improved ROI
• Improve flexibility
• Receptive to changes
• Improve visibility
12/08/21 3
Agenda
• What is Scrum
• Scrum Artifacts
• Scrum Meetings
• Scrum at PayCalc
12/08/21 4
What is Scrum?
24 hours
Daily Scrum
Meeting
Potentially Shippable
Product Backlog Product Increment
As prioritized by Product Owner
Source: Adapted from Agile Software
Development with Scrum by Ken
Schwaber and Mike Beedle.
12/08/21 5
What is Scrum?
• Roles
– Product Owner
• Possibly a Product Manager or Project Sponsor
• Marketing
• Internal Customer
• etc.
– ScrumMaster
• Represents management to the project
• Typically filled by a Project Manager or Team Leader
• Responsible for enacting Scrum values and practices
• Main job is to remove impediments and remove any politics
– Project Team
• 5-10 members
• Cross-functional: QA, Programmers, UI Designers, etc.
12/08/21 6
What is Scrum?
• Daily “stand up” meetings
– Only the ScrumMaster and the project team are allowed to talk:
outsiders may listen in, but are removed should they say anything
• This is all about who is committed to the project or not…
12/08/21 7
What is Scrum?
• Daily “stand up” meetings
– Three questions:
1. What did you do yesterday
2. What will you do today?
3. What obstacles are in your way?
12/08/21 8
Agenda
• What is Scrum
• Scrum Artifacts
• Scrum Meetings
• Scrum at PayCalc
12/08/21 9
Scrum’s Artifacts
• Scrum has remarkably few artifacts
– Product Backlog
– Sprint Backlog
– Burndown Charts
12/08/21 10
Agenda
• What is Scrum
• Scrum Artifacts
• Scrum Meetings
• Scrum at PayCalc
12/08/21 11
Scrum Meetings
• Following meetings are planned:
– Scrum planning meeting
– Daily scrum meeting
– Retrospective
– Sprint review meeting
12/08/21 12
Summary
• Create list of user stories – Product Backlog
• Prioritize the User Stories
• Estimate the user stories
• Plan a sprint based on the capacity
• Do Scrum meeting to keep track of status and
make adjustments to work book as required
• Update learning document after each Sprint
12/08/21 13
Summary
• Careful about:
– Estimates – Do not overestimate /
underestimate. Review estimate along with
peer to ensure it is realistic
– Task break down – Logical break down. Make
a work flow
12/08/21 14
• Thank You
12/08/21 15