How to manage timelines in sprint effectively?
- New stories may be affecting previous story design/code - you have certain velocity and that is for new work but your previous work also gets impacted
- So very less time is there for new stories as lot of time is spent in other activities : Backlog grooming for next sprint(I agree PO/BA do that but dev people also send their queries), bug fixes of this sprint , bug fixes of previous production deployed releases, refactoring the existing stories which is impacted with new stories - as you are creating new story - the design also change in database/class here/there.
Any suggestions on how to manage sprint timelines effectively?
Question is broken from the original question as asked by Mark Phillips and CodeGnome