Apr 18 - May 8Phase 1May 8 - 27May 28 - Jun 5
SPRINT 3.1: DEVELOPING ADAPTABILITY HACKS
We will assign a hackathon guide to each hacking team so that if you have questions as you are developing your hacks, you have someone to show you the way. If you are leading or participating in a hacking team, you will be introduced to your teammates and your hacking guide via email shortly (and some of you may have received this email already).
For this sprint we have two tasks:
TASK 1: Review this "hack cheatsheet," a short guide for creating a great management hack. The document contains a number of practical tips as well as links to some of our favorite hacks already contributed by members of the MIX community.
TASK 2: Connect with your hacking team and begin hacking.
- Each team lead should have received or will soon receive an email connecting them to all of the people that have joined their hacking team and their guide. Once they receive this email, team leads should connect their team as soon as possible to begin work.
- Each hack should be developed using this hack template (.docx version) or hack template (.pdf version).
You may wish to collaborate by discussing then sharing a version of the hack via email. Or you may want to create a shared Google Drive doc that everyone on the team can access to minimize versioning issues. You may also want to set up a Google Hangout, Skype meeting, or other collaborative session so team members can meet and discuss the hack before beginning work. It is up to each team to decide what tools to use to collaborate. We’ve found that this is usually better than forcing people to use one collaboration tool that may not work equally well for all teams. Use whatever tools you are comfortable with for collaborating.
- Each team should post a solid draft of their hack to their hack page (find your hack in the list here) before this sprint ends on August 12.
- If you have other questions or issues, email either your team's hackathon guide or email hackathon guide Chris Grams.