Upgrades used to control Software Delivery. How well do you upgrade from one version to the other, do you run them side-by-side, etc, etc? When we deployed client/server the big separator is that they were ALWAYS distinct. Now we live in a world where we can “toggle” between the old and new, bringing about its own challenges. If you’re building software that toggles between feature sets there are a few scenarios you should always be…
The countdown is on, you’re almost there. Get that project out the door. Make it count. Complete. You’ve done the work, it’s almost time to celebrate your achievement.
Because if you’re not having fun, why are you doing it?
If you can’t change your plans, you shouldn’t be planning. This isn’t a complicated post – if you aren’t willing to change your plan – you shouldn’t be planning. Because plans always change.
Fixes are minor annoyances that bug us and hold us back. Add a label, change the field, move a button to the right, add a new page, clean up the navigation, add in some extra fields, show this as a grid, use a different UI widget, etc, etc. Fixes are a long list, they are the backlog that drags on forever that you open up and say – “Does this stuff still matter?” They do,…