Planned Iteration Schedule

These past few weeks since we've been ramping back up on the development of Lysine, we decided to do time boxed iterations of one month in length, starting each new iteration on the 1st of every month. Iteration 1 will complete by October 1st and while we will not likely have a releasable Beta by that time, we should start being able to forecast much better than we've done in the past.

We've accomplished a lot thus far in this iteration. Our backlog of items is solid, we've been fixing a lot of bugs and thinking more and more about the UI and User Experience rather than being knee deep in the guts of how and when to perform the proper bitwise operations on the raw bytes to yield a proper conversion.

In the past couple of weeks we've made over 330 file changes within 44 commits to our repository. We've loaded up the product backlog with a total of 54 items, have resolved 30 of them. We currently have 8 items left remaining in the queue for Iteration 1.

In addition, we've been doing work outside of what is listed in this schedule as we are still getting used to tracking everything. For example, I have added a lot more tests and have been leveraging the Code Coverage tools in VS2005 to point me to spots in the code that are not tested. Several weeks ago, we had only 10 to 15 percent of our code covered by unit tests, as of tonight we have over 80%:

Only a few weeks ago we had less than 50 unit tests. As of tonight we have 250 tests (207 passing).

Tags: lysine, amino software, unit testing, code coverage, planned iterations, iteration