One development cycle consists from 5 steps:

1. Bug. Assign a bug to yourself before introducing any code changes.
2. Red. Write a failing automated unit test before you write any code, which reproduces the bug. If unit test could not be created, add test case to LazyCureTest\LazyCure_TestCases.xls.
3. Green. Write code in order to make unit test or test case passed.
4. Refactor. Remove code duplication, verifying that all unit tests still passed. You can repeat 2-4 steps by introducing additional tests, related to the bug.
5. Commit. Commit the code changes, specifying bug id and summary and any other details of maiden changes.

The following criteria is taken into the account when bug to fix is chosen:

1. Priority.
2. Severity.
3. Creation time.

New LazyCure build could be created if there is at least one bug fixed and there are no bugs with priority 9 – Highest.

New minor LazyCure release could be created if at least one new feature is implemented and there are no bugs with priority 7 – High or higher.

New major LazyCure release could be created if at least one major feature is implemented and there are no bugs with priority 5 – High or higher.

The latest version of LazyCure Development Strategy could be found on http://lazycure.wiki.sourceforge.net/Development+Strategy page.