- Testing lessons**
designed by freepik https://stories.freepik.com/The coordinator asks some of the researchers in the community to use the tutorial and to report any issues or bugs. It is also recommended to organize training activities using the tutorial and gather feedback from participants. The outputs of the evaluation are:
- a list of issues and bugs.
- whether the tutorial needs polishing (go to step 4) or is ready for a release (go to step 6).
6. Release
designed by freepik https://stories.freepik.com/The tutorial is released on GitHub in a beta version and published on Zenodo. With this version, the lessons can be used for broader teaching and contributions.
At the end of the blitz …
Our development blitz took about one week and the ESMValTool tutorial was released in Beta-version.
Like every procedure, a development blitz has some pros and cons. A development blitz increases focus, creates satisfaction and good feeling, helps communication, and spreads best practices in the community. However, it may lead to disappointment, needs lots of commitment and slows down decision making.
Interesting readings:
The Carpentries Curriculum Development Handbook provides guides on designing and developing:
- different parts of a tutorial, see episodes.
- objectives and scope, see developing content.
- development and release stages, see lesson life-cycle.
Here, some blog posts about blitz planning that might be of interest:
Acknowledgment
Thanks to [Carlos Martinez-Ortiz], [Felipe], [Pablo Rodríguez-Sánchez] and [Tom Bakker] for their feedback.
