# data[].attributes.headline
BA super busy not available to refine defect

# data[].attributes.subject
BA super busy not available to refine defect

# data[].attributes.headline
Plan should flow: DEV->Sit -> test->DEMO-> UAT -> etc

# data[].attributes.subject
Plan should flow: DEV->Sit -> test->DEMO-> UAT -> etc

# data[].attributes.body
this is to reduce number of defect raised

# data[].attributes.body
I am thinking that we can do this directly as I have been a bit of a bottleneck.

# data[].attributes.headline
V. quick turnaround on P1s compared to pre-kanban

# data[].attributes.subject
V. quick turnaround on P1s compared to pre-kanban

# data[].attributes.headline
Single call is sufficient and we have to make sure all the team members has to join

# data[].attributes.subject
Single call is sufficient and we have to make sure all the team members has to join

# data[].attributes.body
Double stand-up work well when it's really required

# data[].attributes.body
Nick - Change stand stand ups to be more focused , build in the morn and QA in the afternoon. Keep to 15 mins

Dem - create a checklist for QAing issues to ensure we know if they are an actual bug or not

Honor - create and assign BAs to relevant areas in spreadsheet so alice knows who to assign tasks too

Ola/Sean - to attach W1 setting progress to UAT plan so UAT team  could only use correct countries (means countries that have been fully set-up) in UAT

TEAM
- ensure we are stricter around what makes a P1
- Use fix deployed to when deploying fixes
- Turn up to meetings on time