Team Rock-it are short on time, and there are now only two members left – it’s time we Blast Off into the performing stage!

How will Team Rock-it blast off? Fail Fast!

Looking back, moving forwards and The Conflict Fast Model.

Co-Creative Design and Development has been eventful for myself and our team, during the start of the module I suffered from the Dunning Kruger effect. My career experience involves working in teams, sprints and projects but for the last couple of years, I have been working on my own. In hindsight, I should have formed an approach based on sound research, rather than relying on my experience. Starting again from the beginning and reflecting on everything the team has been through I looked for team performing methodologies that work fast. The Conflict Fast Model and fail fast mantra aligns with my personal approach to conflict. The Fail Fast approach suits my impatience, direct honesty and the importance I place on psychologically safe working environments but this potentially only works in some scenarios and teams.

My approach in teams, is to rip the plaster off quickly, talk about the issues and this isn’t for everyone and I should have stepped back and thought about the whole team and what the whole team needed but now we are short on time and the team knows me better it’s the right time. “Inspired by this mantra we have a similar mantra at the team level. We “conflict fast” to make deep and real improvements within the team dynamic” (Pimentel Medeiros 2016). “If we take the Lencioni model as a reference, we can see that one of the dysfunctions of a team is fear of conflict. When a team avoids conflict, there’s usually no trust among the team members. Connecting this idea with the Tuckman model, when a team avoids conflict, they extend the forming phase. It is important to remember that for the Tuckman model, a team must face phases like forming, storming and norming before reaching the performance phase. There are no exceptions” (Pimentel Medeiros 2016). Moving the team on to work together as a real agile team. Now there are only a few weeks left we need The Conflict Fast Model. “The Conflict Fast Model – Changing a pseudo agile-team into a real agile-team (2016). “Putting together a high performance team is probably the most important ingredient of good agile adoption. If your company has a lack of team spirit, you are likely to have a pseudo agile-team. In my personal experience, with a pseudo agile-team, your agile adoption will fail. Sad, but brutally true” (Pimentel Medeiros 2016).

Measuring Team Performance

Mike Cohn – Advanced Topics in Agile Planning

Iteration Planning

Reliable Decisions

Agile Planning

The team has begun to formalise Agile processes which is supporting the team to reflect.

The team are heavily focused on using two main software tools: Trello and Miro. The team is far smaller, meaning there is less discussion but we have found Miro and Trello to be far more collaborative tools than GDrive and other software. We use Slack for general discussion and sharing research but even then we usually share our research on Miro.

Trello – Kanban

Trello – Sprint Planning

Miro – Asychnrounous & Sychronous Planning

Miro – Retro

SWOT Analysis

“This week’s spark activity involves carrying out a SWOT analysis. Normally, a SWOT analysis is used to identify strengths, weaknesses, opportunities and threats in relation to a business opportunity, or as part of a planning exercise. In this instance, the technique is applied as a means of reviewing the team’s performance so far. The aim is to harness the team’s intuition to identify areas of teamwork that might benefit from data collection. Once the SWOT analysis is complete, use the findings to identify metrics that have the potential to generate insight and either confirm the strengths and opportunities or mitigate the weaknesses and threats” (Falmouth University 2021).

The Goal Question Metric Approach

Sprint 6 ‘A new look, features and music’

Sprint Goal: Design a new feature, implement music and refine the look of our space

Sprint Planning (Pull Tasks from Backlog)

Collaborative Individual Tasks
Iterate 3D Environment
Ambience for Prototype
Select and implement animations
Synchronous/Asynchronous Team Tasks
Pitch Brainstorming
Brainstorming a New App Name
Refine Feature Design

Brainstorming a new app name

Brainstorming an App name

We held a synchronous collaborative session to brainstorm a new app name together. We used dot voting to indicate our favourite names.

The UX Team has been working on the user flow, competitor anaylsis and research into sustainable cocktails and gamificaiton of events.

Feature 1 A sustainable cocktail event

The feature will include gamification of rewards for sustainable actions:

UX Team Research:

A new name, idea and features:

