{"id":6923,"date":"2012-08-02T07:21:59","date_gmt":"2012-08-02T14:21:59","guid":{"rendered":"http:\/\/integrumtech.com\/?p=6923"},"modified":"2012-08-02T07:21:59","modified_gmt":"2012-08-02T14:21:59","slug":"an-agile-teams-lessons-learned-startup-weekend","status":"publish","type":"post","link":"http:\/\/integrumtech.com\/2012\/08\/an-agile-teams-lessons-learned-startup-weekend\/","title":{"rendered":"An Agile Teams Lessons Learned from Startup Weekend"},"content":{"rendered":"
This weekend the Integrum team decided to participate in Chandler Startup Weekend<\/a>. Startup Weekends are weekend-long, hands-on experiences where entrepreneurs and aspiring entrepreneurs can find out if startup ideas are viable. Teams focus on customer development, validating their ideas, practicing LEAN Startup Methodologies and building a minimal viable product.<\/p>\n As a team we decided it would be a fun way to spend some time together and challenge our abilities. We told ourselves that we would either join a pitched idea and work as the development team or we would play with an idea of our own and deliver the product. Either way we wanted something that could be done within the short time we had together while leaving no pressure to continue past the weekend. We also knew we were slightly handicapped because we would NOT be working on Sunday.<\/p>\n The Wednesday before Startup Weekend we spent a fifteen minute time box on brainstorming some ideas. Here is the list we came up with:<\/p>\n Friday night we showed up ready to jump right in to something. We got some dinner from Pittsburgh Willy<\/a>‘s and then started listening to pitches. As the pitches were winding down we decided to keep it just our team because we would not be around on Sunday and to go with the Craigslist Car Scraper. At this point it was about 8pm and we found a room and got started.<\/p>\n We started out by doing a quick Agile Lift Off<\/a>. This process took us about 30 minutes.<\/p>\n Vision<\/strong>: Allow vehicle buyers with less than $5,000 an efficient way to locate a new vehicle. We then did a quick story workshop in about 30 minutes to generate a backlog of stories. \u00a0After creating the backlog we sorted it and started planning. It quickly became apparent that at no stories larger than 1 hour, that 1 hour sprints probably made sense. When breaking down tasks we made our smallest time box 6 minutes or 0.1 hours. Most tasks were either .1 or .2. We setup two clocks, one to measure iteration time (1 hour) and one to notify of time box (6 minute).<\/p>\n At the end of every sprint we would do a Core Protocol Checkin<\/a> and then do a quick retrospective. After the retrospective we would take a break and play some NFL Blitz<\/a>. Then right back into another planning (generally about 10 minutes).<\/p>\n We worked from 8pm – Midnight (4 hours) on Friday and 8am – 8pm on Saturday (12 hours) for a total of 16 hours including time for breaks, meals, etc. We had 3 sprints on Friday night and I believe 6 sprints on Saturday for a total of 9 hours of keyboard time.<\/p>\n This is what we produced http:\/\/hooptie.co<\/a><\/p>\n\n
<\/a><\/p>\n
\nValues<\/strong>: Fun experience, Less BS, Less time on Craigslist, Best deals right away
\nWorking Agreements<\/strong>:<\/p>\n\n
<\/a><\/p>\n