Spring 2013 Advising Starts this week.

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.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
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.
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.
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
Scrum 1.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Managing a Project Using an Agile Approach and the PMBOK® Guide
Mai Müür Tallinn  Retrospective as a part of Scrum  The idea of retrospectives  Rules of the game  Impact to IT team  Strenghts and weaknesses.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
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.
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
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
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.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
SCRUM.
End of Sprint Meetings (Ceremonies)
PV213 EIS in Practice: 06 – Development process 1 PV213 Enterprise Information Systems in Practice 06 – Development process.
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?
#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!
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.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
AGILE SCRUM METHODOLOGY
Flight Software Conference 2016
Project Management with VSTS
Scrum.
Scrum and TargetProcess
SCRUM.
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.
SE 3800 Note 7 Planning, Impediments Ch. 3
SE 3800 Note 7 Planning, Impediments Ch. 3
Client Management Managing Client Expectations
Impact of Agile Methodology on Software Architecture
CSCE 741 Software Process Lecture 04 Availability
Scrum MODULE 3 – Part 3.
Summarizing Our Models to Date
Johanna Rothman Know What “Done” Means Chapter 11
Scrum Overview.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
CSCE 741 Software Process Lecture 04 Availability
Agile practices for documentation teams
Sprint Planning April 2018.
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
Scrum in Action.
Agree what we will finish in the sprint
Sprints.
Release retrospective
AgilityHealth® ScrumMaster Training
Driving Successful Projects
Presentation transcript:

Spring 2013 Advising Starts this week

Sprint Review & Retrospective Two “end of sprint” activities Sprint review Sprint retrospective How do they differ?

Review Participants Scrum team Who Role Scrum team Hear product feedback, answer questions regarding the sprint and product increment Internal stakeholders Provide feedback, suggest changes (from what perspective?) Other internal teams Provide area-specific feedback (e.g., sales, legal, other development) and sync work External stakeholders Provide feedback, suggest changes (who exactly? why?)

Review Preparation Sprint review prework Identify participants (specific people) Set the schedule (when, duration) Confirm sprint work is done (DONE)

Review Preparation Sprint review prework Identify participants (specific people) Set the schedule (when, duration) Confirm sprint work is done (DONE) What is the definition of DONE? Who decides? When is the decision made? (at end? JITduring sprint?) Granularity of the decision? (per PBI?)

Review Preparation Sprint review prework Identify participants (specific people) Set the schedule (when, duration) Confirm sprint work is done (DONE) Prepare for demonstration (ceremony?) Decide who does what (facilitator? demo?)

Review Overview Review Sprint backlog items (or sprint goal) Potentially shippable product Groomed product backlog Updated release plan Present sprint goal, PBIs, actual achievements Explain any discrepancies Demonstrate what actually got built What if it cannot be demonstrated? (Really??) Discuss state of the product, future direction of the project Implicit/explicit backlog grooming

Retrospective Participants Who Role Scrum team Reflect on the sprint experience from a process point of view ScrumMaster Lead process discussion, help team focus on fidelity to its own chosen process Product owner Help address issues with requirements, PBI grooming issues, interaction with team Other stakeholders Only if invited by the team; not invited if negative effect on team safety/openness

Retrospective Structure How much time? Location? Facilitator? ScrumMaster Other team member Outsider (other ScrumMaster?) About 1.5 hours for a 2-week sprint, more for longer ones. Meet in team area or elsewhere? Access to data vs environment more conducive to open discussion.

Overview Set atmosphere Focus Exercises (or prep) Objective data Subjective data Insight backlog Retrospective Improvement actions Insight backlog Improved team spirit Focus: general improvement, or is there something specific we need to work on? Exercises: create/mine sprint timeline, brainstorm/group insights (determine ahead or select dynamically) Atmosphere: ground rules for safe/open discussion, active participation Context: Share perspectives to seek common team understanding of what happened, from objective data; agree on event timeline, emotions seismograph [more on following slides] Set atmosphere Share context (common perspective from individual ones) Identify insights Determine actions Close the activity

Insights What worked well, or not? Improvement ideas? Organize insight backlog Cards on wall A B C D E F

Insights What worked well, or not? Improvement ideas? Organize insight backlog Cards on wall B D E F Silent grouping Pre-existing categories? A C

Actions Select insights from new backlog “Dot voting” Consider timeframe for changes Decide on actions Specific task items General changes B D E F Specific: improve infrastructure software, tools General: behavioral, attitudinal A C

Follow Through Sprint tasks Include tasks to implement chosen actions Not a separate “improvement” effort! Integrate into the next sprint’s work Specific: improve infrastructure software, tools General: behavioral, attitudinal

Retrospective Issues Not doing one (or not well) Superficial, not addressing real issues Watch out for the elephant! (safety?) Poor execution: facilitation, blame/complain Too ambitious (or miss ongoing improvements) Lack of follow-through Retrospective should not replace ongoing improvement activity during the sprints.

What Else? What else did you learn about sprint reviews and retrospectives? What questions do you have?