undefined | Better HN

0 pointsrobertlagrant3y ago0 comments

> 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.

0 comments

js83y ago

If 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.

robertlagrantOP3y ago

I'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!

js83y 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.

1 more reply

j / k navigate · click thread line to collapse

0 pointsrobertlagrant3y ago0 comments

> OK, I take it your answer for visibility is management reporting, I am not sure about predictability

0 comments

js83y ago

If 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.

robertlagrantOP3y ago

I'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!

js83y ago

> Sounds as though I've convinced you!

1 more reply

j / k navigate · click thread line to collapse