Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace:
prateek_singh_-_retrospective_moving_from_a_subjective_to_objective_world

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
prateek_singh_-_retrospective_moving_from_a_subjective_to_objective_world [2015/08/20 07:22] – external edit 127.0.0.1prateek_singh_-_retrospective_moving_from_a_subjective_to_objective_world [2020/06/02 14:21] (current) – external edit 127.0.0.1
Line 1: Line 1:
-Title: PrateekSingh-RetrospectiveMovingFromaSubjectiveToObjectiveWorld Timestamp: 2015-08-05 21:03:18 +0000 Created: 2015-08-04 17:54:57 +0000 Last Accessed: 2015-08-04 17:54:57 +0000 Times Accessed: 0 Tags: Metadata: gpslongitude=-77.017526,gpslatitude=38.780525 # Premise+====== Prateek Singh - Retrospective: Moving From a Subjective to Objective World ====== 
 + 
 +====== Premise ======
  
 Traditionally Agile teams run retrospectives to facilitate learning, development, collaboration and improvement of the team. Teams have tried multiple different formats to get the right outcomes. Issues of all sorts seem to pop up many times - lack of participation, finger pointing, irrelevant topics, lack of prioritization of issues. Are these or similar problems hindering the effectiveness of your retrospectives? What format of retrospective can best promote the culture of collective vision and collaboration in your team? How can we get the best outcomes fro the team by having the most collaborative retrospectives? Recently numerous teams have moved to objective retrospectives from a completely subjective form of retrospective as a solution. Objective retrospectives use the team’s data to conduct the retrospective, to create talking points and to see the effects of action items taken by the team since the last retrospective. We will go over examples of patterns seen in metrics and graphs to assist with identification of talking points and examples of resultant action items. We will also do a deeper dive into facilitation of techniques for facilitating both subjective and objective retrospectives. We will also talk through figuring out the best format to choose for Traditionally Agile teams run retrospectives to facilitate learning, development, collaboration and improvement of the team. Teams have tried multiple different formats to get the right outcomes. Issues of all sorts seem to pop up many times - lack of participation, finger pointing, irrelevant topics, lack of prioritization of issues. Are these or similar problems hindering the effectiveness of your retrospectives? What format of retrospective can best promote the culture of collective vision and collaboration in your team? How can we get the best outcomes fro the team by having the most collaborative retrospectives? Recently numerous teams have moved to objective retrospectives from a completely subjective form of retrospective as a solution. Objective retrospectives use the team’s data to conduct the retrospective, to create talking points and to see the effects of action items taken by the team since the last retrospective. We will go over examples of patterns seen in metrics and graphs to assist with identification of talking points and examples of resultant action items. We will also do a deeper dive into facilitation of techniques for facilitating both subjective and objective retrospectives. We will also talk through figuring out the best format to choose for
Line 12: Line 14:
 ====== Action / Learning ====== ====== Action / Learning ======
  
-  * write about this in comparison to Scott Downey+  * Write about this in comparison to Scott Downey? This is another approach to making sure we have the data we need for retrospectives.
  
 ====== Presentation ====== ====== Presentation ======
  
-Attachments: Retrospectives.pdf+Attachments: {{:retrospectives.pdf|Retrospectives.pdf}}
  
 Speakers Prateek Singh - Manager of Software Engineering, Ultimate Software @singhpr Speakers Prateek Singh - Manager of Software Engineering, Ultimate Software @singhpr
Line 82: Line 84:
 3 types of retrospective Autocratic - sm says what we work on - not good except at beginning Guided - elicit tops, and add in topics Team centric - 3 types of retrospective Autocratic - sm says what we work on - not good except at beginning Guided - elicit tops, and add in topics Team centric -
  
 +{{tag>Conference Collaboration Retrospective}}
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/prateek_singh_-_retrospective_moving_from_a_subjective_to_objective_world.txt · Last modified: 2020/06/02 14:21 by 127.0.0.1