Going the Scrum Way

199
-1

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
199
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Going the Scrum Way

  1. 1. Scrum Methodology Going the ScrumWay
  2. 2. 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
  3. 3. 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
  4. 4. 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
  5. 5. 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
  6. 6. 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
  7. 7. 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
  8. 8. 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
  9. 9. 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
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×