Saturday, May 01 2021 other-methodologies
Imagine this: You’ve just started working on a new team and you’ve your first task, a simple bug fix to address a problem recently experienced by multiple customers. After pulling the code down onto your development machine, you’ve opened it in for the first time and you can’t quite believe what you’re seeing on screen in front of you.
Saturday, May 15 2021 other-methodologies
Imagine this: You are developing a new product feature, requested by one of your company’s most important customers. After nearly a fortnight of work, you’ve almost finished the work – a couple more days and it will be ready for release. This morning your manager asked you to temporarily drop that work so that you can urgently work on a different feature, for a different customer.
Saturday, May 29 2021 other-methodologies
Imagine this: You’re the manager of a development team and you normally give your developers a fair amount of autonomy. There’s a shared backlog of tasks and developers are free to select whatever they like. Your expectation is that they’ll work on a mix of bugs, features, and general product quality improvements – but you’ve noticed some of your mid-level developers are exclusively working on new features, and never on bug fixes or improving quality of existing features.