Release retrospective

Slides:



Advertisements
Similar presentations
The Road to Agile From the Bottom Up Kevin Malley Tracey Clark 1 March 20 th, 2013 SWOQG.
Advertisements

Information Technologies Page 1 Information Technologies Page 1 Information Technologies Page 1 Information Technologies Page 1Information Technologies.
An Agile Retrospective Clinton Keith Overview Retrospective format What works (clear wins)? What doesn’t work so well? What do we need to start doing?
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
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.
When is Agile the Best Project Management Method? Lana Tylka.
Release and Iteration Planning September 13, 2008.
Stephen Chief Strategy Officer Telerik
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
Agile Project Management. An Informed Decision It is not a snap decision whether to use an agile approach or not, just like flying or driving somewhere.
Creative Disruption: A Core Systems Strategy Workshop November 3, 2011.
Agile Information Management Development. Agile Project Management Characteristics  Acceptance and even welcome of changing requirements  Incremental.
Managing Agile, Waterfall and Hybrid projects within the Portfolio
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
© Workroom Productions Slide 1 Adventures in Session-based Testing James Lyndsay Workroom Productions
 Overview of agile project management  Key concepts and terminology  Available resources and tools  Applicability of agile project management to different.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Copyright © Curt Hill Scrum Software Development Paradigms What is a Scrum?
Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka.
Agile Methodology and Scrum
Change Request Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
AGILE SCRUM METHODOLOGY
The Strategic Role of Information Development in Continuous Delivery
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Fundamentals of Information Systems, Sixth Edition
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Valuable Project Management Tools and Techniques
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Agile Scrum Management
Principles of Information Systems Eighth Edition
Spring 2013 Advising Starts this week.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
September 20, 2017 Agile Techniques Workshop Susan Futey
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Project Review Team name
Mike Cohn - Agile Estimating and Planning
By: By: Agile Scrum Master Online Training.
Impact of Agile Methodology on Software Architecture
Chapter 3: The Project Management Process Groups: A Case Study
Scrum MODULE 3 – Part 3.
WEBINAR: Becoming Agile In Software Testing: The Government Edition
Teaching slides Chapter 3.
Johanna Rothman Agile Team Measurements Chapter 12
How to Successfully Implement an Agile Project
Practical ways to measure and track the progress of Agile projects Ensuring that key data is visible in an Agile environment Dave Browett – March 2013.
Johanna Rothman Report Your Project State Chapter 14
[Project Name] Project Report
Project Ideation Agile Down-to-Earth © 2016.
IS&T Project Reviews September 9, 2004.
Agile Philly: Estimating Vs Forecasting Using a Monte Carlo Tool
Agile practices for documentation teams
[Project Name] Project Report
<Project Name> Milestone Summary Report
The Software Testing Life Cycle
Software Development In Agile
SDLC (Software Development Life Cycle)
Executive Project Kickoff
MODULE 1 Introduction WELCOME to the ROOT CAUSE ANALYSIS WORKSHOP
Are you measuring what really counts?
Speaker’s Name, SAP Month 00, 2017
What makes a Good Agile Team
AgilityHealth® ScrumMaster Training
Presentation transcript:

Release retrospective Presentation subtitle is Open Sans Regular 14pt, one line maximum 00 Month 0000 | Firstname Lastname

Release retrospective vs Sprint retrospective The Release and Sprint retrospectives have many similarities including techniques and the ultimate goal of continuous improvement which is so important to Agile. However there are some differences …

Release retrospective vs Sprint retrospective Focus on the entire release (multiple sprints) with goal to improve next release Focus on current sprint with goal to improve future sprints

Release retrospective vs Sprint retrospective Emphasis on risk ID specifically with respect to strategic objectives and product quality (refer to slide on inspection points) Emphasis on process improvements

Release retrospective vs Sprint retrospective More formal, greater prep required Somewhat informal and casual, less prep required

Release retrospective vs Sprint retrospective Fact and data driven Emotional/feeling points may be addressed

Release retrospective vs Sprint retrospective Broader participation - team, management, & stakeholders Limited participation - team only

Release retrospective vs Sprint retrospective Duration – typically, two hours depending on release length, format, and agenda Duration – typically, one hour

Some common inspection points for release retro Product quality Current status of the projects Number of escaped defects Planned features versus delivered features Whether the features delivered were in order of priority The number of features developed that were actually accepted The number of features delivered that are actually used by the customer The number of issues reported by the customer and the length of time we took to fix those issues Whether the release date was extended and, if so, why Whether we delivered all the scope planned for the release The number of defects getting generated on previous enhancements Whether we are taking interim customer feedback New technology initiatives Infrastructure issues causing release delays Performance improvement initiatives Any new tools to be introduced The optimization that can be done at various levels How we measured the data and scope of improvement What strategies were highly effective Etc. Source: https://www.scrumalliance.org/community/articles/2014/september/the-significance-of-release-retrospectives

Overview and techniques for retrospectives For a general overview and some common techniques that are useful in running scrum retrospectives, please refer to: http://pdn.pega.com/documents/scrum-basics-retrospectives