Agile Next Steps (Tax Team)

1.Testing

Alastair to drive the Testing Strategy + catch-up with Sabrina, Chris and the rest of the team to get input on how best to improve our QA strategy

Need to update our existing Test framework epic/feature in Azure (e.g., create new tickets)

Need to prioritize this work effort

Need to dedicate a % capacity each sprint for this work effort

Stephen mentioned that we don’t spend enough time on L0 tests

Need to review our strategy around L0/L1s

Chris indicated that we should discuss about L0s in refinement

Next Action Point: As discussed, we will organize a meeting to break down our testing strategy (e.g.,
testing roadmap) – Kev to set the meeting up in Jan

2.Acceptance Criteria

We’ve made some good progress since our Agile training in October

Stephen mentioned: We still need to improve our acceptance criteria

Need to be more explicit about what needs to be done

Need to add more details into our stories

Need to think about edge cases

We should discuss more about acceptance criteria during refinement

Richard mentioned: We don’t want too detailed acceptance criteria - Need to strike the right balance on the level of details in acceptance criteria.

Mohsen mentioned: Acceptance criteria are not detailed enough

Next Action Points

If we have missed acceptance criteria, we need to understand the reasons why and then
improve. These discussions will now take place as part of the Sprint Retro

In User stories, highlight any acceptance criteria which have been missed out. These can then be discussed in the Retro.

3.Estimation process

We’ve made some good improvement recently (i.e., we now collectively estimate)

Stephen mentioned: we need to break down stories into tasks at a more granular level (more on this below in
capacity planning)

we need to consider L0s when we break items down into tasks

Next Action Points: Collectively agree on reference user stories, which will guide our estimation process (Kev will
help with this)

4.Sprint Review

We’ve started to organize Sprint Reviews (30 minutes session). Received good feedback!

Sprint review happens at 11.30am on the last Friday of the Sprint

4.Capacity Planning

Next Action point: Kev to organize a capacity planning meeting in early Jan

5.Sprint Planning

Next Action point: Break up Sprint planning in two parts. Part 1 (i.e., What) to take place at 9am until
9.30am on the last Friday of the Sprint. Part 2 (i.e., How) will occur at 10.15am until 10.30am. And between 9.30am and 10.15am, we can then break items into tasks. Chris to update meeting. Let’s review this process in January after a couple of sprints (e.g., we may potentially need to allocate more time for planning)

6.Velocity

Next Action point: Kev and Richard to catch up in a 1:1 in early Jan