Scrum in Action.

Slides:



Advertisements
Similar presentations
practicing agile development since 2002 csm x 4, cspo x 2 contracted ken schwaber taught agile to 100s agile alliance, acm, ieee mike cohn disciple delivered.
Advertisements

SCRUM basics Julie Rudder & Claire Stewart. What is scrum (Claire) Scrum roles (Claire) Scrum rhythms and processes (Claire) How to write stories (Julie)
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.
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.
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
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Intro to Scrum. What is Scrum? An answer to traditional “fixed cost / strict requirements” contracts which had very high rates of failure Recognizes the.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
Scrum 1.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Agile development By Sam Chamberlain. First a bit of history..
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
What is Scrum Process? Where is it used? How is it better?
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.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
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 2800.
SCRUM.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
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.
Software Quality Assurance Chip Ene, February 14, 2015.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
CMPS 116 Software Design Project. Introduction Instructor: Dr. Huahai Yang IBM Research – Almaden Former SUNY Albany Programming.
Scrum Process Proposal 1/16/09. User Stories Scrum Process Proposal.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Agile Processes: Scrum
Approaches to Systems Development
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Project Management
Agile Project Management Methodology Scrum Overview
Project Management with VSTS
Scrum.
Scrum and TargetProcess
SCRUM.
Agile Training – Agile Overview
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
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 
Chapter 3: The Project Management Process Groups: A Case Study
Approaches to Systems Development
Burn Down charts for Project Management
As implemented for CSM Field Session
Project Management and the Agile Manifesto
Scrum MODULE 3 – Part 3.
Burn Down charts for Project Management
Johanna Rothman Agile Team Measurements Chapter 12
Summarizing Our Models to Date
Scrum Overview.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
© University of Liverpool
Introduction to Agile Blue Ocean Workshops.
Scrum Science NGSS: Engineering, Technology, Applications of Science
Adjective: Able to move quickly and easily. Principles and Values
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/Kanban Overview
Presentation transcript:

Scrum in Action

Outline Models to Date Scrum in Action Effort Estimation Writing User Stories Writing Accepteance Criteria Use Cases vs User Stories Scrum Reviewed The Process The Roles The Artifacts The Meetings Effort Estimation Managing the Sprint Task Board Burn Down Chart Story Map

Analysis – Requirements Model Traditional Analysis Models Data Flow Diagrams ERD Object-Oriented Analysis Models - UML Use Case Diagram Domain Class Diagram Use Case Descriptions Activity Diagrams

User Story (def) a high-level description of a requirement (i.e. functionality) that is valuable to a user or product owner of the software product. User Role – who? Goal – what? functionality/feature Reason – why? value adding As a sales rep I want to view a list of customers so that I can pick one to contact.

Acceptance Criteria Acceptance criteria provide clarity as to the expectation. Contains 3 to 5 functional criteria regarding the user story what the user must be able to do what the user must not be able to do what the system must do User Story Acceptance Criteria As a sales rep, I want to view a list of customers so that I can pick one to contact. Display all customer info by customer ID in tabular form. Include filtering & sorting. Show total records & total visible records. Accessible from the main navigation menu.

Use Cases vs User Stories User Story As a sales rep, I want to view a list of customers so that I can pick one to contact. Customer View Customer List As a doctor, I want to view a patient’s prescriptions so that I can look for drug to drug interactions. Doctor View Patient Prescriptions

Use Cases vs User Stories – Describing Each User Story As a sales rep, I want to view a list of customers so that I can pick one to contact. View Customer List Customer Use Case Description Acceptance Criteria Display all customer info by customer ID in tabular form. Include filtering & sorting. Show total records & total visible records. Accessible from the main navigation menu.

Scrum Reviewed – the Process An iterative and incremental agile software development methodology. Frequent releases in short development cycles: 2 to 4-week sprints Product Backlog Sprint Backlog Increment Sprint Execution Sprint Review (“Demo”) Sprint Planning Sprint Retrospective Daily Scrum (“Stand-up”) + Stakeholders Task Board Burn Down Chart

