I released the alpha of the Costs to Expect App yesterday. It is later than planned, but I don’t want to dwell on that, I have other posts that explain the delay.
I am now going to work towards the public alpha. I’m not going to adjust the release date; I am still hoping to have it ready for the 1st of April, as we get closer to the release I will update the roadmap accordingly.
At the start of the year, I had an accident, the result, a rotator cuff injury that is slowly healing. I still have a long way to go before my shoulder is back to normal strength and mobility.
A shoulder injury doesn’t sit well with programming, my productivity for the first three weeks after my injury dropped to zero. I’m back at work; however, I am not yet at 100%, I’m working in bursts.
I initially planned to release the private alpha of the Costs to Expect App in November. Minor delays meant I pushed it back to December. Due to injury and typically development delays, I released the alpha yesterday.
Delays and setbacks with development are common. I use Pivotal Tracker; after years of use, my iterations are typically spot-on. In my case an iteration is two weeks long, it might contain 60 points worth of work, I’ll create ‘n’ new tickets and ‘m’ bugs. By the end of the iteration, I’ve mostly completed everything I had planned.
There are weeks when I work less, and I’ll adjust the team strength value to take into account absence, but when you don’t work for three weeks, the impact is enormous. It would be easy to think I’m three weeks behind, that isn’t true, I didn’t do three weeks of development however in that period I would typically create ‘n’ new tickets and ‘m’ bugs.
I can never recover the lost time, that is gone, I’m going to use this as an opportunity to review the ‘plan’ and re-prioritise. As good as the ‘plan’ is I’m reasonably confident there are some ‘likes’ I can move further down the list and ‘needs’ that can move up the list.