Sprint 2 Planning
The goal for sprint 2 will be improving stability and security (mostly a continuation of sprint 1, obviously).
The sprint backlog items are:
The total ideal man hours is 29, which is hopefully a more reasonable amount for slightly less than 2 weeks (since I'm leaving a dayish for planning, setting up the demo and doing the retrospective).
All of these carried over from the last sprint with the exception of the last item. I discovered during the last sprint that my fake data insertion code no longer worked due to changes I had made towards the end of the semester when I first developed the application. I really need those routines in order to have adequate data for testing, so they need fixing.
So now, I just have to do it. Phew.
The sprint backlog items are:
| Priority | Description | Points |
|---|---|---|
| 300 | Add error checking, unit testing, and integration testing using JUnit, DBUnit, FindBugs, etc. | 16 |
| 290 | Add logging statements throughout the code | 3 |
| 270 | Add additional sanitization of input and other security measures | 8 |
| 255 | Fix fake data insertion code | 2 |
The total ideal man hours is 29, which is hopefully a more reasonable amount for slightly less than 2 weeks (since I'm leaving a dayish for planning, setting up the demo and doing the retrospective).
All of these carried over from the last sprint with the exception of the last item. I discovered during the last sprint that my fake data insertion code no longer worked due to changes I had made towards the end of the semester when I first developed the application. I really need those routines in order to have adequate data for testing, so they need fixing.
So now, I just have to do it. Phew.
Comments
Post a Comment