Thank you for your time. We went over the TBB concerns, reviewed possible solutions, review action items with dates. In addition to this, we discussed measures of success on these action items. We agreed to document it by Friday. We reviewed the first eight slides .

Brian stated that we should not create more work for the SDM. Yash stated that the idea is not to make more work or get all the improvement done by the SDM. However, we need SDM's help and involvement to implement solution and new tools. The SDMs will be one of the stakeholders as it cannot be done in vacuum. Yash shared some examples on how we are empowering SDMs by providing additional help. Here are some examples:
• Involved two data scientists to do the ticket analysis
• Involved Moogle team to build online quiz tool - done
• Involved SharePoint developer to build SP KM site on Atos side - done
• Online Kanban TBB board was built and given to the SDM - done
• Offered additional help on Oracle side – in progress
• Providing help to improve team collaboration with the offshore team.

All of the above help came from outside of the TBB team including SDM.

Here are the timeline topics:
1. Implement SharePoint TBB KM site:
Brian raised a question that Atos communicated in 2/16 QBR, that it will be built and deploy Knowledge Management site. He was wondering why it was done in 2two months. We decided to park this question to get additional info. In the meantime, we continued with the action items and timeline:
2. TBB Online Quiz – We agreed to build questions based on our knowledge and run it by BSA to reduce their involvement. TBB is concerned abonut the investment required to build questions on their side.
3. Build, Skill Matrics and Identify Gaps – Since Raj has worked on this , he will put a measure together.
All of the above three items will be measured:
• Yash suggested to conduct a survey before and after using Surevymoney website
Measurement
For IT: Up -to -date Incident Knowledge base since the launch date. This will help IT team to improve resolution time. Overall ticket resolution time will go down.
For Business:
1. Compare before and after Incident resolution time that should be lower than current resolution time.
2. Survey to validate that team members are asking the same information again and again.

3. ITGC Audit - Brian to share the list of ITGC control to conduct audit every 3 months. He indicated that we may need a project to address some of the gaps.
4. CAST – Yash to arrange a demo for Brian.
5. Complete ticket analysis – we will do monthly.
6. Configuration changes (Source Control) Short term – 80% of the code that Atos touches (5 applications) will be in new Visual source safe staging area. Once the code is locked in, we will add build and deployment processes.
Measurement: 100% code in source control with controlled environment.
TFS Long term – put a business case for TBB to depict why we need TFS.
Next steps:
• Document success measures for each Tasks and share with Brian by Friday.
• Schedule a weekly status meeting to review the progress.
• We will share the weekly status report.