# data[].attributes.headline
ADO/VSTS: Suggestion for improved team communication

# data[].attributes.subject
ADO/VSTS: Suggestion for improved team communication

# data[].attributes.body
Suggestions for how we can better use VSTS/ADO to communicate:
1. All team members should "Follow" all user stories in our backlog so they will receive updates (similar to being a stakeholder on an IA ticket). Related: Recommend also Following relevant Shared Services cards.
2. When you have finished a task card, mark it Done AND provide an update in the relevant user story so all team members know the next task can start.

1. People are not getting notifications. Not setting up and following cards.
2. Decentralized communication. Use of task cards for comments (vs the user story card) results in information getting buried.
3. Setup a separate call to dive into this.
4. Agile coach says that team members can assign VSTS/ADO cards to each other if they want, as long as it is not being assigned from SM/PO level.

# data[].attributes.body
Was able to be cross-trained for text versions and manuscripts.

# data[].attributes.body
We have not improved the process for lesson writing and reviews. The reviews were again rushed at the end. Maybe we could start the writing process earlier (before the sprint)?

1. Writers had a lot of competing work to prioritize.
2. Writing includes a lot of research.
3. Research yields a lot of information that has to be prioritized. Objectives are clear, but there is still a lot of information to sort out with the people that we have on the team.
4. May be some opportunity for efficiency by splitting up tasks and starting to work research and writing in parallel.
5. User stories may need to be split up to move reviews to a later sprint.

# data[].attributes.body
The work this sprint was much more distributed.

# data[].attributes.headline
Pressure to complete items timely but other responsibilities are slowing processes. 

# data[].attributes.subject
Pressure to complete items timely but other responsibilities are slowing processes. 

# data[].attributes.body
Felt delayed based on external responsibilities.
1. Unpredictable teacher IA load.
2. Redistribution is not easy because of SME roles.
3. Competing priorities and unclear commitment wrt Agile (60-40??)
4. Escalate as a team concern to address at the program level.

# data[].attributes.body
Communication was awesome this sprint.

# data[].attributes.body
These were still changing halfway through the PI, resulting in a lot of rework for our team.

Program level.

# data[].attributes.headline
Communication not always clear in terms of expectations for graphics workflow

# data[].attributes.subject
Communication not always clear in terms of expectations for graphics workflow

# data[].attributes.body
1. Learning curve with first time with graphics requests process.
2. Uncertainty with process flow as reviews resulted in queries.
3. Opportunity exists in better utilizing comments and other communication. Process was outlined in VSTS cards.
4. Need to monitor.

# data[].attributes.body
Finally getting the hang of VSTS :)

# data[].attributes.body
it felt good to ask other team members for help! :)

# data[].attributes.body
It would benefit everyone if new ideas were discussed in advance and not unexpectedly given to the team to complete.

(IE magazine templates)

# data[].attributes.headline
Be more clear in terms of time frames and estimations of how long something will take. 

# data[].attributes.subject
Be more clear in terms of time frames and estimations of how long something will take. 

# data[].attributes.body
1. Transparency wrt workload and expectations.
2. Unexpected teacher IAs. Estimation of workload was as estimated.

# data[].attributes.body
Collaboration between CD/ID allows lesson writing and asset storyboarding to take place in parallel. This helps ensure that asset development is not lagging until late in the PI.

# data[].attributes.body
Team is eager to help cross-train and answer any questions.

# data[].attributes.body
It might help to consider delays and to add buffer time when setting deadlines to complete work.

# data[].attributes.body
When I finish a task in ADO, it helps to actually assign the next step to the appropriate person. That way, they can go into their personal "Work Items" section and have it right there for them without having to open the whole feature.

# data[].attributes.headline
Working with other members of the team that I had not had the opportunity to have much interaction with up to this point.

# data[].attributes.subject
Working with other members of the team that I had not had the opportunity to have much interaction with up to this point.

# data[].attributes.body
The asset-building process has improved and was spread out during the sprint.

# data[].attributes.body
Team is doing a good job of "rolling with the punches" when things pop up unexpectedly. Trying to make use of the bug feature in VSTS to ensure that we are accounting for the work without expanding the scope of other stories.

# data[].attributes.body
We need to be more careful about "moving goalposts" of user stories. This is appropriate during planning and backlog refinement (as our understanding of scope evolves), but we really should not be bumping out tasks to later sprints as a way of ensuring that a story "gets done" in time.

1. Will ask the Agile coaches for input.

# data[].attributes.headline
Lack of clarity in feature card for Racing Interactive

# data[].attributes.subject
Lack of clarity in feature card for Racing Interactive

# data[].attributes.body
Led to confusion at program level about whether or not the asset is a prototype (final answer: it's not, but it also kind of is).

1. Elevated to the Program Level.