Skip to content

Retrospectives

Andrew Smith edited this page Feb 3, 2016 · 1 revision

Retrospectives

hackweek 2016-02-01

What story am I telling?

What does a typical retrospective look like? We all gather in a single location and retrospect on the previous iteration; discussing what went well and what didn't, as well as gather ideas on how the team can improve as a whole. This often comes in the form of a physical medium such as a board and sticky notes. This is the textbook definition of a retrospective. However, application of this defintion to real-world teams can present intersting challenges.

For one, we are often not in a single location. Sometimes we out of the office or simply out of the state/country working remotely. This means a physical board can often be impractical.

Furthermore, we want to capture the output of the retrospective. How else can we ensure we are improving over the course of many iterations? Capturing a retrospective faciliated as described comes with its own process: taking photos of the stickies and board, typing the stickes and ideas generated into a digital form, then posting these into a repository for historical reference.

V1 Sidekick: Retrospectives solves these problems by providing team members a mobile digital board in which to "stick" their ideas. Ideas are dot voted and help the team identify hot topics for discussion. In addition, it integrates directly with VersionOne; keeping track of previous retrospectives.

Feature Highlights

  • Knows who you are (what user, teams, etc.) and notifies when a retrospective starts for you to join
  • Real-time board with the 4 typical quadrants for team members to add their feedback
  • Feeback can be voted on by team members and allow for easy identification of important topics
  • Saves retrospective outcome back to VersionOne
Clone this wiki locally