How to add a pointed story to an active sprint without scope creep

[Ron West]

(Searched and couldn't find the answer -- so sorry if been asked before).

We do the standard 2 week sprint. Every developer commits to X (usually 21) story points. 

But there are times when the individuals finish their committed work in this active sprint and (in conjunction with our product team) start working on stories that were targeted for the next sprint.

How can I bring these stories into the current active sprint without making the burndown chart look like we creeped scope?

One option was to create an unpointed empty story and change the existing story to become a sub-task -- which is messy if the existing story already had sub-tasks.

[Lenin Raj]

Hi @Ron West 

I think this scenario isn't possible. Does keeping 0 story points until the current sprint is complete and then updating the story point work for you?

[Ron West]

I guess we can try. It just means we will lose the initial estimate for the picked up story.