-
Notifications
You must be signed in to change notification settings - Fork 3
Project management
lrozenblyum edited this page Aug 28, 2019
·
3 revisions
| Principle | Explanation | Motivation | Since |
|---|---|---|---|
| Test-driven development | Red-green-refactor | Evolution of interfaces. Good regression testing artifacts. | 0.1 |
| Internal quality | Every release contains internal improvements. It can be refactoring, libraries upgrade, new documentation etc. | Keep interest to the project. Minimize technical debt. | 0.1 |
| Release automation | Releases are automated to a big degree which will eventually be increased | Improve automation skills. Make it easy to release. | 0.3 |
| Fixed release dates | A release should have a fixed due date | Remedy against too long releases (like 0.3). | 0.4 |
| Agressive splitting | If there are any blockers or unclear parts of a task they should be split to a new task | Remedy against procrastination. Main supporter of 'Fixed release dates'. | 0.4 |
| Stable unit tests | Unit tests should not rely on random values | Remedy against unstable tests | 0.6 |
| Possible random integration tests | IT tests may contain true work with Random | Possibility to find something not found by stable tests | 0.6 |