Introduction to SCRUMBy Sriram Srinivasanwww.iamsriram.com
What is SCRUMSCRUM TimelinePeopleArtifactsProcess
What is SCRUM?SCRUM is an agile methodology for developing software. The term is named for a  formation in rugby, which is used to restart the game after an event that  causes play to stop, such as an infringement.
SCRUM Timeline1986 -  Hirotaka Takeuchi and Ikujiro Nonaka described a new holistic approach for product  development1991 - DeGrace and Stahl, in “Wicked Problems, Righteous Solutions,” referred to this approach as Scrum, a rugby term mentioned in the ‘article by Takeuchi and Nonaka.1995 -  Sutherland and Schwaber jointly presented a paper describing Scrum at OOPSLA ’95 in Austin, TX, its first public appearance.2001 - Schwaber teamed up with Mike Beedle to describe the method in the book “Agile Software Development with Scrum.”Source – http://en.wikipedia.org/wiki/Scrum_%28development%29
People
Product Owner is responsible for managing the Product Backlog and represents stakeholders in the project.
Stakeholder is someonewith an interest in the outcome of the project.
Team - A group of people that is responsible for managing itself to develop software
SCRUM MASTER  is responsible for making sure SCRUM is correctly implemented and the goal of using SCRUM is achieved.
Artifacts
Product Backlog - List of project requirements with estimates. This  will change due to business andtechnology changes
Product Backlog Items  areFunctional & Nonfunctionalrequirements  and issues,which are prioritized inorder of importance
Sprint Backlog - A list of tasks that defines ateam’s work for a Sprint.
Sprint Backlog Task is one of the task team needs to execute to turn product backlog into working functionality
Process
Time box is a period of time in which a planned event or meeting occurs and cannot be exceeded.
Increment – Productfunctionality developedin various stages.Each iteration results in incremental development of functionality
Iteration is a cyclewithin a project.
Sprint Planning is a one-day meeting timeboxed to 8 hours that initiates every Sprint.
Sprint - A 30 calendar day time box, where teamdevelops product backlog items selected into a shippable product.
Burn Down Chart  work remaining across time in asprint, a release, or a product.
Done – Work completed and agreed by all stake holders and conforms to organization processes , conventions and guidelinesImage - http://www.sxc.hu/profile/svilen001
Daily Scrum Meeting is a daily status meeting held for a short period of time where, team will discuss about the work completed and planned plus let scrum master know about any impediments that needs to be removed.
Sprint Review Meeting  a short meeting where completed product is demonstrated to and reviewed by stakeholders
Sprint Retrospective Meeting is a short meeting scheduled by the scrum master where just concluded sprint will be reviewed and learning‘s noted to be implemented in the next sprint.
SCRUM helps in achieving
Hurray! Finally this presentation is over Images by www.sxc.huwww.dreamstime.com
About SriramSriram has 15 years of information technology industry experience, where he has played various roles in delivering multimillion dollar projects. You can reach him at: Mobile 	: 8122597519Mail   	:ssram37@gmail.comwww 	: www.iamsriram.comTwitter	: www.twitter.com/sriramsLinkedIn	: www.linkedin.com/in/ssramFB                : www.facebook.com/ssram37
Introduction to Scrum

Introduction to Scrum

  • 1.
    Introduction to SCRUMBySriram Srinivasanwww.iamsriram.com
  • 2.
    What is SCRUMSCRUMTimelinePeopleArtifactsProcess
  • 3.
    What is SCRUM?SCRUMis an agile methodology for developing software. The term is named for a formation in rugby, which is used to restart the game after an event that causes play to stop, such as an infringement.
  • 4.
    SCRUM Timeline1986 - Hirotaka Takeuchi and Ikujiro Nonaka described a new holistic approach for product development1991 - DeGrace and Stahl, in “Wicked Problems, Righteous Solutions,” referred to this approach as Scrum, a rugby term mentioned in the ‘article by Takeuchi and Nonaka.1995 - Sutherland and Schwaber jointly presented a paper describing Scrum at OOPSLA ’95 in Austin, TX, its first public appearance.2001 - Schwaber teamed up with Mike Beedle to describe the method in the book “Agile Software Development with Scrum.”Source – http://en.wikipedia.org/wiki/Scrum_%28development%29
  • 5.
  • 6.
    Product Owner isresponsible for managing the Product Backlog and represents stakeholders in the project.
  • 7.
    Stakeholder is someonewithan interest in the outcome of the project.
  • 8.
    Team - Agroup of people that is responsible for managing itself to develop software
  • 9.
    SCRUM MASTER is responsible for making sure SCRUM is correctly implemented and the goal of using SCRUM is achieved.
  • 10.
  • 11.
    Product Backlog -List of project requirements with estimates. This will change due to business andtechnology changes
  • 12.
    Product Backlog Items areFunctional & Nonfunctionalrequirements and issues,which are prioritized inorder of importance
  • 13.
    Sprint Backlog -A list of tasks that defines ateam’s work for a Sprint.
  • 14.
    Sprint Backlog Taskis one of the task team needs to execute to turn product backlog into working functionality
  • 15.
  • 16.
    Time box isa period of time in which a planned event or meeting occurs and cannot be exceeded.
  • 17.
    Increment – Productfunctionalitydevelopedin various stages.Each iteration results in incremental development of functionality
  • 18.
    Iteration is acyclewithin a project.
  • 19.
    Sprint Planning isa one-day meeting timeboxed to 8 hours that initiates every Sprint.
  • 20.
    Sprint - A30 calendar day time box, where teamdevelops product backlog items selected into a shippable product.
  • 21.
    Burn Down Chart work remaining across time in asprint, a release, or a product.
  • 22.
    Done – Workcompleted and agreed by all stake holders and conforms to organization processes , conventions and guidelinesImage - http://www.sxc.hu/profile/svilen001
  • 23.
    Daily Scrum Meetingis a daily status meeting held for a short period of time where, team will discuss about the work completed and planned plus let scrum master know about any impediments that needs to be removed.
  • 24.
    Sprint Review Meeting a short meeting where completed product is demonstrated to and reviewed by stakeholders
  • 25.
    Sprint Retrospective Meetingis a short meeting scheduled by the scrum master where just concluded sprint will be reviewed and learning‘s noted to be implemented in the next sprint.
  • 26.
    SCRUM helps inachieving
  • 27.
    Hurray! Finally thispresentation is over Images by www.sxc.huwww.dreamstime.com
  • 28.
    About SriramSriram has15 years of information technology industry experience, where he has played various roles in delivering multimillion dollar projects. You can reach him at: Mobile : 8122597519Mail :ssram37@gmail.comwww : www.iamsriram.comTwitter : www.twitter.com/sriramsLinkedIn : www.linkedin.com/in/ssramFB : www.facebook.com/ssram37