I believe that the "innovation managment plan" normally means to specify who owns the IP of innovations, who exploits them, and similar matters. If that is true, then writing this for ODK should be trivial. But we have to check whether my recolllection is actually true.
Executive summary of the above, if I understood correctly: the Innovation Management Plan is not so much about what kind of innovation will be undertaken in our project, but the steps we take to foster innovation, from creative thinking to selection of the good ideas and actual implementation of them.
In this case, innovation management is just what we do everyday as researchers :-) So it feels a bit verbose to rant about it. Well, we can, in a few pages, describe how we work (user driven development, focused workshops like Sage Days, with brainstorms and experiments, coding sprints, regular online meetups in the Jupyter team) and the collaborative tools we use (mailing lists, version control, editing pads, wiki, ...).
That's an occasion to showcase our processes to the reviewers (they may be unfamiliar with it) and could even be the occasion to exchange between each other some tips about what is effective.
Note: there is some overlap with our aim about identifying and showcasing best practices for software development; we can see this as a preliminary step in this direction.
Just a reminder that reports are due for mid-february, to buy us some time for proofreading, feedback, and final submission before February 28th. See our README for details on the process.
In practice, I'll be offline February 12-19, and the week right after will be pretty busy. Therefore, it would be helpful if a first draft could be available sometime this week, so that I can have a head start reviewing it.