# data[].attributes.body
what do we do that just about hangs together, but needs a lot of improvement?

# data[].attributes.body
what do we do that is pretty solid, but could be improved?

# data[].attributes.body
what do we do that is rock solid?

# data[].attributes.body
Compro and QA Team communicates their progress well and asks questions that helps story refinements (ie. addition to AC)

# data[].attributes.body
Collating/Finalising items to be deployed
YJ IG EM

# data[].attributes.body
Involve Rachel at UX stage

# data[].attributes.body
Both the developers and testers have been great at accomodating  changes/updatets to the tickets that come up during the sprints

# data[].attributes.body
User Story clarifications

# data[].attributes.body
Manav

# data[].attributes.body
Keeping the joint kanban board informative and up-to-date (important for visibility to stakeholders)
MP

# data[].attributes.body
The discussions in standup are very useful. We are able to discuss a lot of queries and we get the answers quickly.

# data[].attributes.body
Allow time for working out cross dependencies
EM

# data[].attributes.headline
Features that Impact the whole CambridgeOne

# data[].attributes.subject
Features that Impact the whole CambridgeOne

# data[].attributes.body
Some track independent features e.g. global navigation was discussed in the past, but it was never priortised. Is it still in backlog?
MP Manav YJ

# data[].attributes.body
Resizing of Failed/Spill-Over User Stories
IG

# data[].attributes.body
IG Manav YJ EM

# data[].attributes.body
- Start looking at Bea's proposal on bug prioritisation. Arrange meeting to discuss this.
- Cluster raised bugs per epic so we would now the timings on when it's needed
- Arrange bug triage meetings

# data[].attributes.body
- deployment meetings within tracks

# data[].attributes.body
- All streams to flag/Tag items related to High Level Navigation OR those abandoned items (without owners)
- Raise these items to the Scrum of Scrums (to create more awareness of these items)