We are often asked how our band of Melon Twits functions. We try our best to be as agile as possible and are continuously trying to improve upon and evolve this. We use our evolved version of Scrum because we feel it allows the team to take responsibility rather than the individual. We use Scrumwise to help us keep track of what’s going on.
Sprints - Twits usually run two week sprints to attempt to maintain agility. The sprint is only altered if the entire team agrees.
Sprint Planning - Twits use the backlog to decide upon the next most important items to complete and add their own tasks to an item to describe the development involved. We associate points to the items to roughly determine if the correct amount of points are present in the sprint. Our sprint’s goal is themed to a song title chosen by the team.
Daily Scrum - Twits grab a drink as a team and then have the Daily Scrum at around 9:45. The Daily Scrum, for Twits, is a means to stay curious about each other's work and understand how the project, as a whole, is progressing. One Twit provides a summary of daily activity at the end. Daily Scrum is replaced on Mondays with a team sit down where Twits catch up and outline the week ahead.
Retrospective - Like all our processes, retrospectives are a work in progress. Twits try to make these entertaining and each Twit has the opportunity to present what they have been working on over the last sprint. We also look into any improvements that could be made to the way we are working and give any other useful updates to the team.
Once a week for a couple of hours Twits pair up and teach each other something from their knowledge domain. For example, an iOS developer may teach a web developer how Core Location can be used. We believe that this helps to transfer knowledge, improve team communication, improve our ability to describe our work in technical detail, develops team relationships, and provides us all with an appreciation of what each other is doing.
On Friday afternoon Twits work on the Friday afternoon project. This is currently Collobus, a question and answer application for use by teams. The Friday afternoon project allows the team a chance to work on something new and lemon twisty at the end of the week, whilst developing new skills.
All business staff have a "tech mate" randomly assigned. Bugs, ideas, and feedback, can be reported to an individuals "tech mate". The engineering mate will then go through necessary steps and provide feedback. Tech mates alternate every 6 months.
When we are hiring new Twits two key tenets are thought about and discussed. Firstly the potential Twit must fit in culturally and believe in the philosophies that the team stands by. Secondly the potential Twit must meet the technical standard for the role being applied for. Although the potential Twit must meet the technical standard we are not pedantic about some particulars and are always willing to teach new Twits. Please don’t worry if you don’t fit the job specification precisely.
We understand that having interviews can be extremely stressful and we do our absolute best to make sure that potential Twits are made to feel comfortable and welcome at all times. We always hope that your interaction with us is a great experience.
Potential Twits all go through the process outlined below: