Slide 1

Slide 1 text

Hasso Plattner Institute University of Potsdam, Germany [email protected] @chrisma0 Virtual Team Members for Agile Retrospectives Christoph Matthies Dagstuhl Seminar BOTse, November 2019

Slide 2

Slide 2 text

Motivation 2 Why ChatBots for Development Processes? ■ Chat solutions widely used in software teams ■ Bots ➞ “virtual team members” [Lebeuf et al., 2017] □ Remote team member who only chats □ More team capacity! □ Give new (bot) team member development process analysis role [Lebeuf et al., 2017] Lebeuf, C. & Storey, M.-A. & Zagalsky, A., “How Software Developers Mitigate Collaboration Friction with Chatbots”, Talking with Conversational Agents in Collaborative Action Workshop @ CSCW'17, 2017.

Slide 3

Slide 3 text

Application Context 3 Scrum Retrospective: dedicated improvement meeting [Schwaber et al., 2017] [Schwaber et al., 2017] Schwaber, K., & Sutherland, J., “The Scrum Guide - The Definitive Guide to Scrum: The Rules of the Game”, 2017, [online] Available: http://scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-US.pdf

Slide 4

Slide 4 text

The Scrum Retrospective 4 A Habitat for an Software Process Analysis Bot Retrospective Meeting Sprint ■ What went well? ■ What should be improved next iteration?

Slide 5

Slide 5 text

The Scrum Retrospective 5 Did we improve what we planned? Retrospective Meeting A Habitat for an Software Process Analysis Bot

Slide 6

Slide 6 text

The Scrum Retrospective 6 A Habitat for an Software Process Analysis Bot Did we improve what we planned? commits, reviews test runs tickets static analysis Retrospective Meeting Project Data Evidence of last iteration’s work

Slide 7

Slide 7 text

The Scrum Retrospective 7 A Habitat for an Software Process Analysis Bot Did we improve what we planned? commits, reviews test runs tickets static analysis Retrospective Meeting Project Data Evidence of last iteration’s work

Slide 8

Slide 8 text

The Scrum Retrospective 8 A Habitat for an Software Process Analysis Bot Did we improve what we planned? commits, reviews test runs tickets static analysis Retrospective Meeting Project Data Evidence of last iteration’s work

Slide 9

Slide 9 text

9 Retro Bot Vision

Slide 10

Slide 10 text

Related Work 10 An Entire Family of Software Bots ■ Tools for supporting Retrospectives through automation □ Reminders, archiving action items [goReflect, 2019] □ Facilitating activities [Retrium, 2019] □ Running surveys [Standuply, 2019] □ Document results [RetrospectiveBot, 2019] ■ Existing bots automate organizational tasks, Based on team’s perceptions, little focus on data! [goReflect, 2019] GoReflect, “goReflect - Continuous Retrospectives for Agile Improvement,” 2019, [Online] https://www.goreflect.com/ [Retrium, 2019] Retrium, “The era of boring retrospectives isover,” 2019, [Online] https://www.retrium.com [Standuply, 2019] Standuply, “Retrospective Meeting Slack Bot,” 2019, [Online] https://standuply.com/retrospective-meeting [RetrospectiveBot, 2019] retrospective-bot contributors, “Retrospective Bot” on GitHub [Online] https://github.com/bayesimpact/retrospective-bot

Slide 11

Slide 11 text

Image Credits 11 In order of appearance ■ Robot by Oksana Latysheva, UA from the Noun Project (CC BY 3.0 US) ■ Analysis by mynamepong, TH from the Noun Project (CC BY 3.0 US) ■ Developer by shashank singh from the Noun Project (CC BY 3.0 US) ■ Wall by Creaticca Creative Agency from the Noun Project (CC BY 3.0 US) ■ Feedback by Shocho from the Noun Project (CC BY 3.0 US)