The APInf team organizes bi-weekly Experimentation Mondays. The purpose is to encourage a culture of experimentation and exploration. This allows the team members to learn by doing and to get familiar with new technologies. It hopefully will also increase job satisfaction. The experimentations can even be used for very minimal implementations of customer needs.
Bi-weekly:
- 10.4.2017
- 24.4.2017
- 8.5.2017
- 22.5.2017
- 5.6.2017
- 19.6.2017
- 3.7.2017
- 17.7.2017
- 31.7.2017
- 14.8.2017
- 28.8.2017
- 11.9.2017
- 25.9.2017
- 9.10.2017
- 23.10.2017
- 6.11.2017
- 20.11.2017
- 4.12.2017
- 11.12.2017
- and so on...
10:00am (EET)
- gather together (Meeting room Canada in Tampere, others online)
- everyone picks an idea, participants added to Github issues. You can assign yourself to issue already on Friday.
- start doing!
3:30pm (EET)
- gather together and see the results.
- close the issues
After the day, add front slide to video and upload to Youtube. You can add the front slide to the video in Youtube too. Add link to video in the given issue and correspondent experimentation day log.
- You have to do something - result must be something tangible
- Creating just specs or task lists is not enough (concept building is not doing)
All code results are under EUPL?
- All ideas in issues.
- When idea is "used", add description for it in the correspondent day log and close the issue. An example
APIOps is our experimentation community in which we engage with other developers. We encourage other companies to follow our example.
Thus all code results from Experimentation Mondays go under APIOps organization. https://github.com/apiops. Members of APIOps organization can create repositories. Just create a repository and put all in one place.
After the day every team member is expected to give feedback about the experimentation day. Use for purpose build API. Use the API via Swagger documentation. (Crafting the API is one experiment)