Introduction To Scrum
Upcoming SlideShare
Loading in...5
×
 

Introduction To Scrum

on

  • 8,473 views

This is an Introduction to Scrum presentation by Deepak Mittal, IntelliGrape software.

This is an Introduction to Scrum presentation by Deepak Mittal, IntelliGrape software.

Statistics

Views

Total Views
8,473
Views on SlideShare
8,469
Embed Views
4

Actions

Likes
2
Downloads
847
Comments
0

1 Embed 4

http://www.slideshare.net 4

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Introduction To Scrum Introduction To Scrum Presentation Transcript

  • Introduction to Scrum
      • Presented
      • at
      • Agile Awareness Workshop
      • conducted by Xebia
      • by
      • Deepak Mittal, IntelliGrape Software
      • on
      • June 14, 2008
  • Agenda
    • Agile Manifesto
    • What is Scrum
    • Scrum core ideas
    • Difficulties with practising Scrum
    • Questions
    • Feedback
  • Quick Poll
    • Agile Manifesto.
    • Scrum.
    • Agile methodologies.
    • Requirements can be frozen.
    • Standish Group report.
  • Agile Manifesto
    • Individuals and Interactions over processes and tools
    • Working software over comprehensive documentation
    • Customer collaboration over contract negotiation
    • Responding to change over following a plan.
  • Scrum Framework
    • Roles : Product Owner, Scrum Master, Team
    • Ceremonies : Spring planning, Spring review, Sprint retrospective, Daily Scrum Meeting
    • Artifacts : Product backlog, Spring backlog, Burndown Chart
  • What is Scrum?
    • The name Scrum
    • Prioritized activities in a product backlog
    • Sprint in 30 calendar days (22 working days)‏
    • Self-organized, crossfunctional teams, 7 +/- 2
    • Daily stand-up
  • Scrum Flow
  • Scrum Roles
    • Product owner
    • Scrum master
    • Scrum team (5-9 people)‏
  • Product Owner
    • Maintaining the product backlog
          • Prioritizing
          • Presentation of product backlog to the team
    • Participation in sprint planning and sprint presentation
    • Responsible for product vision, ROI and release management
    • Can follow sprint via Daily Scrum, Burndown chart and via Scrum Master
  • Scrum Team
    • Teams of 7 +/- 2 participants
    • Crossfunctional
    • Best experts in the domain area
    • Maintaining the sprint backlog
    • Self-organizing
      • Team decides who shall do what
      • They inspect and adapt as the sprint goes along
    • Have most of the powers during a sprint
  • Scrum Master
    • Responsible for the process
    • Responsible for optimizing the Scrum environment
    • Responsible for Daily Scrum
    • Runs Sprint Retrospective
    • Coach
  • Spring Planning / Workshop
    • 1. Product Owner, Team, and other Stakeholders talk through Product Backlog Items and prioritization.
    • 2. Team determines how much time it has available to commit during the Sprint
    • 3 . Team selects as much of the Product Backlog as it can commit to deliver by the end of the Sprint, and turns it into a plan
      • - Validates commitment by breaking down into tasks with time estimates
      • - Team decides who will do what, when; thinks through sequencing, dependencies, possible task trades, and so forth.
  • Daily Scrum
    • Daily Scrum must not last more than 15 minutes
    • Held same place, same time, every working day
    • Participants can not be late
    • Anybody can come, but only the team and Scrum Master can speak
    • 3 questions answered by each team member
        • What did I do yesterday?
        • What am I going to do today?
        • What are my impediments?
  • Sprint presentation
    • Team presents work done in the sprint.
        • What have we achieved?
        • Should show finished functionality.
        • What is missing.
        • Maximum of 2 hours for presentation.
  • Sprint Retrospective
    • Run by Scrum Master
    • Team reflects on the sprint
        • What went well?
        • What did not go so well?
        • How can we improve?
  • Who is using Scrum?
    • US Federal Reserve
    • SAP
    • H P
    • Motorola
    • TransUnion
    • Google
    • Microsoft
    • Yahoo
    • Sun
    • Siemens
    • Nokia
    • Philips
    • BBC
    • IBM
  • Scrum Core Ideas
      • Everything is time-boxed.
      • Inspect & Adapt.
      • You can-not plan everything.
      • Fail early.
      • Shippable product at the end of every iteration/sprint.
      • Iterative development.
      • Cross-functional teams.
      • Self-organizing teams.
      • Team owns the sprint backlog.
  • Common Problems
    • Creating cross-functional teams.
    • Thinking in time-boxed manner – requires discipline.
    • Shifting from the paradigm of TL/PM- ownership to team-ownership.
    • Making use of Sprint retrospective effectively.
  • Questions!
  • Feedback
      • [email_address]
  • License
      • This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License