Scrum Overview.

Slides:

Advertisements

Similar presentations

Scrum in 10 slides.

Advertisements

ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.

Agile and Scrum: Executive Summary June 2, 2011 Bob Schommer, CSP, PMP, MCTS Senior Project Manager Skyline Technologies, Inc.

What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.

Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.

Copyright © 2012 by Mark J. Sebern Product Owner & ScrumMaster Who are these people, anyway?

Slide title 70 pt CAPITALS Slide subtitle minimum 30 pt Scrum Training: The Scrum Guide Explained for the Self-Organizing Team Glen Wang

ECE44x SCRUM Overview slides adapted from Marty Stepp

Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.

Copyright © by Mark J. Sebern Software Engineering Process I SE Product backlog, estimation, velocity.

Scrum in 10 slides by Pierre Mengal – Scrum In Ten Slides v1.1 is licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported.

Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.

Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.

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.

Dr. Rob Hasker. Logistics  Class roster, attendance policy  Book, Schedule, policies, grading  Course web site  Prereq check:  SE 2800, Software.

What is Scrum Process? Where is it used? How is it better?

10/8/2008Clarity PLC Fall WebConference This slide copyright Jeffrey A. Bloom Tips and Techniques Leveraging Clarity’s Notes Facility & SCRUM in.

Software Engineering- Scrum 徐瑋 Alen 林芳瑜 Flora 1.

Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint Execution.

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.

Copyright © 2012 by Mark J. Sebern Scrum Overview (from

Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.

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 © by Mark J. Sebern Software Engineering Process I SE Sprint review and retrospective.

Agile Information Management Development. Agile Project Management Characteristics  Acceptance and even welcome of changing requirements  Incremental.

Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.

Dr. Rob Hasker. A new process: YOGA  10 Principles 1. Ignore the past, only look ahead 2. Be artists, free to create 3. Meditate on code each day: what.

Copyright © 2012 by Mark J. Sebern Sprints Sprint planning Sprint execution.

Using Scrum to Improve Teamwork, Communication, Quality and Speed

Lecture 5 17/9/15. What is Scrum? Scrum is one of the leading agile software development processes Agile framework for completing complex projects. Originally.

The Agile Manifesto Some thought starters for Ogilvy on how to work with Agile and SCRUM approaches to managing projects.

Copyright © 2013 by Mark J. Sebern Sprint Review & Retrospective Two “end of sprint” activities Sprint review Sprint retrospective How do they differ?

Introduction to Agile. Introduction Who is this guy?

Agile CRM Applying the Scrum Methodology for Deployment Neil Benson.

Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!

Using Scrum to Improve Teamwork, Communication, Quality and Speed.

Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.

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

Business Intelligence in Classroom WHY:.  Purpose – knowledge to make an informed career decision  Process – Use Scrum method of project management.

Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.

Project Management with VSTS

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

Spring 2013 Advising Starts this week.

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.

Product Backlog List of things that needs to be done to make the product come into existence

Impact of Agile Methodology on Software Architecture

CSCE 741 Software Process Lecture 04 Availability

Scrum MODULE 3 – Part 3.

Summarizing Our Models to Date

SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES

© University of Liverpool

CSCE 741 Software Process Lecture 04 Availability

Agile practices for documentation teams

Scrum in 10 slides by Pierre Mengal – Scrum In Ten Slides v2.0 is licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported.

Scrum Science NGSS: Engineering, Technology, Applications of Science

Taking it to the next level

Scrum in Action.

Scrum: Daily Stand Up Meeting

Presentation transcript:

Scrum Overview

Scrum Overview (simplified diagram) Review/retrospective (from http://en.wikipedia.org/wiki/File:Scrum_process.svg)

Scrum Activities Sprint planning Sprint execution Sprint retrospective Daily scrum Sprint planning Sprint execution Sprint retrospective Sprint review

Scrum Roles Who’s the boss? Who are these people? Product owner ScrumMaster Development team Who’s the boss? Who? How many?

Scrum Roles Who are these people? Product owner ScrumMaster Guiding team on creating, following process; removing impediments Scrum Roles Who are these people? Product owner ScrumMaster Development team What problems will we have in implementing Scrum roles in this course? What will be developed, and in what order 5-9 people: determines how to deliver what product owner requests.

Product Backlog Items (PBIs) What goes in here? Who manages these items? What is “grooming”? How are the PBIs ordered? How are the PBIs measured? Are they the same size?

Sprints What is a sprint? How long does one last? The textbook author indicates 1-4 weeks, but MSOE affiliates use a 2-week minimum

Copyright © 2012-2014 Mark J. Sebern Sprint Planning What are these components? How does planning work? Copyright © 2012-2014 Mark J. Sebern

PBIs vs Tasks Measurement units (story points, hours)? Mapping between PBIs and tasks? Types of tasks and definition of done Design, code, review, test, etc.

Checkpoint

Sprint Execution (1) Doing the work! Performing the identified tasks Tracking progress (more later . . .) Adapting to emergent knowledge (Re)allocating team effort as needed

Sprint Execution (2) What is the daily scrum? What are the three questions?

Sprint Execution (2) What is the daily scrum? "Stand-up" meeting (< 15 minutes) 3 questions answered by each member: What have I accomplished (since last)? What do I plan to have done (by next)? What is keeping me from progressing?

Sprint Execution (3) What is the potentially-shippable product? What’s the purpose/motivation? What is “done”? How about “done done”?

Sprint Execution (4): Inspect and Adapt Sprint review Focus on the product (includes feedback) Sprint retrospective Focus on process (process/practice improvement)

Review/retrospective Scrum process Roles Product owner, Scrummaster, Developers Product backlog, sprint backlog Sprint execution Potentially shippable product increment – done work Review Retrospective