Going the Scrum Way
Upcoming SlideShare
Loading in...5
×
 

Going the Scrum Way

on

  • 243 views

 

Statistics

Views

Total Views
243
Views on SlideShare
243
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

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

    Going the Scrum Way Going the Scrum Way Presentation Transcript

    • Scrum Methodology Going the ScrumWay
    • Introduction • Scrum is an agile software development framework for managing projects. • Scrum Methodology is – Iterative – Incremental • Scrum focuses on project management process which is more – Flexible – Accountable vikashmishra001@gmail.com http://mishravikash.wordpress.com/ http://in.linkedin.com/in/mishravikash
    • Why Scrum? • Scrum gives priority to Individuals and interactions over processes and tools • In Scrum working software is given more importance over comprehensive documentation. • In Scrum customer satisfaction takes precedence over monetary gains. • Changes in requirements are accepted even in late stages of product lifecycle. vikashmishra001@gmail.com http://mishravikash.wordpress.com/ http://in.linkedin.com/in/mishravikash
    • Scrum Methodology • Scrum introduced the idea of “empirical process control” – Scrum measures actual progress of project to plan and schedule release. • Scrum divides work in Sprint. • There are set of roles, responsibilities, and meetings that never change. – Product Owner – Scrum Master – Team Member vikashmishra001@gmail.com http://mishravikash.wordpress.com/ http://in.linkedin.com/in/mishravikash
    • Sprint • A Sprint is basic and essential subsidiary of Scrum Methodology. • Sprint length varies from 3 to 4 weeks. • Team decides the amount of work which needs to be accomplished in Sprint cycle. • Goal andTimeline of Spring in not altered. vikashmishra001@gmail.com http://mishravikash.wordpress.com/ http://in.linkedin.com/in/mishravikash
    • Product Owner • He/she is the soul of project. • Interacts with customers to gather requirements. • Communicates the vision of the product to the team members. • Prepares and prioritizes product backlog. • Micro-manages the project. vikashmishra001@gmail.com http://mishravikash.wordpress.com/ http://in.linkedin.com/in/mishravikash
    • Scrum Master • Act as bridge between Product Owner andTeam. • Shields the team from distractions and motivate the members to achieve the goals of the sprint. • Act as a mentor and helps team members to overcome the hurdle. • Responsible for improving productivity of team. • Makes sure that Sprint cycle meets its deadline. vikashmishra001@gmail.com http://mishravikash.wordpress.com/ http://in.linkedin.com/in/mishravikash
    • Team Members • Comprises of all people of various skill set required to accomplish the goal. • Responsible for building the product which is good to be shipped. • There is no hierarchy and members are self-organizing. • Team determines how it will accomplish the work to be completed vikashmishra001@gmail.com http://mishravikash.wordpress.com/ http://in.linkedin.com/in/mishravikash
    • Building Products using Scrum • Product Owner prepares Product Backlog. • Sprint planning meeting at the start of sprint cycle to decide way ahead. • Daily stand-up meeting(10-15 minutes) – Assess progress – Eliminate obstacles – Pick Items from Product Backlog • Sprint Review is performed at the end to measure success and decided future course of action. vikashmishra001@gmail.com http://mishravikash.wordpress.com/ http://in.linkedin.com/in/mishravikash