Kanban is better, especially paired up with continuous delivery. Once something is done, ship it and move onto something else. Longer research things can be broken down into smaller cards, you're just constantly pulling them in.
We skip estimates, they prove to be useless indicators of when something will be done so why bother? I think our PM's use velocity as a metric (num of cards done over time) and generally plan enough work so we aren't idle.
If you have a weekly grooming session to keep grooming the cards that are next, there shouldn't be wait times.
Waiting for sprint review before moving onto further steps is wasting time which goes against Lean Software Development principles.
We skip estimates, they prove to be useless indicators of when something will be done so why bother? I think our PM's use velocity as a metric (num of cards done over time) and generally plan enough work so we aren't idle.
If you have a weekly grooming session to keep grooming the cards that are next, there shouldn't be wait times.
Waiting for sprint review before moving onto further steps is wasting time which goes against Lean Software Development principles.