Suggested criteria for project management software evaluatation
You may disagree with some of these criteria, but if so, I would be interesting in learning why. My viewpoint is requirements for a cooperative economic system. That might not be what you want to do.
These are comments on https://git.fairkom.net/faircoop/Tech/General/wikis/PM-Testing
- More than one person can collaborate on the same thing (whatever they call "thing" in their software).
- Each person can get credit for their individual contributions to the collaborative effort.
- They can collaborate on creating something, and the something they created can be reported and saved in some kind of repository where others can make use of it, until it is gone.
- They can report their use of equipment and consumption of materials in making something, and the quantities of materials they consumed will be removed from wherever they were electronically recorded.
- They can optionally get credit for what they created instead of how long it took them to do it.
- People can work on flows that contain several stages of effort that go into making something, for example,
- translating a document, editing the translation, and formatting for publication
- mixing dough, kneading dough, forming loaves, baking bread.
- Different people can work on each of those stages, and each get credit for their contribution to the end result (e.g. published document or baked bread).
- Those workflows can intermix digital and material things, like creating the recipe for the bread, and then making the bread.
- The workflows can cross different autonomous organizations, forming supply chains.
- The workflows can be planned beforehand.
- Workflows that are used a lot can be recorded in some form so that they can be easily replanned without starting from scratch and defining everything.
I can come up with more, but that seemed like enough to understand your goals. If anything is not clear, please ask.