Agile Creative Teamwork at Trojan Horse was a Unicorn 2016
First the Colab members have been grouped randomly into teams of eight people each. Every team was then assigned two media industry veterans, who would be coaching the team. There was no formal hierarchy or strict role assignment apart from this. The only objective for the teams was to create an idea for a media product and actually pitch it to the rest of the Colab members in the end.
Hm … where did you hear that before?
If you have any experience with agile software development this will already sound familiar. Even if the roles of scrum master and product owner weren’t formally defined. The main focus of the two veterans was to herd the team into a direction and ease the decision making during the project – thus optimising the process and increasing the probability of a successful outcome.
During the project the following points struck me to be valid targets for improvements, in case the colabs return next year:
- A team size of eight creates a lot of discussion overhead. A smaller team might work more efficiently.
- Choose an odd number as team size. This way it would be easier to simply cast a vote when making decisions, since you will never run into a draw this way.
- Having the project work time in the morning hours of every day of the THU event lead to many members rather working on the project than actually attending the THU talks in the afternoon. It would be better to have the colabs en bloc upfront before the main event.
- Considering the actual creative work the hardest part was to agree upon a story. Maybe that should be part of a brief, if the colabs are to be repeated next year.
Apart from these points I really enjoyed the experience. I was actually wondering for some time before THU 2016 if an agile framework can work at all in a purely creative work environment. The colabs at THU proofed that point.
P.S.: I wonder if the THU playground will have an agile structure once it is up an running.