Last year at the SAP TechEd event there was some confusion around the SAP InnoJam event, specifically in what was going to happen to the event in 2014. There were some rumors that it was ending and would be no more. Well I am here to tell you that it is alive and well!
However, with all things there are some changes I want you all to be aware of. Our team was tasked to taking on the SAP InnoJam challenge moving forward and so over the past several weeks we have done just that. We have spoken to tons of people, reviewed feedback, blog posts, tweets, etc. and come up with several options that were reviewed and discussed. What follows is how the SAP InnoJam events will be moving forward and what that means to all of you.
First the biggest change is that the "SAP InnoJam" event name and format we are reserving for use at our own annual event. The reason for this is simple; we want to be able to modify and adjust our agenda and format without causing disruption to the community, University Alliances and others. I think to best explain this the following goal and agenda will help.
The Goal
The goal and purpose of a InnoJam event is to give attendees a technology experience around the building of actual working solutions/prototype during the course of the event. Based on themes and business cases of real world problems.
Agenda and Flow (30 to 36 hrs)
- Welcome (5 mins)
- Keynote (40 mins)
- Business Case presentations (1 hr) - BizFire
- Each case represents a possible team
- Team Selection based on business cases (1.25 hrs)
- Teams are open, join the one that shows interest for the same business case you do
- Break (30 mins)
- Technology Showcase (1 hr per pillar, presentations from partners, etc.) - TechFire
- Design Thinking (1 hr)
- How can design thinking help your team
- What can Design thinking do for you
- Team separation, Design Thinking coaches assinged (30 mins)
- Break (30 mins)
- Team Work (24 hours) - Innovation Slam
- Presentation preparation with coaching (45 mins)
- Break (30 mins)
- Judging and Announcement (1 hr) - InnovationFire
Again this format will take place at SAP's own annual events each year. We tried not to make too many radical changes all at once so consider this a evolving format.
Our own UA program now have their very own event which is the "SAP UA InnoJam".
The Goal
The goal and purpose of a UA InnoJam event is to provide students with a guided experience around the building of actual working solutions/prototype during the course of the event.
Agenda and Flow (30 to 36 hrs)
- Welcome (5 mins)
- Keynote (40 mins)
- Theme Presentation (1 hr)
- Each event has a central theme designed in co-operation with faculty and regional businesses
- Team Selection (1.25 hrs)
- Teams are created randomly by the hosting team in order to mix universities, experiences; the faculty and students will be further separated to give the students a chance to challenge the faculty solution vs. solution
- Break (30 mins)
- Technology Showcase (45 min per pillar, presentations from partners, etc.) - TechFire
- 2 to 3 technologies present
- Design Thinking Mini Workshop (3 hr)
- How can design thinking help your team
- What can Design thinking do for you
- Team separation, Design Thinking coaches assinged (30 mins)
- Break (30 mins)
- Team Work (24 hours) - Innovation Slam
- Presentation preparation with coaching (45 mins)
- Break (30 mins)
- Judging and Announcement (1 hr) - InnovationFire
Now to round out the selections we've also asked the community to expand their own "" format to include an InnoJam style element. After speaking with the amazing folks in the Netherlands who have driven the community versions of the InnoJam the last several years we felt the following event format would be a good starting point and we've provided a suggested agenda however we hope that the community takes the opportunity to be innovative with the format and agenda of the event as well - who knows what amazing things will come about that we could roll back into the official event formats.
We are of course happy to schedule an open call to discuss any of these changes and we welcome all of your feedback!
