The workflow related to a Z-Bounty starts when somebody submits a feature request, and ends with the release of a solution for it, as further detailed below.
After you've explored the sections like Z-Wiki, Z-Issues, Z-Clues and Z-Files, you'll for sure realize the tremendous effort (investment) done so far to create the current content of these sections (and related downloadable solutions).
But, one never realizes what has been done, only what remains to be done …
Z-Issues contain the problem statements for commonly known issues in ChangeMan ZMF (mostly enhancement requests, sometimes problem tickets). A possible solution for each of the issues mentioned can be found in either:
This section contains information about a possible solution for each of the issues mentioned within the Z-Issues. It is the documentation about how a possible solution of the specific Z-Issue might look like.
This section contains the complete set of software related to the specific solution of any issue described in the Z-Issues. This software is fully compliant to what is documented in the Z-Clues also, and includes installation instructions, info about configuration options, etc about the software. For short: the Z-Files section is actually a collection of slick stuff for enhancing ("mashing up") your ChangeMan ZMF implementation dramatically!
Z-Reports On Demand is about creating a customized version of any of the Z-Reports, so that such report (and/or graph) perfectly fits the ChangeMan ZMF reporting requirement. Developing (on demand) a brand new report (or graph) that fits into the Z-Reports category (and where it will be added to also) is a variation of it.
The ChangeMan ZMF documentation is probably in here ...
The Z-Wiki (for short the Z-Wiki, pronounced as zwiki) contains all sorts of information and in depth documentation about ChangeMan ZMF, not included in standard ChangeMan ZMF manuals. This kind of documentation was typically produced by experienced ChangeMan ZMF administrators and consultants.
No matter how good and complete user and/or admin manuals are, there will probably always be issues, questions, etc that have not been documented. However, quite a bit (maybe even 'MORE'?) topics seem to come back in various ChangeMan ZMF implementations. Addressing those issues and questions is the main purpose of this Z-Redbook section, which includes guidance and implementation experiences.
Sometimes you can achieve amazing results in using vanilla features, simply by using these features in a special way (that the ChangeMan ZMF developers may not even have thought about when designing / developing ChangeMan ZMF).
After you've explored the sections like 
Z-Issues contain the problem statements for commonly known issues in ChangeMan ZMF (mostly enhancement requests, sometimes problem tickets). A possible solution for each of the issues mentioned can be found in either:
This section contains information about a possible solution for each of the issues mentioned within the 
This section contains the complete set of software related to the specific solution of any issue described in the 
The Z-Wiki (for short the Z-Wiki, pronounced as zwiki) contains all sorts of information and in depth documentation about ChangeMan ZMF, not included in standard ChangeMan ZMF manuals. This kind of documentation was typically produced by experienced ChangeMan ZMF administrators and consultants.
No matter how good and complete user and/or admin manuals are, there will probably always be issues, questions, etc that have not been documented. However, quite a bit (maybe even 'MORE'?) topics seem to come back in various ChangeMan ZMF implementations. Addressing those issues and questions is the main purpose of this Z-Redbook section, which includes guidance and implementation experiences.
Sometimes you can achieve amazing results in using vanilla features, simply by using these features in a special way (that the ChangeMan ZMF developers may not even have thought about when designing / developing ChangeMan ZMF).