iteraplan Development Model - And How Customers Can Influence Development

Community Edition vs. Enterprise Edition

iteraplan is continuously developed by iteratec
  • Two editions:
    • Community Edition
      • Available as Open Source (AGPLv3 License)
      • No cost
    • Enterprise Edition
      • Offers additional features and services
      • Very moderate yearly fee.
      • Commercial license, no source code.
  • iteratec leads and funds general development
    • Users may contribute code, documentation, translations, …
    • Special customer features can be incorporated if customers provide partly funding

Release Cycle

  • iteratec publishes two releases every year
    • Scheduled for April and October
    • Additional bugfix releases published independently from the schedule, if required
  • iteratec maintains a roadmap of future features

How can this roadmap be influenced?

  • Feature priority determines in which release it is implemented

Handling of Feature Requests

  • After submission of a feature request to iteratec
    • Development team evaluates how the feature fits into iteraplan’s overall concept and roadmap
    • Feature request either accepted for the main development line, or rejected
    • Accepted feature requests become part of the long-term roadmap, without specific dates
      • no guarantees
      • no costs for customer
  • Feature sponsoring: To boost an accepted feature’s priority, customers can sponsor development
    • Cost sharing: iteratec looks for other customers who are interested in the feature and who are willing to sponsor it
    • Sponsoring costs depend on feature complexity and relevance for other customers
    • After sponsor commitment, feature is allocated to a specific release, i.e. developed with a delivery date
  • Customers can contribute feature implementations themselves
    • Development based on the Community Edition
    • Changes become part of the main line of development (subject to Contributor License Agreement)
    • iteratec welcomes code, translations, documentation, etc.
  • Customer-specific feature: individual development
    • Feature does not become part of main line of development
    • Customer covers all development costs
    • Additional costs for integrating the feature in future releases
    • Guaranteed delivery date