# data[].attributes.headline
Respect others' time by not extending our internal meeting always (Mythili)

# data[].attributes.subject
Respect others' time by not extending our internal meeting always (Mythili)

# data[].attributes.body
We always slip off the agenda and we always taken the time for granted of team and always extended our meeting slots. We should plan for sequential sessions if we need to discuss further.

# data[].attributes.headline
We have a process but not being followed

# data[].attributes.subject
We have a process but not being followed

# data[].attributes.body
My observation for application onboarding approach / process has been documented but I don't believe we have followed them at all. Moving forward, it would be better to follow our own process

# data[].attributes.body
Better planning of what is realistic the team can accomplish without making commitments that cannot be met

# data[].attributes.body
Like bulk joiners, now we are also getting bulk expiry notifications for contractors, this could've been thought through to compile the users according to managers and send them in one email per manager. Good thing we are routing to the mailbox now, but imagine if it opens up to public and each manager would be getting 100+ emails from us in a day.
Priyanga

# data[].attributes.body
Data quality issues in higher environment did bring up many unknown issues that had it they existed in lower environments would have helped us address them soon. It will be a good idea to do thorough testing in stage. - Dipankar

# data[].attributes.headline
Stop and rethink when we are changing the user experience. The decision should be well documented in such scenarios and proper sign offs to be captured. 

# data[].attributes.subject
Stop and rethink when we are changing the user experience. The decision should be well documented in such scenarios and proper sign offs to be captured. 

# data[].attributes.body
some sort of automation or CI/CD pipelines should have been considered or set up before/during the project phase. that would have really helped deployment dependencies and time.

# data[].attributes.headline
Planning sessions to involve all the team members (Mythili)

# data[].attributes.subject
Planning sessions to involve all the team members (Mythili)

# data[].attributes.body
We had not involved or informed our implementation vendors when we planned for our releases, which would cause deviation in plan later because of the feasibility aspects of what is planned for a taken release. Also QA was not involved in but they raised concerns that the time wasn;t sufficient for testing etc. So, I believe we should involve everyone in our release plans so everyone knows the efforts involved and can vote for the plan and proceed without deviation in actual plan.

# data[].attributes.headline
Proper traceability on activities in conjunction with requirements

# data[].attributes.subject
Proper traceability on activities in conjunction with requirements

# data[].attributes.body
Traceability could have been easier if we do proper tracing from design, dev, testing back to requirements to easily identify future releases.

# data[].attributes.body
Time constraints can cause a lack of quality. The team cannot do better without being given enough time.
L

# data[].attributes.body
Participation on all team members to have an alignment is the key to have a universal understanding and communication to outside stakeholders. There were times that this has caused issues and confusion from stakeholders as we were providing different input to them.

# data[].attributes.body
In Future, if we can have requirements tagged as if they are existing standard driven or new standard IAM team is trying to enforce, we will get better buy in from application teams as well as internally. This will also help us to prioritize which are to be met or not for later. - Dipankar

# data[].attributes.body
Better communication with stakeholders so they understand the objective of meetings and leave the meeting knowing what is in it for them

# data[].attributes.body
additional permission for Ops to perform more tasks on the dev/lower environments such as creating users/ id for testing purposes. instead of relying on another team. We could have had the process sorted out before the start of the project.

# data[].attributes.body
Even though there were a lot of instances where the team was stressed out on the deliverables and trying to catch up on outstanding activities, the Management team always noticed them and rewarded the team with great appreciation.

# data[].attributes.headline
Proper regression testing should be completed for each releases. Be it minor or major release.

# data[].attributes.subject
Proper regression testing should be completed for each releases. Be it minor or major release.

# data[].attributes.body
In the project mode, quality of work overall has been compromise due to lack of time in properly executing them. I believe a better strategy and planning can be improve and thoroughly consider realistic delivery vs good on paper only.

# data[].attributes.headline
Strategy to discover all involved processes on application side (Mythili)

# data[].attributes.subject
Strategy to discover all involved processes on application side (Mythili)

# data[].attributes.body
We should find a way to understand the process better on any application side so we do not miss out on some requirements. Example of re-org in the People team's process; We did not realize it earlier to releasing our certifications to managers and we started receiving whole big number of certs to managers for the re-orgs too. We need to strategize on discovering the processes on the application side. (Bulk-joiners in Employees is another example that we missed out on)

# data[].attributes.body
Team should be aware of implementation success or failure the same day it occurs to keep in the loop.
Laurie

# data[].attributes.body
There has been a great support from leadership team in terms of providing direction, address roadblocks and prioritize the work streams.

# data[].attributes.body
Complete the requirement traceability after each release rather than at the end of the project.

# data[].attributes.body
Overall, everything was good. Few issues here and there from what was observed, every team faces, no matter how planned a team is. Communication wise we have improved leaps and bounds but still needs to be improved further. Also always more time could've been planned around the releases to not feel rushed, but get that we were on a schedule.
Priyanga

# data[].attributes.body
Proper structure e.g. Agendas, people

# data[].attributes.body
Since we have very highly manual activities being done simultaneously, we have to be very thorough in our work without compromising efficiency. Delegating some tasks is also very helpful in ensuring that things are getting done on time so we can also work on other things. -KM

# data[].attributes.headline
Seggregating our environments only added more complexity and we have made many exceptions to meet project deadline which invalidated the true intent of it.

# data[].attributes.subject
Seggregating our environments only added more complexity and we have made many exceptions to meet project deadline which invalidated the true intent of it.

# data[].attributes.body
More input and attention from tech team when reviewing requirements instead of the input being given much later causing rework. Requirements should not come from only BAs.
Laurie

# data[].attributes.body
Breakdown the requirements per release to avoid tagging/untagging process that is time consuming

# data[].attributes.body
There were tons of scenarios throughout the project where requirements were not looked at that causes ambiguity. It would be great if step does not ever get missed.

# data[].attributes.headline
Get thorough through our licenses (Mythili)

# data[].attributes.subject
Get thorough through our licenses (Mythili)

# data[].attributes.body
We did not realize our PAM module license within SailPoint and we have had a different mindset altogether as to implement the integration between SailPoint & CyberArk. So, we must be thorough through our license on what all we acquired already.

# data[].attributes.body
The team was very good at coordinating and helping out each other at every critical situation and made things work.

# data[].attributes.body
(Suggestion) - Ops to communicate to the team in teams channel/email once a release or fix is implemented on Prod

-Cema

# data[].attributes.body
Before a release proper impact assessment is required and should have a structure e.g. impact was discovered on or after implementation

# data[].attributes.body
Understanding what our basic requirement needs  are e.g., application patterns, questionnaire before reaching out to application teams to prevent going in circles.