Scrum Reviewed – the Artifacts Product Backlog Product Owner Prioritized List of Product Backlog Items (PBIs) PBIs are written as user stories and will have: Acceptance Criteria Story Points/Effort Estimated – by dev team Increment Potentially Shippable Product or Potentially Deployable Product Product Owner decides when to release Managing Scrum Task Board For each item in the Sprint Backlog, list & classify all tasks: To Do, In Progress, Done Sprint Burndown Chart Shows amount of work remaining in one sprint Story Maps Organizaing user stories Sprint Backlog Development Team List of PBIs committed to Includes the Tasks for each PBI

Scrum Reviewed – the Roles Product Owner client stakeholder who controls the Product Backlog Scrum Master a facilitator removes impediments, resolves issues Development Team 5-9 members Cross-functional skills “the developers” self-organizing teams complete control over organization & work processes They decide what goes in a Sprint

Scrum Reviewed – the Meetings Sprint Planning 8 hours - Creating the Sprint Backlog Part I: Product Owner presents the desired User Stories & the acceptance criteria for each story. Part II: Dev Team identifies tasks for each story; creates time estimates per task; finalizes the user stories they can commit to. Dev Team gets to say if there are details lacking in the user stories & cannot commit to certain stories Attended by: Product Owner, Dev Team, Scrum Master Daily Scrum (“Stand-Up”) 15 mins daily – Status update w/in dev team Yesterday, Today, Barriers Attended by: Development Team, Scrum Master Sprint Review (“Demo”) 4 hours - inspect & adapt the product; add new items to product backlog Attended by: Product Owner, Dev Team, Scrum Master PLUS: stakeholders Sprint Retrospective 3-hours - Process improvement lessons learned, successes & failure Attended by: Scrum Master, Dev Team

Scrum Reviewed – Additional Meetings Backlog Refinement – “Grooming” Refining the next items on the product backlog to prepare for the next sprint(s). It includes: Clarifying backlog items Reducing Epics into smaller items Determining dependencies Task can be done during a Sprint Planning Meeting but many prefer to do this in a separate meeting (e.g. toward the end of a sprint). Epic - a large Backlog item An Epic is a feature that is too broad/complex to be completed in 1 sprint and should be split into multiple stories.

Managing Scrum: Effort Estimation – Story Points Fibonacci Sequence: 1, 2, 3, 5, 8, 13 - The sum of the 2 numbers to the left. T-Shirt Sizing: S, M, L, XL 0 1 1 2 3 5 8 13 21 34 User Story A Assume: User Story B is about half the difficulty of User Story A. With Fibonacci, you will never see half of any number! It forces you to think! Is this user story a little more difficult than half (i.e. 5)?, or Is it a little less difficult than half (i.e. 3)?

Managing Scrum: Taskboard A quick visual way for everyone to see how the project is going. It is the focal point during the Daily Scrum. Task Board User Story To Do In Progress Done As a Sales Rep, I want to view a list of customers so that I can pick one to contact. As a Sales Rep, I need to maintain client data & locations so that we can properly determine their product needs based on their profile.

User Story To Do In Progress Done Task Board User Story To Do In Progress Done As a Sales Rep, I want to view a list of customers so that I can pick one to contact. As a Sales Rep, I need to maintain client data & locations so that we can properly determine their product needs based on their profile. 4. Design the UIs 2. Modify the Domain CD 1.Review the User Story details 5. Test the UIs 3. Create a sketch of the UIs 3. Create a sketch of the UIs 2. Modify the Domain CD 1.Review the User Story details 5. Test the UIs 4. Design the UIs

Managing Scrum: Burndown Chart Sprint Burndown Chart Assess how much work has been completed Used by Scrum Masters at the Daily Scrum & Sprint Retrospective meetings Story Points

Managing Scrum: Story Map Useful when we have a lot of user stories and we need to understand how to progress through them.