Managing the scope of a sprint

During any development life cycle, it is inevitable that at some point there will be a change to the scope of the sprint, either due to last-minute changes to the requirements or by the need to include an urgent bug fix.

In this section, we'll firstly look at how we can change the scope of a sprint by including a newly linked issue to the sprint.

We'll also look at how we can use automation rules to monitor the sprint and notify the team when the scope changes.

Creating a rule to add a linked issue to the sprint

In this example, we are going to make use of the fact that we have both a private internal software development project (My Application with key MAPP) and a public support project (My Application Support with key MAPS) where customers can raise requests and report bugs.

We are also going to assume that we have a team that monitors the public support project and triages incoming requests.

Part of this triage involves...