# data[].attributes.body
1

# data[].attributes.body
2

# data[].attributes.body
4

# data[].attributes.body
3

# data[].attributes.body
Utilize UI devs more(just a little?) to help testing

# data[].attributes.body
Keep sprint bugs and stories prioritized during sprint

# data[].attributes.body
Always add priorities for bugs

# data[].attributes.body
PM team keeps public view of all customer communciations

# data[].attributes.body
Announcement section at the end of daily standup with what is going on outside of the sprint

# data[].attributes.body
Announce what you plan to work on at end of day

# data[].attributes.body
Pre-publish release notes / product press release

# data[].attributes.body
Vertical Sliced teams - always

# data[].attributes.body
Demo as soon as possible

# data[].attributes.body
Hipchat current sprint room for details after announcements

# data[].attributes.body
Call out individuals during standups

# data[].attributes.body
have dancing video for not paying attention

# data[].attributes.body
weekly task/story grooming

# data[].attributes.body
Communicate with project owner before adding tasks, defects, bugs

# data[].attributes.body
Template for Defects, Bugs, Tasks, etc.

# data[].attributes.body
set max story point allowed

- by features and bugs

# data[].attributes.body
Take on less stories to begin with

# data[].attributes.body
Release Story

- Training, testing, documentation with priorities

# data[].attributes.body
Story ambassador

# data[].attributes.body
Demos during sprint to get feedback - Continuous Feedback

# data[].attributes.body
Cross functional teams for sprint planning (So server and UI tasks are synced)