How to handle work reviews within a sprint

[Shannon Mollenhauer_ PMP_ CSM]

Constrained by a workflow that has these phases: Awaiting Analysis, Analysis, Backlog, In Development, etc.

Team is new to using Jira for agile software development so we haven't figured out all the tricks and tips for incorporating it into our WOW. If our general process is for a BA to hand off an analysis task/issue to a senior dev to review and approve before it goes into the development phase, should we just use the Backlog phase as the holding bucket for that handoff and have the BA assign the senior dev to do the review? Or, do we keep the task in Analysis phase and assign while it's there, letting the dev move it to Backlog if accepted or keeping it in Analysis for further work? How do we account for the estimated points for review? How do we handle work that is ready for dev review on the last day of the sprint?

Should we be using subtasks for the analysis and review so the parent task isn't complete until those separate subs are done?

[Ravi Sagar _Sparxsys_]

Hi @Shannon Mollenhauer_ PMP_ CSM 

Yes you can keep it in the backlog if you want for all the requirements/epics to keep things simple.

Or you can use a separate Kanban board to track all the new requirement with columns like Open > In Review > Approved > Ready for Development

Now your main SCRUM board could be used for delivery where you can only pick epics that are beyond Ready for Development state, where BA/Lead can refine the backlog, prioritise it, do high level estimation.

Do a bit more refinement to the estimates before you start the sprint. You review/testing of stories can be part of the sprint if you want to delivery/release regularly, there can be separate sprints in future for integration testing as well.

Use sub tasks to further break down your stories but story points only at the story level counts and reflected in the reports.

Ravi