3 ms·
OK, I take it your answer for visibility is management reporting, I am not sure about predictability, you didn't really answer it. SW development is as predicta
by js8 4y ago
OK, I take it your answer for visibility is management reporting, I am not sure about predictability, you didn't really answer it. SW development is as predictable as much you're willing to invest into research/planning, and that very much overlaps (as observed in Kanban) with doing the actual work.
When I started SW development in 2005, we had one meeting a week (Friday) with our boss, where we summarized what progress we made during the week. It was exactly what he and his superiors needed to know, not anything more.
- robertlagrant 4y ago> OK, I take it your answer for visibility is management reporting, I am not sure about predictability Not reporting. Reporting is an internal function. People would like to know what's happening and what's going to happen, so that they know roughly what to expect for planning purposes elsewhere in the business, e.g. marketing. Not just reporting for its own sake.
- js8 4y agoIf you want to know how long it will take to develop a feature, just create a task for this research/design/planning and schedule it as usual in Kanban. Still, no sprint required.
- robertlagrant 4y agoI'm not saying a sprint is required. You were asking why visibility and predictability would be a good idea. Sounds as though I've convinced you!
- js8 4y ago> Sounds as though I've convinced you! Not really.. The PP asked how to do visibility and predictability without sprints. I asked, what do you need it for? You said, they are imposed externally. I said, well, if they are imposed externally, figure out the minimal requirements and do that. No need to do any extra bureacracy, they are not required for SW development process.
- robertlagrant 4y agoI didn't mention extra bureaucracy. I just explained why visibility and predicability are a good idea, which you seem to agree with.