# data[].attributes.body
Team is overloaded on both sides trying to keep up with work required. Management has indicated that additional resources will not be allocated, and it doesn't appear that sprint points actually matter (as we have 300 points for a 2 week sprint compared to other Comply/Sci teams)

# data[].attributes.body
Always adding more tasks and stories at last minute, which have to go through UAT / QA which pushes back deployment

# data[].attributes.body
Team continues to make impressive work with bad requirements / bad data / vague descriptions / tight deadlines

# data[].attributes.body
Still need to get a better understanding of velocity and be more consistent with pointing and release planning

# data[].attributes.body
Please make sure Roko team is part of this as they play a big part in these stories

# data[].attributes.body
All team (Roko+NYC) is very hardworking. Good communication in team (Roko and NYC) that very help to understand requirements.
Again many thanks to each for helping and assistance!

# data[].attributes.headline
Description of Tickets from Customer Support

# data[].attributes.subject
Description of Tickets from Customer Support

# data[].attributes.body
A confusing description of tickets without expexted results. Example, DIG-1232 or DIG-1231 or PTCCFOUR-31617. And to compare with good and understanding description - DIG-1313.

# data[].attributes.body
One story with separate sub-tasks:

for BA

for DEV

for QA

Estimation for each sub-task to can see work-log and velocity each team (BA, DEV, QA).

All comments, specs, examples files will be added to main story to visible (because no one person open each sub-task to check).

Each team (BA, DEV, QA) close own sub-task when finish.

After QA will be finished, QA close own sub-task and assign story to UAT.

# data[].attributes.body
Need to discuss and agree on a "target" point total for Dev/QA.  Everyone should should be aware and use the target during sprint planning.

# data[].attributes.body
Responded very quickly (again) to business request related to infrastructure/performance.

# data[].attributes.headline
Process of story tickets in DIG project is NOT under control of PM. Now when PTCC UI fixes are under roko dev team - we have a conflict when ticket can be created and assigned to Sprint without letting know to PM

# data[].attributes.subject
Process of story tickets in DIG project is NOT under control of PM. Now when PTCC UI fixes are under roko dev team - we have a conflict when ticket can be created and assigned to Sprint without letting know to PM

# data[].attributes.headline
All tickets should go through one channel even if it will not be done by NY DIG team. Product meed to be in the loop since new stories in sprint affect DIG team resources 

# data[].attributes.subject
All tickets should go through one channel even if it will not be done by NY DIG team. Product meed to be in the loop since new stories in sprint affect DIG team resources 