Topic | A. Incremental | B. Rewrite |
---|---|---|
Time to Completion | Slower | Faster (because of less technical debt to manage, decreased tech risks, and lack of fast-track support) |
Technical Risks |
|
|
Incremental Value | Value available with each release | None until project matches functionality of OpenLMIS 2.0 (with toggle off feature set) |
Technical Quality | Likely higher due to ability to start with a clean slate, particularly in regards to test coverage. | |
Migration Path | ||
Scope | ||
Cost | ||
New Implementations During Project | New implementations can take advantage of incremental releases, have possibility of working with community on needed extension points | New implementations before completion will use 2.0 and have to upgrade later. |
Community Collaboration |