38
edits
Innovation/Open Source Experiments: Difference between revisions
add link to experiment setup page
(format fix) |
(add link to experiment setup page) |
||
| Line 79: | Line 79: | ||
* Write and approve plan | * Write and approve plan | ||
* [[Innovation/Experiment Setup]] | |||
* Run and document experiment | * Run and document experiment | ||
* Evaluate and transfer as needed | * Evaluate and transfer as needed | ||
| Line 91: | Line 92: | ||
We will track these items and assemble complete experiments. In some cases there will be a principal investigator plus another contractor, on separate contracts. (For example, a project requiring a complex bot might have a PI focused on the codebase being developed and a bot developer/administrator working mostly in a separate bot repository.) | We will track these items and assemble complete experiments. In some cases there will be a principal investigator plus another contractor, on separate contracts. (For example, a project requiring a complex bot might have a PI focused on the codebase being developed and a bot developer/administrator working mostly in a separate bot repository.) | ||
Deliverables for experiments should be simple and self-contained. For example, an ideal deliverable is a report or blog post. Software projects for experiments will run more smoothly if the deliverable is a set of data or results _about_ the software, and not the whole project. | |||
== Project scope == | == Project scope == | ||