TO-DO: record here the partial or final conclusions and results of the technical experiment.
TO-DO: describe here the objectives that motivated this technical experiment. Usually, a design decision will be made based on the results of the experiment. Explain what decision that is and what system(s) will be affected. Hint: try to articulate the objective as a technical question that you need to answer. Example: what is the minimum bandwidth for my app to stream video at 25 fps on HD?
[Planned | In progress | Suspended | Canceled | Concluded]
Add different statuses as you see fit.
TO-DO: list the deliverables that the experiment is expected to produce. Examples:
- executable, functional prototype
- presentation to the team
- report/table comparing 2+ technologies/products/design alternatives
TO-DO: list the resources that are required to execute the experiment. They may include, for example:
- software tools or frameworks
- product documentation or other reading materials
- effort in person-days
- machines, VMs, or other hardware elements
- access to computational resources
- dedicated space in a database
TO-DO: describe how do you intend to execute the experiment. It can be, for example, a sequence of activities to perform. Activities may include, for example:
- research on the Internet for alternatives
- studying the documentation of a tool/framework
- creating the code of a prototype
- running tests/benchmarks
TO-DO: indicate the deadline for concluding the experiment. Be realistic and make meeting the deadline a goal. If appropriate, indicate intermediary milestones.
TO-DO: list here publications, web pages, etc. that contain information relevant to the experiment.