Vision Statement: To give Millennials a way to find sustainable communities, so that they can express themselves and uphold their values in a social space safely and conveniently

What is a sustainable community?

“How Greenify Fosters Sustainable Communities The Institute of Sustainable Communities (1997) defines healthy climate and environment, social well-being and economic security as the three essential elements of a sustainable community (See Figure 1) [6]” (Lee et al 2013)

A collaborative brainstorm:

Fig 1. Features Brainstorm

A New Look for our venue space

3D Environment – Iteration

In line with my research from Sprint 5 and giving the environment more of a well-being, sustainable and inclusive vibe I’ve iterated on the architecture:

  • Layout & Curved Glass Roof
  • Skybox & Cocktail bar
  • Terrain
  • Curved ramp?
  • Plants plants plants?

Choosing an avatar and programming animations

Choosing music and sound

  • A forest ambiance for the background –
  • A women singing –
Video of singing


Firefly by Snowflake (c) copyright 2020 Licensed under a Creative Commons Attribution Noncommercial (3.0) license. Ft: bangcorrupt

Improving the terrain

Sprint Retro


New Skills, Confidence and pushing through barriers

Co-Creative Development has pushed me through a few confidence barriers. One being my fear of making a 3D environment and game, 3D Modelling, a dab at UX Design Sprints and some UX Research (with the help of the UX part of our team). I created imaginary barriers in my own thoughts and while reflecting with a friend and a cup of tea at Euston, I likened the process to endurance training or pushing past the pain barrier in training. My friend had her own barrier with programming, and struggling to push through her studies at a different university. Supporting her to breakthrough her own pain threshold for her Computer Science studies, revealed my own blockades. *Citation need

List of figures

Fig 1. Features Brainstorm

Fig 2. Layout

Fig 3. Skybox

Fig 4. Terrain



GRODIN, Debra and Thomas R. LINDLOF (eds.). 1996. Constructing the Self in a Mediated World. Thousand Oaks: Sage Publications.

LEE, Joey J. et al. 2013. ‘Greenify: Fostering Sustainable Communities via Gamification’. In CHI ’13 Extended Abstracts on Human Factors in Computing Systems. 1497–502. Available at: [accessed 22 Jul 2021].

Mike Cohn (2012) Advanced Topics in Agile Planning [online video]. Available at: (Links to an external site.) [accessed 5 May 2021]

PIMENTEL MEDEIROS, Manoel. 2016‘The Conflict Fast Model | Agile Alliance’. 2016. Agile Alliance | [online]. Available at: [accessed 26 Jul 2021].

This exercise is derived from one found on (Links to an external site.).

  • How do You Measure Success? | Q+A. 2019. 

  • CASTKA, P., BAMBER, C. J.,  SHARP, J. M. and BELOHOUBEK, P. 2001. Factors affecting successful implementation of high-performance teams. Team Performance Management, 7(7/8), pp.123-134.

  • CSIKSZENTMIHALYI, M., ABUHAMDEH, S. and NAKAMURA, J.. 2005. ‘Flow’. In Anonymous Flow and the Foundations of Positive Psychology. Guilford Publications Inc, pp.227-238.

  • DINGSØYR, T. and LINDSJØRN, Y. 2013. ‘Team Performance in Agile Development Teams: Findings from 18 Focus Groups’. International Conference on Agile Software Development.

  • van den Hout, J. J. J. , Davis, O. C. and Walrave, B. 2016. The Application of Team Flow Theory. Switzerland: Springer.

  • KC, D. S., STAATS, B. R., KOUCHAKI, M. and GINO, F. 2019. Task selection and workload: a focus on completing easy tasks hurts performance. Management Science, 66(10), pp.4397-4416

  • LYNN, G. S. and REILLY, R. R. 2000. Measuring team performance’. Research-Technology Management, 43(2), pp.48-56.

  • Agile Team Perceptions of Productivity Factors. August 2011. 

  • TUCKMAN, B. W. 1965. Developmental sequence in small groups. Psychological Bulletin, 63(6), pp.384-399.