The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours 1 - 4 weeks.

Slides:



Advertisements
Similar presentations
Scrum in 10 slides.
Advertisements

Engineering Bernd Fischer RW344: Software Design ▬ ▬ ▬▬ ▬ ▬
ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
Lecture 3 CS171: Game Design Studio 1I UC Santa Cruz School of Engineering 12 January.
An Introduction to Agile SCRUM Methodology
Dept. of Computer Science & Engineering, The Chinese University of Hong Kong Agile Software Development CHEN Xinyu
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Agile Development.
Presentation from: See Also: scrumreferencecard.com/ScrumReferenceCard.pdf.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
Scrum introduction XP Days Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions.
Scrum 1.
An Introduction to Scrum
An Introduction to Agile SCRUM Methodology
Managing a Project Using an Agile Approach and the PMBOK® Guide
Scrum Agile Methodology
Introduction to Agile.
Agile Design and SCRUM Brent M. Dingle, Ph.D. “For the last few centuries, … science has been attempting to break matter down into ever smaller bits, in.
1 Agile Methodology & Programming Ric Holt July 2009.
What is Scrum Process? Where is it used? How is it better?
1 SCRUM 22/02/2009 By Siemen Bastiaens >>
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Release and Iteration Planning September 13, 2008.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
Stephen Chief Strategy Officer Telerik
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
1 An Introduction to Scrum. 2 Square One Consulting We’re losing the relay race Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development.
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?
Agile Information Management Development. Agile Project Management Characteristics  Acceptance and even welcome of changing requirements  Incremental.
Presentation from: See Also: scrumreferencecard.com/ScrumReferenceCard.pdf.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
SCRUM.
The Agile Manifesto Some thought starters for Ogilvy on how to work with Agile and SCRUM approaches to managing projects.
SCRUM. WITH ACKNOWLEDGEMENT TO MIKE COHN FROM MOUNTAIN GOAT SOFTWARE, LLC.
Introduction to Agile. Introduction Who is this guy?
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
A Brief Conversation on Agile and the Scrum Framework
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
CMPS 116 Software Design Project. Introduction Instructor: Dr. Huahai Yang IBM Research – Almaden Former SUNY Albany Programming.
Scuola Politecnica Dipartimento DITEN Università degli Studi di Genova An Introduction to Scrum and XP Prof. Riccardo Berta.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum.
Agile Training Day 2 November 17, 2015.
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
By: By: Agile Scrum Master Online Training.
The Agile Product Owner
Scrum MODULE 3 – Part 3.
Summarizing Our Models to Date
Scrum Overview.
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
© University of Liverpool
Adjective: Able to move quickly and easily. Principles and Values
Scrum in Action.
Presentation transcript:

The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks

Discussion today Presents an alternative way of developing products Provides insight into Scrum values Demonstrates Scrum as a simple framework

Scrum Overview

What is Scrum? The most unique aspect of rugby is the scrum, pictured below, which is used to restart play following minor infractions during the match. Scrum -- a group responsible for picking up the ball and moving it forward.

3 pillars of Scrum

Scrum Values 6 CommitmentOpenness Courage Focus Respect

The Traditional Way orem ipsum dolor sit amet, co nse ctetur Milestones and Tasks 7

The Traditional Way 8

The SCRUM Way orem ipsum dolor sit amet, co nse ctetur Product Backlog 9

Involved vs. Committed 10

Involved vs. Committed 11

The Scrum Way orem ipsum dolor sit amet, co nse ctetur Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint N Sprint is 1 – 4 Weeks 12

Traditional SDLC vs Scrum

Source:

Scrum Overview Self Organize and Deliver as a Team 24 hours weeks Product Backlog Sprint Backlog Incremental Solution Delivery Daily Standup Meeting Team Retrospective

The Scrum Framework Events Sprint Planning What are we doing next? Daily Scrum How are we doing today? Sprint Review How did we do? Sprint Retrospective How do we get better? Artifacts Product Backlog What are we doing and in what order? Sprint Backlog What are we doing right now? How will we do it? Burndown Chart How are we doing in this sprint? How we are doing in this release? Roles Product Owner What should we work on and Why? (Vision) Development Team Who will do it and how? ScrumMaster Who will help us do it (Process Facilitator)?

The Core Scrum Team Product Owner Development Team Scrum Master Small enough to remain nimble and Large enough to complete significant work within a Sprint Self-organizing and cross-functional Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback

Product Owner Define the feature of the product Makes scope vs. schedule decisions Responsible for achieving financial goals of the project Prioritize and ranks the product backlog Adjust features and priority every sprint, as needed Accept or reject work results

Development Team Typically 5-9 people Cross-functional QA, Programmers, UI Designers, etc. Members should be full-time May be exceptions (e.g., System Admin, etc.) Teams are self-organizing Membership can change only between sprints

The Scrum Master Responsible for enacting Scrum values and practices Main job is to remove impediments

Product Backlog A list of all desired work for the project Ideally expressed such that each item has value to the users or customers of the product Prioritized by the product owner Team estimates items in Backlog relative to each other using predetermined scale (story points) Product Owner, with the help of the team, will continuously ‘groom’ or ‘review’ the backlog.

Sprints Scrum projects make progress in a series of “sprints” Target duration is 1-4 weeks A constant duration leads to a better rhythm Product is designed, coded, and tested during the sprint Product Backlog

Sprint Planning InputTeam WorkOutput

Burndown charts Primary method of tracking progress A Burndown chart shows how much work is left as of various dates Two types Release burndown Sprint burndown

Release burndown

Daily Scrum meetings Parameters Daily 15-minutes Stand-up Not for problem solving

Daily Scrum Daily, 15 minutes, Commitments in front of peers Everyone Answers 3 Questions What did you do yesterday? 1 1 What will you do today? 2 2 Is anything in your way? 3 3

Sprint Review Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture Participants Customers Management Product Owner Other engineers

Team Retrospective Key mechanism for examining and improving methods and teamwork at the close of every sprint and demo Team Answers 3 Questions What did we do well? 1 1 What didn’t go well? 2 2 What could be improved in the next sprint? What could be improved in the next sprint? 3 3

Inspect and Adapt

Thank You Somnath Ghosh (mobile)

24 hours weeks