Your SlideShare is downloading. ×
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Scrum luqman
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum luqman


Published on

Published in: Technology, Business
1 Like
  • @ThichLuong
    Shippable is some tanglibe deliverable. It can be a software product, a requirement/design document, a prototype, test result etc., which can be delivered. If you say 'The output of this sprint is just the effort estimation of the entire project', it is not acceptable, as it not tanglibe hence it is not shippable.
    Are you sure you want to  Yes  No
    Your message goes here
  • Can you help me.What does it mean shippable
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. SCRUM
    Mohammed Luqman Shareef
  • 2. Agenda
    What is scrum?
    Roles in scrum
    Scrum artifacts
    Scrum meetings
    Q & A
  • 3. What is Scrum?
    Scrum is an agile approach to software development.
    It is an iterative development. The project progresses in series of Sprints.
    There is no team lead. Teams are self-organizing. Scrum Master is a coach for the team.
  • 4. Ham and Egg story
    A chicken and a pig decide to start a restaurant.
    Chicken says “Lets call it Ham and Eggs!"
    Pig replies “No Thanks, You’d only be involved where as I’d be committed!"
  • 5. Roles in Scrum
    Committed (Pigs)
    Product Owner
    Scrum Master
    Team Member
    Involved (Chickens)
    Stakeholders (Users, Customers..)
  • 6. Roles in Scrum
    Product Owner
    Writes User stories.
    Creates product backlog.
    Prioritizes user stories.
    Scrum Master
    Is a team member and NOT a team lead.
    Makes sure Scrum team lives by the values and practices of Scrum.
    Facilitates Daily Standup and Sprint Review meetings.
    Responsible for delivering the product.
    Typically made of 5-7 people.
  • 7. What is Sprint?
    Sprint is a time-boxed iteration, typically 2-4 weeks.
    Output is a shippable product (No matter how basic it is).
    A release typically consists of multiple sprints.
    Each Sprint starts with Sprint planning, having daily scrum meetings, ends with Sprint review followed by sprint retrospective.
  • 8. Scrum artifacts
    Product Backlog
    Sprint Backlog
    Product burn down chart
    Sprint burn down chart
    Team Velocity
  • 9. Product backlog
    Managed by product owner.
    It is the list of all the features to be added to the product.
    Contains user stories ( a short description of customer requirements).
    User stories re-prioritized by product owner after each sprint.
  • 10. Scrum Meetings
    Sprint Planning
    Daily Standup
    Sprint Review
    Sprint Retrospective
    Only pigs are allowed to speak, chicken are welcomed only to listen.
  • 11. Sprint Planning
    Estimate the effort/Story points from the product backlog.
    Planning Game / Poker
    Each User story is divided into Engineering tasks
    Every team member gets a deck of cards with numbers representing story points.
    For each user story every one estimates and show the card with that number.
    Discuss the discrepancies and finalize the story points.
    Determine the Sprint goal.
    Plan for the user stories for next sprint.
    Out come is ‘Sprint Backlog’ (list of user stories to be completed).
    Tasks are signed up by team members (Not assigned).
  • 12. Daily scrum meeting
    Not more than 15 mins.
    No problem solving
    Same time and same location
    3 Questions
    What did you do yesterday?
    What obstacles are in your way?
    What will you do today?
  • 13. SPRINT review
    Team presents the product that has bee built during the sprint to management, customer and product owner.
    3 Questions
    What was the Sprint goal?
    What was committed from Product backlog?
    What is completed?
    Product owner checks against DONE criteria.
    Executed from dev environment.
    Stake holders comment/criticize on the developed functionality
    Identify not completed and new functionality to be added to the product backlog
  • 14. SPRINT Retrospective
    End of each sprint
    Product owner, Scrum master and team are involved.
    3 Questions
    What went well (Continue doing this)
    What didn’t go well (Stop doing this)
    Improvement areas (Start doing this)
  • 15. Burn down charts
    To track progress
    Sprint burn down chart
    Shows number of tasks left in the current sprint backlog.
    Updated daily by scrum master and uploaded to a shared location (sharepoint).
    Product burn down chart
    Shows number of requirements left.
    Requirements can be added/removed.
  • 16. Team Velocity
    Team velocity = Number of story points burnt in a sprint.
    If a team of 4 members complete 3 user stories with story points 5,5,8 story points respectively.
    Team velocity = (5 + 5 + 8 ) / 4
    = 4.5 user stories per person in a sprint
  • 17. Advantages
    Increased productivity.
    Continuous development process improvement.
    Team gets focused. One common goal.
    More accountability and responsibility.
    Flat structure, No manager-sub ordinate relation.
    Team work, No individual failure/success.
    Higher visibility.
    Better evaluation.
  • 18. Questions?
  • 19. Thank you