---
# System prepended metadata

title: EXCLAIM development process discussions

---

# EXCLAIM development process discussions

The purpose of this document is to outline discussions about the development process of EXCLAIM.

* Where are pain-points?
* What can be improved? How?
* What is working well

# Cycle 12

## Clarifications regarding shape-up

*Ben*

* Do we expect that we finish all projects that we plan? Because sometimes we don't.
* What about unexpected tasks (e.g., bugfixes)? Since we never planed for those, how are we supposed to deal with them?
* What if circumstances change during the cycle and we would prefer to invest time into a different task instead?

Answers given by Matthias & Hannes:

* If we don't finish a project the project can be extended into (part of) the cool down in exceptional cases if all steps to completion are fully understood (they are "down-hill" in their language)
* Bugfixes that are not emergencies are taken care of in the cooldown. But also you can shape a bugfix project that accumulates a list of important bugfixes.
* It should be added that if there is significant portions left (guess especially if there are "uphill" tasks which are not completed) at the end and nothing can be shipped, the (remainder of the) project needs to be shaped again and brought to the betting table once over