D1.4: Innovation Management Plan v1 #20

Closed
minrk opened this Issue Sep 8, 2015 · 7 comments

Comments

Projects
None yet
4 participants
@minrk
Contributor

minrk commented Sep 8, 2015

This is the first version of the Innovation Management Plan for OpenDreamKit. This report contains:

  • Some context about the Virtual Research Environment and the end-user / developer relation;
  • A description of transversal innovations OpenDreamKit is pushing for;
  • Notes on open source (mathematical) software development processes, with a focus on some systems the VRE is developing;
  • Elements of strategy for reaching out for a wide range of end-users.

@minrk minrk added this to the D1.4 milestone Sep 8, 2015

@nthiery nthiery modified the milestones: Month 18: 2017-02-28, D1.4 Mar 22, 2016

@kohlhase

This comment has been minimized.

Show comment
Hide comment
@kohlhase

kohlhase Jun 30, 2016

Member

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.

Member

kohlhase commented Jun 30, 2016

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.

@bpilorget

This comment has been minimized.

Show comment
Hide comment
@bpilorget

bpilorget Nov 21, 2016

Contributor

@nthiery We need to take care of this for February 2017

Contributor

bpilorget commented Nov 21, 2016

@nthiery We need to take care of this for February 2017

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Jan 10, 2017

Contributor

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.

Contributor

nthiery commented Jan 10, 2017

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.

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 6, 2017

Contributor

Dear M18 deliverable leaders,

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.

Thanks in advance!

Contributor

nthiery commented Feb 6, 2017

Dear M18 deliverable leaders,

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.

Thanks in advance!

@bpilorget

This comment has been minimized.

Show comment
Hide comment
@bpilorget

bpilorget Feb 28, 2017

Contributor

@nthiery Github description is done. From my view only the second section of the document (obviously) needs more information. But then again if you are under water this is merely the first version.

Contributor

bpilorget commented Feb 28, 2017

@nthiery Github description is done. From my view only the second section of the document (obviously) needs more information. But then again if you are under water this is merely the first version.

@nthiery

This comment has been minimized.

Show comment
Hide comment
@nthiery

nthiery Feb 28, 2017

Contributor

Second section fleshed up a bit; cross-proofreading with @bpilorget done. Submitted.
Thanks @bpilorget for writing this up!

Let's circulate this v1 among the participants to brainstorm toward adding some depth in v2.

Contributor

nthiery commented Feb 28, 2017

Second section fleshed up a bit; cross-proofreading with @bpilorget done. Submitted.
Thanks @bpilorget for writing this up!

Let's circulate this v1 among the participants to brainstorm toward adding some depth in v2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment