# data[].attributes.headline
The RTM was a great resource for Managing Gaps. I think we should continue to use that until we reach the burn down and from that point it would be all Feature Requests from the Client

# data[].attributes.subject
The RTM was a great resource for Managing Gaps. I think we should continue to use that until we reach the burn down and from that point it would be all Feature Requests from the Client

# data[].attributes.headline
At the beginning of the project, there wasn't much formal guidance but our team recognized that and worked really well to pull for one another. 

# data[].attributes.subject
At the beginning of the project, there wasn't much formal guidance but our team recognized that and worked really well to pull for one another. 

# data[].attributes.headline
How to present a Roadmap in a clear and consistent manner for future Clients. It would be a good idea to review at a high-level but also maintain a regular schedule of "Here's how the Roadmap applies to you, Ruan/Client." The Client-Specific Roadmap could be viewed monthly or quarterly depending on number of Gaps tied to the client. This would also help them resource plan in case they have any Dev work on their end

# data[].attributes.subject
How to present a Roadmap in a clear and consistent manner for future Clients. It would be a good idea to review at a high-level but also maintain a regular schedule of "Here's how the Roadmap applies to you, Ruan/Client." The Client-Specific Roadmap could be viewed monthly or quarterly depending on number of Gaps tied to the client. This would also help them resource plan in case they have any Dev work on their end

# data[].attributes.headline
We can do a better job of simultaneously tracking Aha and the corresponding JIRA ticket(s). We should outline what is Critical Path to a Phase's Go Live Date

# data[].attributes.subject
We can do a better job of simultaneously tracking Aha and the corresponding JIRA ticket(s). We should outline what is Critical Path to a Phase's Go Live Date

# data[].attributes.body
The entire workflow is inconsistent. The hierarchy of tickets is not the same across initiative/epics. Insufficient information included within the individual stories to understand what work is being completed and how to ensure that it meets acceptance criteria.

# data[].attributes.body
Major issues within the system that block testing are not treated as high priority. Data changes that require a full release or bugs that require 1-2 release cycles to resolve significantly delay testing efforts and lead to putting dates at risk.

# data[].attributes.body
Building relationships and staying in constant communication with a core group between Ruan & Mastery helped keep teams engaged and responsible.

# data[].attributes.body
Being on both Ruan and Prime and seeing the overall project process evolve from Ruan into Prime worked well.
Centralized Information
Tracking ownership
Accountability for tasks

# data[].attributes.body
We still have a ways to go on creating a seamless process for any gaps found. Progress has been made, but some more urgency around timelines would help.

# data[].attributes.body
We are evolving, but the more roles tasks and accountability are defined the faster and more efficient and new project will flow.

# data[].attributes.body
Not only having people assigned to roles, but giving the people in those roles enough bandwidth to be successful without being pulled in 3 different directions or projects would help

# data[].attributes.body
Having a solidified critical path forward from the start that is signed off on. I understand that there will be changes, but having clear answers for all parties involved will likely help to create a seamless process.

# data[].attributes.body
Daily or weekly 15 minute meetings to ensure that all internal teams are aligned on progress. Vastly reduces the number of potential surprises.