Retrospective - WuppDays #1
- Douglas Webb
Owned by Douglas Webb
Date: 2015-10-15
Location: Malo
Facilitator: Clemens Wolff
Top 6
What we did poorly: lack of daily schedule.
- Â pre-meeting before the next wuppdays to define draft schedule
- refine structure communally during the first days of the next wuppdays
- find a person to enfore rota of schedule/chores durng the wuppdays
- find a way for the enforcer not to be a drill seargant
- look for dedicated chores people
- get everyone to participate in chores, do not exclude developers from chores
- respect people's priorities laid out in application
- coordinate meeting-time with chore-time so they don't overlap
What we did poorly: lack of project structure.
- plan before the next wuppdays what will be done
- create a process for meetings: hand-gestrures, agenda, faciltator, goal
- be clear about what we're trying to do, dessiminate goal one-pager
- train participators in meeting process, dessiminate required reading
- search for dedicated facilitators
- take shared checkins of teams more seriously and actually do them Â
What still puzzles us: how do we continue in the future?
- Â find a community manager to have an overview of the project and tasks
- come up with a process of how people get assigned to tasks, e.g. have a spreadsheet with contributors and their interests and farm out tasks to them that seem relevant
- make sure that people delegate their tasks when they don't have time or energy to work on them
- have concrete and attracting tasks for new contributors to pick up
- present what is there and what needs to be done
- summarize what we can port from the foodsharing community on how to get people involved and come up with a contributors recruitment plan
- define the objective we want to reach
- think about ways to keep people involved, e.g. ask people for specific
- commitments not just general contributionÂ
 What still puzzles us: why are we copying Facebook?
- Â ask designers for alternative designs and discuss them, don't just implement the first thing that comes up
- explain how the Facebook functionality fits into the bigger picture
- have the current foodsharing process documented and explained online
- have a plan of features we want and why we want them and how the features fit into the vision and mission
- come up with a process to democratize prioritization without using too much time, e.g. investigate user needs deeplyÂ
 What we did well: good spirit!
- Â get an animator/team-builder
- make a list of energizers that work well
- make it explicit that activities like energizers are entirely optional so that people who don't feel comfortable with them can not participate and come up with a way to create a group feeling in different ways
- have a team building activity at the start that forms the group but still is focused on the project e.g. dragon dreaming
- come up with a process for introducing new members and visitors to the group
- have tasks ready for new people to pick up immediately
- have mentors to get new members up to speed
- come up with a way to have less people leaving half way through, ask for
- commitment for the full time, cutoff entry and leaving point, open door day
- for people who are interested in the project but don't want to commitÂ
 What we did poorly: lack of silent space.
- Â make separation between work area and living area clear
- have the work area not close to the socializing area
- have a dedicated quiet room
- have retrospectives aimed towards improving living and working together more frequently
- have a designated trust-person with whom to share concerns privately
- find more channels through which people can report problems
- have owners who make sure that problems that get brought up actually get fixed
To the extent possible under law, the yunity wiki contributors have waived all copyright and related or neighboring rights to the content of the yunity wiki. More information...
You have an account but can't edit or create pages? Write us in the open chatroom or in our yunity Slack!