Question about scope change in Jira

[Егор Козлов]

Hello guys,

Maybe someone can help me))

How many issues (epics, task sits, etc) I can add in a sprint without scope changes even if I'll not estimate them in story point? And how does Jira calculate it?

Thak you🙏

[Dave Mathijs]

Hi @Егор Козлов , welcome to the Atlassian Community!

Adding any issue to an active sprint is scope change. Furthermore, issues should not be added to a sprint unestimated.

That defeats the purpose of all agile reports.

So my answer would be: None.

[Fabio Racobaldo _Herzum_]

Hi @Егор Козлов ,

welcome to the Atlassian community!

For agile purposes, you could estimate activity in story points/remaining time. Scope change means that something happens to your sprint (new activity added/removed). Based on that change also the estimation, in story points / remaining time) should change.

There are no limit for scope change, btw if the change is so big you should close the sprint and planning a new one with the desired scope.

Hope this helps,

Fabio

[G subramanyam]

Hi @Егор Козлов welcome to Atlassian community.

Their are not restrictions on the number of issues (issue type) to add to a Sprint. And the second part of your question about Scope change is incorrect.

Before start of the Sprint or during the Sprint progress, you can add as many as you want provided your management doesn't give emphasis on scope change parameter.