
Our skunkworks Twitter applications are complete! Over the past eight Friday afternoons our team has been working feverishly on experimental design & development projects using the Twitter API. Why? To learn and explore! The web is a constantly changing landscape, and to be on top of our game it is necessary to research and explore. Not to mention, we are a creative and ingenious bunch who crave experimental projects to work on.
Skunk works or skunkworks is widely used in business, engineering, and technical fields to describe a group within an organization given a high degree of autonomy and unhampered by bureaucracy, tasked with working on advanced or secret projects.
- Skunkworks definition on Wikipedia
76design’s Skunkworks Recipe:
76design donates time each week (usually Friday afternoon), and the team donates an open mind, fresh creative ideas, energy, and finally a working demo. The projects are intended to encourage exploration, therefore the skunkworks recipe itself is iterative and malleable. Through skunkworks we will be testing new approaches to web dev with the hope of integrating the findings into our daily work. That said, the following was a guideline for our first project, but we expect this recipe to change over time.
Week 0: Preparation of project Theme & Constraints
Constraint breeds design. Therefore we present the team with a challenge while leaving plenty of room for creativity. The challenge also centers the experimentation around a particular area of interest. For this project the Theme was Twitter, and the main constraint was the web application had to use the Twitter API.
Week 1: Brainstorming & Team Selection
The team gathered for a single large brainstorming session where everyone threw ideas at the whiteboard. This generated a large quantity of ideas, and encouraged the team to be creative, critical, constructive, and considerate. Following the brainstorm we broke into teams of 2 and selected the concepts we wanted to experiment with for the next few weeks.
Week 2: Research, Concept Refinement & Work plan
Now that the team has had a full week with their concept, they refine it into a concrete plan. Week 2 is all about editing the ideas & features down into a reasonable plan which can actually be accomplished within the short time line. This exercise involves documenting each task’s level of effort and priority. At the end of the project the teams are asked to compare the outcome to their initial plan.
Week 3, 4, & 5: Design, Code & Test
These weeks are all dedicated to designing and coding the project. The teams check in briefly every week to discuss their progress and help each other with challenges. Inevitably, unforeseen issues or fresh ideas will cause the plans to change, therefore the teams are encouraged to work iteratively using agile methodologies. Teams are graded on their ability to define project scope and manage scope change.
Week 6: Present working demo to the entire team
The projects are now ready for a functional demonstration, and everyone gathers in the boardroom for a short 5 minute presentation and Q&A period for each project.
Week 7: Followup
The teams will write a reflective blog post about their project which includes an overview, the challenges faced, the outcome, and the potential next steps for their project. Teams will also share the insights they gained from the skunkworks experience. Furthermore, teams will post relevant information to our company wiki for future use. The Teams are free to continue the projects if they wish, or publish them online as they are.
So stay tuned. The first round of skunkworks twitter applications are complete and we will be posting the team’s project followups over the next week or so.