Kanban serves as a useful guide to the agile approach in Business Analysis, unlike the other framework focused on on this platform; Scrum, it does not stipulate specific processes to follow so it is much less of a framework.
Watch Below:
Work In Progress (WIP)
What?
WIP limits determine the maximum amount of work that the team can take on in each status of a workflow.
Why?
- Limiting the amount of WIP reduces the amount of work that is “almost completed” by forcing the team to focus on a smaller set of tasks till completion.
- There is more value to done work than in progress work.
- WIP Limits also highlights bottlenecks early before a situation becomes dire.
How?
The team will initially determine WIP limits for each status and redefine them after monitoring the average number of work items in each status for a few iterations.
Policies
What?
- Set of rules or criteria that team adopts as a guide for moving a user story from “WIP” to done for each status of a workflow.
- Policies are not static, they are living artefacts made visible to remind and guide.
Why?
- Policies guide behavior in order to make the right choices and actions to help assist where multiple individuals are working.
- Helps create clarity if there is conflict on how to go about doing something or if something is done.
How?
Identify policies by asking your team the following type of questions:
- You’ve finished coding a new feature. What do you need to do to make it ready for QA and minimize the possibility of rework?
- You run into an impediment. Who needs to know? How are you going to seek resolution? While you’re waiting, do you start new work or not?
- How do you make sure that bug fixes, etc. are prioritised within their SLA requirements?
BA Agile Framework 