Thank you for the wishes Peter.
I’ve finished the first sprint and it’s time for a little
I found writing a product backlog and using the sprint concept very
useful. But I think I have missed something during the sprint. Even in
solo, the concept of daily scrum meeting should probably be used, and
adapted like I’ve read on some comments: “a time to reflect on what
was previously done, what will be currently done, and what is holding
on the back.”
In short, my first sprint was composed of 2 product backlog items. The
first item was splinted in 3 tasks and the second in 2 tasks. The work
was done in 7 sessions of roughly 3 to 4 hours.
Unfortunately, while working on the third task I have started to work
on related features that were not clearly planned for this sprint and
should have been better defined and developed on later sprint. And for
the worse, I have encountered some unexpected technical difficulties.
The task initially estimated to 2 ideal man hours has finally taken 15
hours with a mitigated result. I could probably say I was overwhelmed
by a bad habit of cow-boy coding ;)
Finally the sprint has ended with only half of the tasks done. I think
this sprint has highlighted two of the main risk of this software
project: The first is to develop unplanned “fun” features and break
the planning. It’s a classic use case for hobbyist game developers.
The second risk was highlighted by the technical difficulties I’ve
encountered. I must try to reduce the number of features that are not
already covered by tutorials or templates provided with the tools I’ve
choose. My limited skills with these newly acquired tools (Unity3D)
forces me to focus on essential features to get my prototype done in
So, I have redefined the second sprint for including the task that was
not done in the first. I have stopped to use IceScrum2 and decided to
use some spreadsheets and my white board (simpler is better). I will
try to take 5 or 10 minutes before each session to reflect on what was
done, will be done …etc. And I will whip myself to avoid cow-boy
This second sprint should end July 31. A 4 pages PDF file is available
on my website with updated features, product backlog, sprint backlog
#1 and #2.