Accept innovation jam pcamp 2011

1,318 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,318
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
20
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Accept innovation jam pcamp 2011

  1. 1. Innovation Jams – Agile Innovation<br />Nils Davis, Product Manager<br />For Silicon Valley P-Camp 2011<br />
  2. 2. Agenda<br />What is an Innovation Jam?<br />How we did it<br />Outcomes<br />
  3. 3. Innovation Jam – What Is It?<br />Short focused period of “innovation”<br />Think and act outside the box<br />Learn some new technologies<br />Work with different people<br />Collaborate in a different and very focused way<br />Do stuff at a different pace than the day to day<br />Improve productivity and creativity<br />Ours took place over about a week<br />1 week of idea gathering and collaboration<br />1 weekend of development<br />
  4. 4. How<br />Gather ideas from community<br />Had a set of suggested categories: usability, visualization, BI, mobility, etc.<br />Elaborate and commit<br />Choose<br />Elaborate some more<br />Commit some more<br />Develop<br />Present<br />All in a very short time<br />
  5. 5. Gathering Ideas<br />
  6. 6. Gathering Ideas<br />38 ideas<br />250 comments<br />Lots of votes<br />Not just comments and voting but<br />“Are you willing to work on this idea?”<br />Competition started at this point!<br />
  7. 7. Selection<br />Exec committee<br />Normal exec criteria – ROI, target customer, cost, immediate impact to market, etc.<br />Execs engaged the whole time (and sponsored!)<br />Top five ideas then go to “code jam”<br />Teams rejiggered as needed<br />PM<br />Designer (shared)<br />Developers (including an architect, usually)<br />QA<br />Idea gathering and selection – 1 week total<br />
  8. 8. Thoughts So Far?<br />
  9. 9. Execution/Development aka “Code Jam”<br />Over 1 weekend<br />Friday morning Pacific to Sunday evening Pacific<br />(Friday night India to Monday morning India)<br />Highly distributed<br />Open Skype chat<br />Dev in the “cloud”<br />Lots of emails<br />All teams were working on new technologies (to them)<br />iPad<br />Mobile (HTML 5)<br />Sencha for visualization<br />Google Docs API<br />
  10. 10. End Game<br />Final presentation on Monday morning<br />Refined “marketing” presentation<br />Demo<br />All teams but one had working code<br />Execs selected winning team and runners up<br />Prizes awarded<br />
  11. 11. Lessons Learned<br />One of the projects is nearly in production, expected later this year<br />Lots of coding got done! But…<br />… The prototype is not the product<br />All required 2+ more FTE months of dev to get to v1<br />One weekend is not enough for a product<br />Many have been reviewed with customers<br />All are on the roadmap<br />In normal prioritization queue<br />Ideal for testing ideas<br />Teams *loved* it<br />Especially opportunity to learn/work in new technologies<br />Prizes may have motivated, but intrinsic motivation was more important<br />Everyone in the company had a chance to contribute to product progress<br />80% of Accept people involved in one or more phases<br />We *will* do it again<br />
  12. 12. Discussion<br />

×