Leadership Profile
Summary
The ten leadership actions taken from the role description (Define, Assess, Align, Delegate, Oversee, Authorize, Mentor, Hire, Report, Evangelize) and the evidence behind each in 2021: sessions led, words from colleagues, projects, and meeting time. Every other page carries the same actions as chips.
Key insights
Actions describe how this work was led. The evidence in the folders shows Define, Assess, Align, Authorize, Mentor, Hire, Report, Evangelize.
They come from the role and responsibilities document (supervisory role). Every session, message, project and meeting in this report carries up to three of them. 433 of 606 meeting hours carry an action; the rest are learning, company events and untitled meetings. The tags describe the type of action, not how well it was performed.
The ten actions
choose one to see what stands behind itMentor
Coaches and teaches people and communities so capability grows beyond the team.
In the role description: Mentors team members, coaches the coaches who deliver through Philips University, and trains software people on new practices.
| Sessions led | 3 | of the 3 sessions Recorded |
| Messages and emails from colleagues | 2 | that describe this action |
| Anytime Feedback reviews | 1 | of 31 written reviews |
| Projects | 4 | · · · |
| Meeting hours | 40 | 51 meetings, from the calendar Recorded |
Meeting time by action
Hours per month, each meeting counted once under its strongest action
Executive Summary
Summary
A one-page account of 2021: the figures that matter most (sessions led, Anytime Feedback, Viva Engage, meeting hours), the actions behind the work, and what came of it.
Key insights
In 2021 I led 3 sessions, and the work shows in what others say: 15 people answered the session feedback forms, 31 colleagues gave Anytime Feedback and 14 chat messages and posts were kept.
Ten leadership actions
records and hours behind eachWhat came of it
Teaching
Sessions led, by series
In the participants' words
Written comments on the feedback forms
The following are the parameters validated by Quality @ Desk- a. Failing Unit Tests (threshold set to 0) b. Reduction in unit-test code-coverage (threshold set to 75%) c. Increase in Code duplication (threshold set to 10%) d.…
We recognized that the time wasted on reworking on several code-quality initiatives was significant. Very often, this resulted into product-quality issues, that demanded costly rework as well. Good examples of these code-quality…
In the past we used to get the feedback related to code quality only during the PR builds. These were the steps for that, Commit the code Raise a pull request Login to jenkin portal Wait for the jenkin job to complete View the…
Projects
Where the year's project work went
Colleagues' recognition
Appreciation emails and messages
In their words
“Very approachable. You were always available and made time to address issues like software quality and automation quality. I really appreciate that you realised others priorities and made time to assist. Your inputs and suggestions have greatly benefitted PS I2M. Initiatives along with SWCoE to evaluate best practicies and compliance and has helped not only the business but also I was able to learn many things on…”
“I worked with Datta on Test ODC project…, Datta is brilliant in analysis and is thought leader. H has contributed to this PIC wide initiative with good insights which helped us in selecting right vendor. He does not shy to be critic of capabilities offered by the partners and always look at how Philips can gain with the partnership we are trying to make with supplier partner.. He has been inspirational leader for…”
“Yes fine. Reverse shadow would be good for interview training & sharing in general I think across Philips maybe to add to bar raisers program. [...] btw, some positive feedback.... one thing I really like about your interview style is that you give just the right amount of time & space for your candidate to show what they can do but without over-running and still covering most of what you wanted to know. [...] Your…”
“It is going really well. The match with my mentor Datta is great. We discussed DevOps way of working and the impact. My mentor presented examples, and the Gemba-event was in particular insightful. The CT-Eye, the visualization and analytics solution for CT, was demonstrated. [...] This is an excellent example of an initiative that drives BizDevOps & Observability. [...] It's been insightful to see how the…”
Learning & Enablement Delivery
Summary
Every training session the folders show Datta delivering in 2021, and the .connect sessions from his record: its date, series, channel, how many people took part where a roster or screenshot says so, and what the participants answered afterwards.
Key insights
The year in sessions
one dot per session, by seriesSeries
Sessions led, with the answers to the feedback forms Recorded
| Series | Sessions | First | Last |
|---|---|---|---|
| Interviewing / Bar Raisers | 1 | 26 Feb | 26 Feb |
| Shift left | 1 | 8 Jun | 8 Jun |
| Virtual Software Excellence Conference 2021 | 1 | 17 Jun | 17 Jun |
How participants scored the sessions
15 responses to "how likely are you to recommend this session", 0 to 10
Every session
3 sessions, with the folder each comes from| Date | Session | Channel | Responses | Average | NPS |
|---|---|---|---|---|---|
| 26 Feb 2021 | Interviewing tips with a partner team | Online session (Menti poll used) | 6 | 9 | 83 |
| 8 Jun 2021 | Less work, more value: why everyone is shifting left (Brazil conference) | Conference session (folder name Brazil Conference) | |||
| 17 Jun 2021 | Observability for customer delight (hands-on) | Virtual Software Excellence Conference, MS Teams |
People: the count on the registration roster or meeting screenshot that the folder holds, as that source states it. Responses, average and NPS come from the feedback form for that day.
The .connect sessions
from the Dattas_Dot_Connects record120 people engaged; the list gives the month only Recorded
13 people engaged Recorded
443 h of meetings with colleagues, 2,975 colleague-meetings; 121 set up by me Recorded
Dot-connects by month
Meetings with colleagues on Software Excellence, from my own monthly exports
By kind, led by me
| Kind | Sessions |
|---|---|
| .connect- General | 2 |
| .connect - CodeDojo | 1 |
| .connect - Quality @ desk | 1 |
| .connect - jscpd | 1 |
By business unit, led by me
| Business unit | Sessions |
|---|---|
| TA | 2 |
| ICAP_SA | 1 |
| PCA | 1 |
| Systems | 1 |
By city, led by me
| City | Sessions |
|---|---|
| Bangalore | 4 |
The 5 .connect sessions led by me, with the team's remarks
| Month | Kind | Business unit | City | Engaged | Remarks |
|---|---|---|---|---|---|
| Jan 2021 | .connect - CodeDojo | ICAP_SA | 5 | Handling Legacy Code - Dojo Session | |
| Jan 2021 | .connect - Quality @ desk | PCA | Bangalore | 1 | PDP 2.0 and Architectural Guardrails |
| Jan 2021 | .connect- General | TA | Bangalore | 2 | Data SW |
| Jan 2021 | .connect- General | Systems | Bangalore | 3 | CodeScene gamification by IGT |
| Jan 2021 | .connect - jscpd | TA | Bangalore | 2 | Exceptions with JSCPD |
Month-by-month figures
| Month | Dot-connects | Set up by me | Hours | Colleague-meetings | Different colleagues | Cities | Most frequent cities |
|---|---|---|---|---|---|---|---|
| 2021-01 | 37 | 9 | 26.5 | 115 | 64 | 11 | Eindhoven, London, Amsterdam, San Diego, Best |
| 2021-02 | 64 | 13 | 51.7 | 331 | 165 | 15 | Eindhoven, Blumenau, Pune, Cambridge, San Diego |
| 2021-03 | 74 | 32 | 50.1 | 269 | 163 | 22 | Eindhoven, Pittsburgh, Cambridge, Bothell, Blumenau |
| 2021-04 | 25 | 1 | 21.5 | 106 | 68 | 9 | Eindhoven, Blumenau, Bothell, Haifa, Amsterdam |
| 2021-05 | 50 | 11 | 39.0 | 230 | 156 | 14 | Bothell, Eindhoven, Best, Boeblingen, San Diego |
| 2021-06 | 46 | 8 | 33.1 | 260 | 147 | 12 | Best, Eindhoven, Bothell, San Diego, Rancho Cordova |
| 2021-07 | 40 | 12 | 26.3 | 197 | 112 | 17 | Eindhoven, Cambridge, San Diego, Rancho Cordova |
| 2021-08 | 51 | 14 | 35.8 | 219 | 138 | 15 | Eindhoven, Best, Blumenau, Aachen, Bothell |
| 2021-09 | 46 | 15 | 38.5 | 297 | 156 | 18 | Eindhoven, Cambridge, Hamburg, Bothell, Haifa |
| 2021-10 | 52 | 3 | 46.9 | 408 | 172 | 18 | Eindhoven, Cambridge, Boeblingen, Blumenau, Haifa |
| 2021-11 | 56 | 47.3 | 381 | 224 | 19 | Eindhoven, Cambridge, Pitsburg, Boeblingen, Haifa | |
| 2021-12 | 34 | 3 | 26.4 | 162 | 108 | 14 | Eindhoven, Cambridge, Amsterdam, Curitiba, Haifa |
The team list gives the month only. Sessions led by me are those whose session lead includes my name. Participants' names and email addresses are not kept.
What participants wrote
63 comments, word for wordQuality at desk helps in reducing the failures found later in the pipeline either in Pull Request/Smoke/Sanity Test/Regression Test. This helps in also reducing the review effort of the architects. For eg. once we deployed quality at desk, we didn't had to worry about compiler warnings, code quality violations , nunit testsetc as that would be caught directly on the build time of the developers and not in the pipeline.
- Getting all code quality matrix while code building itself. No need to wait hours time for TICS report. - Helped to implement Gated Code Quality to maintain current threshold and enhance code quality. - Reduction in CONQ. - Easily tracking for code quality at developer laptop only. - Helping to enhance developer code quality knowledge from PMD reports.
To promote First Time Right quality mind set within the team.
In the past we used to get the feedback related to code quality only during the PR builds. These were the steps for that, Commit the code Raise a pull request Login to jenkin portal Wait for the jenkin job to complete View the report If you get an error related to the any of the code quality related parameters then you need to fix the problem and then go through the same steps that is mentioned above. After the quality at desk integration we are getting the feedback during the local build itself which reduces lot of turnaround time.
We recognized that the time wasted on reworking on several code-quality initiatives was significant. Very often, this resulted into product-quality issues, that demanded costly rework as well. Good examples of these code-quality parameters include the rework on failing unit-tests, decrease in code-coverage, increases in dead-code, increases in duplicated code, increases in Static-Analysis or Compiler warnings, non-adherence to coding-standards, and many more. We felt that we were repeating the efforts on getting our code-quality standards back to where we left them a few weeks / months ago. Hence, we wanted to automate this. This is where the initiative of "Quality At Desk" was created and used thereafter.
Compiler Warnings, Coding Standards, Unit tests
- Code Coverage - Cyclomatic Complexity - Compiler Warning - Coding Standards - Code Duplication - Dead Code - Suppressed Warning
Class Test Functional & Branch Coverage TICS Coding Standard Level 1 - 4 CodeScene Delta Analysis
Coding standards Code duplication Unit test cases Mutation test cases Dead code Compiler warning Static analysis
The following are the parameters validated by Quality @ Desk- a. Failing Unit Tests (threshold set to 0) b. Reduction in unit-test code-coverage (threshold set to 75%) c. Increase in Code duplication (threshold set to 10%) d. Existence of Compiler Warnings e. Existence of c# projects that do not run Static-Code-Analysis f. Existence of c# projects that do not treat Compiler Warnings as errors g. Existence of c# projects that do not treat Static analysis Warnings as errors h. Existence of c# projects that do not use Compiler Warning Level-4 i. Code being committed without a valid and unique review-ID j Existence of Static-Analysis warning-suppression's k. Existence of Compiler-Warning suppression's We are continuing to invest more on increasing the above list.
Compiler Warnings and Coding Standards to ensure that before the code comes for review these basic sanity is already forced upon at developers desk. This saves time both for the reviewer and the developer. Before quality at desk these were either caught in review or in the pull request gating both of which are late in the pipeline and cost time/delay to others
These are the standard code quality practices we follow for our project. These are the ones required for completion of any story/feature with quality.
The quality issues related to above mentioned measures are identified and fixed post delivery and cost more effort to fix compared to time of creation.
Answer is same as provided for the first question. Quality at desk reduces the developer turnaround time to fix issues related to any of the above parameters
More than 2 years ago, the effort estimated on the rework associated with controlling the above code-quality parameters was exceeding 250K USD.
Almost negligible as it is ensured at the build time itself.
- Now we can take code quality details in very less time (from Hours to Minutes) compare to before implementing quality at desk. - Developer then and their itself fix if any code quality issue there.
Separate effort is not reserved for spending in maintaining the measures, it is part of way of working of the team and embedded in the automated processes (pull request build pipeline).
For all of the above mentioned parameters, in total it is reducing about 10% to 15% of the total development time for a typical development scenario.
The time spent on rework associated to the above mentioned parameters is negligible now.
Better quality and time/effort saved in general of the whole team
- Faster code quality feedback. - Code quality improved - Code Review time reduced - Setup Quality as a culture in team - Gates threshold value are helping to improve code quality further and never downward.
The identified measure are automatically maintained by the way of working of the team and explicit effort is not required to maintain the quality.
1. Turnaround time reduction for any development work 2. Most of the development can complete without the network connection, So it reduces network bandwidth (less git commit) 3. Reduces the number of builds needed to complete the development by 30% - 40%. So reduces the load on the build server. 4. Without the internet connection you can complete the development (Specially during WFH scenarios)
Besides the associated effort and cost savings, the quick feedback-loop provided for developers (at their "desk") helped automatically inculcate the necessary disciplines. Furthermore, this helped avoid validating these parameters in the CI pipeline as well, thereby distributing the time spent on the validation of such parameters. However, the biggest gain was seen for product quality wherein several product defects and design-inefficiencies were avoided from being introduced.
Abstract Interpretation and Fortify
- Mutation Coverage - Will be using Cerberus for Cyclomatic instead of JACOCO
Code Duplication Code Size Test Execution Time
Provision to include custom parameters such as Project specific logging rules and gating Project specific coding standards
We would like to validate the c#, c++ project settings, code-review request-quality, unit-test code-quality, modify parameters for similarity analysis, inclusion of Roslyn analyzers, and more.
Critical leaks/violations are caused because of missing Abstract Interpretation/Fortify checks. Right now Abstract Interpretation can be run only on the whole archive and thus takes considerable time and is thus run only nightly. It would be really helpful if this can be run by developers themselves to identify issues and thus gated at desk.
- Mutation coverage will help us to improve our test cases quality. - The main reason to use Cubers as getting all matrix from one framework.
Code Duplication - to promote modular design Code Size - to promote frequent check-ins of small increments Test Execution Time - to keep test at the same level as others in the suite, breach of test pyramid
This would reduce our code review efforts at least by 10%
This is to take our next steps in increasing the disciplines we would like to adhere towards within our teams. If practices are followed ineffectively, the associated gains will be zero or even negative. Hence, we would like to maximize our gains, which can be estimated to an additional 250K USD per year (minimum).
More insights on way of interviewing a candidat4e
1. Assessing the candidates behavioural aspects. 2. How to start the interview
1) How to analyze Behavioral aspects of the candidate 2) Asking 5 why's
How to judge candidates behavioral aspects How to judge candidate is the best fit for the project How to check candidate is proactive
1. How to understand a candidate's team playing abilities 2. How to start an interview 3. Stone walling technique
practices like flip flop, problem solving skills of the candidate,proactive learning based interview techniques
- Behavioral questions - Data Driven than opinion driven
5 WHYs is good technique to start the interview.
1) I will try to analyze behavior of the candidate 2) I will try for some practical questions rather than theoretical questions
5 why technique
Starting an interview, how to also asses the behavior of the candidate while taking a technical interview.
discussing with manager to understand the requirements for the team and role the candidate is interviewed
Overall session covered on all aspects of interview.
Deduplicate test code. Create APIs that have what you want and don't be limited by what you get. Tests should focus on functionality rather than implementation design.
Consider having unit tests focus on behavior rather than structure.
Think of behaviors when coding unit tests Be careful of coupling of unit test implementation to class implementation Write understandable code to help with new joiners
1. Good to see Rhythm code analyzed with other experienced programmers and get feedback. 2. Writing effective unit testing 3. TDD techniques when prototyping before actual design in place.
More often to more folks! We all need to learn this.
Before the meeting, ask participants to have a juicy code examples ready to go.
Wrap up about 10 to 15 minutes before the end of the scheduled time, to debrief and capture action items.
It was little intimidating to see and evaluate code in real time. Preparation before the meeting could have helped by coming with clear agenda and code snippet discussion among internal colleagues before start. (NOTE: It ended really well and learned a lot).
Good dialog using real examples.
Great topics. It took a while to get warmed up with juicy examples, but great discussion overall.
Engaging discussion driven by the participants.
Intimidation went away when it became clear we are here to help each other be better architects of software, and develop even better code that improves quality of Philips products in general but Ultrasound in particular. Experience of Datta, [name] and [name] to guide us and answer our questions was very insightful.
Improving TICS historic trending on Rhythm. Merging best features from TICS and CodeScene. Deep dive into unit test behavior versus structure. Have a walk through of Dependency Injection tools to help manage test seam management at a macro level.
Not at this time.
1. I would like to see good examples from other Philips teams regarding unit tests, TDD or other aspects of software development process like pair programming or extreme programming. 2. Take a concrete example from Ultrasound code base and make improvements while analyzing.
Anytime Feedback & Session Feedback
Summary
What other people said about the work in 2021: Anytime Feedback from 31 colleagues, answers to session feedback forms, emails and Viva Engage comments of thanks, and chat messages kept as screenshots.
Key insights
Everyone who gave Anytime Feedback
31 respondents| # | From | When | Words |
|---|---|---|---|
| 1 | Anonymous respondent | 2021-04-05 | 1056 |
| 2 | Anonymous respondent | 2021-04-12 | 678 |
| 3 | Anonymous respondent | 2021-04-14 | 904 |
| 4 | Steven | Q2-2021 | 927 |
| 5 | Gaurav | Q2-2021 | 901 |
| 6 | Brijesh | Q2-2021 | 795 |
| 7 | Sudeep | Q2-2021 | 848 |
| 8 | Anonymous respondent | Q2-2021 | 532 |
| 9 | Anonymous respondent | Q2-2021 | 665 |
| 10 | Simao | Q2-2021 | 707 |
| 11 | Suyog | Q2-2021 | 329 |
| 12 | Lena | Q2-2021 | 1133 |
| 13 | Aravind | Q2-2021 | 662 |
| 14 | Vishravars | Q2-2021 | 412 |
| 15 | Pankaj | Q2-2021 | 680 |
| 16 | Ian | Q3-2021 | 544 |
| 17 | Elizabeth | Q3-2021 | 418 |
| 18 | David | Q3-2021 | 36 |
| 19 | Nandhini | Q4-2021 | 79 |
| 20 | Prabha | Q4-2021 | 24 |
| 21 | Ashok | Q4-2021 | 458 |
| 22 | Chetan | Q4-2021 | 113 |
| 23 | Richard | Q4-2021 | 103 |
| 24 | Stef | Q4-2021 | 41 |
| 25 | Fernando | Q4-2021 | 20 |
| 26 | Srimathi | Q4-2021 | 39 |
| 27 | Alexandra | Q4-2021 | 99 |
| 28 | Chandra | Q4-2021 | 625 |
| 29 | Satish | Q1-2022 | 117 |
| 30 | Sitangshu | Q4-2021 | 71 |
| 31 | Sundaresan | Q4-2021 | 139 |
Anytime Feedback
31 colleagues repliedWhat colleagues wrote
word for word“Clarity of thought, coding competence, bias to action”
To improve: Articulate the end-goal (like the 'press release' - I guess that's from amazon?) Take on abstract stuff (like PEPF, finance,...) head-on Do and show - lead a piece of real-world refactoring. This is to avoid getting Philipsified :)
“The clarity of the topic is your supreme strength and the way you bring the context for the discussion is commendable.”
To improve: Not anything specific I could think of as I enter feedback. You are doing a great Job!
“Datta has amazing Engagement skills,”
To improve: Knowledge and always moving towards output oriented Approach .
“Collaboration. Datta is approachable and inquisitive and that helps to build engagement.”
To improve: Datta encouraged the team to challenge themselves to try different approaches such as looser coupling of unit tests to the implementation, to focus on the outcome. He encouraged participants to experiment and figure out what techniques work best for them, with the mindset to try something small and see where it takes you.
“The energy you into listening and providing constructive & efficient ways of moving forward with topics.”
To improve: Your doing a great job!
“Eager to improve & inspire : The way visualization, data, metrics, observability etc could be put to better use in improvements.”
To improve: Looking at data, metrics , having KPI driven approach and data to back what is getting discussed are some of the key points i personally got inspired from Datta.
“Clarity of thought, coding competence, bias to action”
To improve: Bar raiser example is there, but I already quoted that last time. Do something like that every quarter :)
“The clarity of the topic is your supreme strength and the way you bring the context for the discussion is commendable.”
To improve: Not anything specific I could think of as I enter feedback. You are doing a great Job!
“Datta has amazing Engagement skills,”
To improve: Knowledge and always moving towards output oriented Approach .
“Calm, credible and knowledgeable. Challenge to status quo while protecting egos. Finding right balance of impatience and longer term persistence. You are great at all of these and have technical breadth and depth that you can demonstrate tangibly to others when needed. A powerful combination!”
“One of the key behaviours that I have learnt from Datta is on how to inspire people to go the extra mile not by coercion or pressure but just by communicating the larger vision and benefits allowing people to enroll themselves. This is a hallmark of great leadership and I have seen it in practice with Datta. Please continue to strengthen and coach people around this.”
To improve: I admire Datta on this behaviour as he has an innate desire to learn, improve and share that with teams. Also, the fact that he keeps it simple, practical and focused on value.
“Some of your key strengths are the efficiency with which you deliver value as well as the commitment and dedication. Furthermore, I would like to highlight your ability to deliver knowledge and adjust your communication and the context based on the audience.”
To improve: Datta shows a really result-driven behavior and enjoys to find solutions to improve the status quo. I can not judge the extend to which he applies LEAN practices in his daily work but he definitely meets expectations in this dimension.
“Good communication skills”
To improve: AOI 1 : - Make your hands dirty by actually implementing things you think through AOI 2 : - Explore , Stabilize, commoditize AOI 3 : - Read , Think, Implement
“Effective communicator and subject knowledge”
To improve: Inner source contributions as examples
“guide teams to improve via connects”
To improve: build your brand, may be articles/blogs in external platforms might help
“You engage with people directly, do not shy away from difficult conversations, don't avoid conflict where it is necessary, but handle it in a way that sensitive to the other party. Technically proficient - remain up-to-date and with hands on experience in the areas we move into.”
“Influencing without authority Effective Communication”
To improve: Exceeds expectations. Have seen Datta suggesting simple and effective solutions to the team. I have this while driving technical connectedness in PM community and during COE assessments. He is able to suggest the next small step forward.
“Data driven analysis and proposals Accountable and taking ownership (e.g., .craft assessments) People orientation (e.g., work on interviews and talent acquisition)”
To improve: More active contribution and presence on Philips InnerSource as a channel/tool to influence more people
“I started interacting with Datta as a part of the WoMentoring program. The way he helped me to identify & refine my goals was an impressive start. His mentorship style of letting the mentee to explore and showing them how he achieved the same was quite helpful and motivating to do better (Ex. How to brand oneself). Also, I have admired his communication skills, the tone and pace of speaking.”
To improve: Please continue to inspithe younger minds by mentoring them.
“- Clarity of thoughts - Drive to excel and make a difference - Eager to improve and inspire”
To improve: Continue with the good work :)
“How Datta Delivers : “Modest” How Datta Leads : “Genuine” How Datta Interacts: “Attentive” How Datta Thinks: “Striving” Above are the best behaviors that Datta portrays IMO and should continue. A very Genuine leader, striving to perform and do his best in almost all opportunities of work where he is either directly or indirectly involved.”
“Very approachable. You were always available and made time to address issues like software quality and automation quality. I really appreciate that you realised others priorities and made time to assist. Your inputs and suggestions have greatly benefitted PS I2M. Initiatives along with SWCoE to evaluate best practicies and compliance and has helped not only the business but also I was able to learn many things on personal front. I liked our collaboration journey this year. We had some healthy discussions over the deployment strategies and they were very fruitful to me.”
To improve: Sorry I do have any points for this section. I feel you have been really supporative and approachable throughout the year.
“Hi Datta, it was great having you as a mentor, I learned a lot from your practice and openness to share. You have a very clear way of presenting things, with a pleasant demeanor, makes for a nice experience engaging with you. I also find that you are eager to make a difference and drive for improvements all the time. A nice example was you engaging in our Research program offsite.”
To improve: Pls continue to go into (for you) unchartered territory, this will stimulate new ideas and learning. Also try to move to new roles every now and then, this will help you grow.
“Great expertise on CI-CD, DevOps, and how to set that up - Reference Architecture. Joins calls/meetings whenever needed.”
To improve: Can be more to the point / adjusting to managerial style of informing. Do not go into implementation details, but give the essence.
“Technical background, listening, business vision, organization”
To improve: For the short time we work together, I miss pairing more in some activities.
“Simplicity... Keep up the good work of supporting ( when asking immediate assistance to sort out the things easily)”
“I started to interact recently with Datta who is helping me create an Onboarding Curricula and Onboarding Journey document for the Software development engineer role and I was impressed with the quick way in which he agreed to help; so constructive. Waw such a refreshing reaction for me specifically as it came in a week when a lot of colleagues were focused on telling me about why things cannot be done! Than once he agreed to help me, things moved very quickly: he create the first draft of the document in a week. Thank you for all this Datta!”
“Very proactive in initiative and with delivery of high standards of work accuracy. With your effective communication, able to manage stakeholders between management & project team.”
“I worked with Datta on Test ODC project…, Datta is brilliant in analysis and is thought leader. H has contributed to this PIC wide initiative with good insights which helped us in selecting right vendor. He does not shy to be critic of capabilities offered by the partners and always look at how Philips can gain with the partnership we are trying to make with supplier partner.. He has been inspirational leader for many in PIC with his deep knowledge on Software excellence and the way he puts across his point is amazing which easily convinces others..”
To improve: He has huge potential and moving to US will give more opportunities to make an further more impact to Philips.
“Datta has great skill to zoom in on a problem and find a solution. His simple way of communication and explanation helps in inspiring and bringing the developers onboard quickly and which is a rare strength these days. Has very good networking and relationship skills.”
To improve: May be one thing would be to create a brand of his own by regularly sharing his knowledge via other mediums and inspiring an wider audience.
“You are an effervescent personality with a winning attitude. An amazing trait is your ability to stay calm and grounded, with your high technical excellence and knowledge. I had the opportunity to work very closely with you and learn lot of things in the technical realm. With your 'team up to win' behavior , i was able to confidently commit on our deliverables [.tune, .connect, Pilot projects, .craft++] and achieve our 2021 targets and goals with flying colors. Thankyou for your hard work , commitment and good contributions.”
To improve: Our team will be growing big in 2022 with increased responsibilities and business commitments. You need to devise additional ways to engage them , both in time zone and challenging pandemic times. Orient new members to be customer facing [customer first / Business first] , seek and address business pain points
Ratings about Datta
from the Dattas_Dot_Connects recordFeedback for Datta - 360 pilot form (Apr 2021)
3 respondents Recorded
| Item | Answers | Mean | Scale |
|---|---|---|---|
| Engagement | 3 | 5 | 1-5 |
| Knowledge | 3 | 4.33 | 1-5 |
| Promptness | 3 | 5 | 1-5 |
| Approachability | 3 | 5 | 1-5 |
| Problem resolution | 3 | 3.67 | 1-5 |
| Leadership | 3 | 4.67 | 1-5 |
2021 Anytime Feedback about Datta (360 Details, Summary and Raw Data…
28 respondents Recorded
| Item | Answers | Mean | Scale |
|---|---|---|---|
| Team up to win | 45 | 4.2 | 1-5 |
| Take ownership & deliver fast | 39 | 4.26 | 1-5 |
| Patient safety, quality & integrity always | 42 | 4.33 | 1-5 |
| Customer First | 36 | 4.36 | 1-5 |
| Eager to improve & inspire | 45 | 4.42 | 1-5 |
| Engagement | 9 | 9.22 | 1-10 |
| Knowledge | 9 | 8.78 | 1-10 |
| Promptness | 9 | 9.56 | 1-10 |
| Approachability | 9 | 9.56 | 1-10 |
| Problem resolution | 9 | 8.33 | 1-10 |
| Leadership | 9 | 9 | 1-10 |
| Work with Datta again | 10 | 9.3 | 1-10 |
| Recommend Datta | 9 | 9.33 | 1-10 |
| Consult Datta for mentoring/coaching | 10 | 9.1 | 1-10 |
Session feedback
15 responses, average 9, NPS 83Every comment is on the page, by series.
Viva Engage
every post and comment from the all-activity page, 2021seen 2,312 times across communities Recorded
on 8 threads
My posts
A post shared to several communities is one row; its views are the sum across them
| Date | Post | Actions | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|---|
| 27 Jan 2021 | The new SW Hiring & Assessment process is live globally! | People Function Community + 1 more | 540 | 14 | 11 | |
| 28 Jan 2021 | Has anyone been able to use the office 365 API's to automate some flows? | Microsoft 365 Users | 186 | 3 | ||
| 2 Mar 2021 | Dear PIC Bangalore community, we need your support: | PIC Bangalore | 192 | 2 | ||
| 2 Mar 2021 | Dear fellow employees, we need your support: | Philips Indian Subcontinent | 144 | |||
| 8 Sept 2021 | How would you avoid duplication of functionality? | the engineering group Software Engineering… | 533 | 1 | 21 | |
| 1 Oct 2021 | Hello everyone, | the engineering group Software Engineering… | 717 | 5 | 30 |
Posts by others where I commented
| Date | Post | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|
| 28 Jan 2021 | Sitangshu: Is Microservices Architecture Shooting up Maintenance and Trouble Shooting effort.. | Philips Innovation Architecture | 199 | 6 | 5 |
| 27 May 2021 | Sundaresan: A warm welcome to all participants. As a reminder, you can post your questions in the Yammer channel and our… | Monthly Technical Sharing… | 209 | 12 |
Chat messages and posts
14 transcribed from screenshots“~ 10 folders were created in our observation duration. Windows keyboard shortcut to creating a folder: control + shift + N [...] Would it be worth considering building a central list of such helpful commands? [...] Would it be worth considering a templatized pull-request to save time? [...] Meeting ended 1h 6m 7:34 PM Wu, Xiangyu 8:11 PM thanks for sharing these tips”
“Nicole Lena Vellal, Dattatreya Caroline Well Done in the PEC Finals presentation ! [...] Nice start... love the stand up setup; O'Reilly and Playlist needs an intro statement; .grow vs share - maybe just skip mention of .share to reduce confusion; Few more seconds on the EES topic/ graph - that is cool! [...] Nicole: thanks!! and thanks for…”
“impactful presentation today in PEC team... proud moment for us [...] thx! hope it came across well we put it together in 5 days and had multiple practice sessions [...] it was great... best part was that all of you had smiles on your face [emoji]”
“Congratulations Pushkar! Good going! [emoji] Pushkaraj 11:44 AM Thank you Datta thanks for guiding me when I needed it 12:18 PM Happy to have helped!”
“Hello Datta, how are you today? Pity we did not make it however I just wanted to share that I really enjoyed the team work the past weeks! Thank you and have a nice week end - when it comes. Thanks Caroline. I share the same feeling. We did a good job in coming together and creating a story in such a short while!”
“Thanks a lot for your time today Saurabh, Santosh. Here are some points I have captured. Timeline of features: Some USPs: How do we capture relevant information so that the decision taken, the information gathered becomes a "look-up" for a feature instead of a "search" [...] Hopefully you can use this to define your current problem statement & why this need is relevant, so…”
“Yes fine. Reverse shadow would be good for interview training & sharing in general I think across Philips maybe to add to bar raisers program. [...] btw, some positive feedback.... one thing I really like about your interview style is that you give just the right amount of time & space for your candidate to show what they can do but without over-running and still covering…”
“Gernot: Really nice, at least I learnd what observability in SW is! David: Yes. And some of the insights of CT systems :-) Thanks guys. Meeting ended 2h 1m”
“Simao 7:51 pm You are welcome. Thanks for your support and hard work!! 7:52 pm You never said "no" to any request I gave you. No matter how crazy the request was or how busy you were. For that I am very grateful. Just hoping you did not burn yourself out too much -- still much to do [emoji]”
“I have 121 with Drew this afternoon to give him news about me but also to talk about the USA comp lead role...... did you already chat with him yet? If not, good opportunity for me to tell him about you (and how talented you are [emoji] ) and that you might be in touch.”
“Hi Datta, Thanks for managing the candidate really well Regds, Gopi”
“It is going really well. The match with my mentor Datta is great. We discussed DevOps way of working and the impact. My mentor presented examples, and the Gemba-event was in particular insightful. The CT-Eye, the visualization and analytics solution for CT, was demonstrated. [...] This is an excellent example of an initiative that drives BizDevOps & Observability. [...] It's…”
“We adjusted our bi-weekly meetings to monthly sessions of an hour, and I would encourage others to make the time as well. This allows for a deeper conversation. [...] Excellent initiative and I totally recommend it. I would also consider group-mentoring [...] Meeting ended 33m47s”
“[Datta, right-aligned] Tejaswini mentioned that we'll not be able to get any interns this year, but can try for one in Aug 2022. I have requested that if any business drops out of internship, then we would be happy to have a conversation with the candidate. [...] I will enroll us for 2022 Aug internship program anyways. Sundaresan: [...] sign-off from Rani - not…”
Capacity & Time Investment
Summary
Where meeting time with colleagues went in 2021, from Datta's own monthly exports: 606 hours of meetings, which leadership actions they served and how the weeks were shaped. The exports are meetings with colleagues, not the whole calendar.
Key insights
Meetings with colleagues in numbers
1 Jan 2021 to 31 Dec 2021 · from my own monthly exports795 meetings, 2.3 h per weekday across 261 weekdays Recorded
12 days had 6 h or more; hours are summed, overlaps are not removed
163 h are other meetings listed in the same exports
Meeting time by leadership action
each meeting counted once, under its strongest actionHours by action
From the meeting title and kind; 173 h in 262 meetings carry no action Estimate
Month by month
Meeting hours per month, by action
Every weekday
hours of meetings per dayBy kind of meeting
Hours by kind, grouped by words in the title Estimate
Month by month
Meeting hours per month, by kind
By weekday
Hours of meetings, Monday to Friday
Largest recurring meetings
Meetings that came back three or more times; individual and small-group meetings are not listed
| Meeting | Times | Hours |
|---|---|---|
| Software Excellence Program- Cont Value Delivery (DevOps Pilots)… | 25 | 24.8 |
| Docker Desktop usage in Philips | 10 | 9.2 |
| Preventive monitoring and alerting Pilot weekly call | 12 | 9.0 |
| GitHub SaaS Global Stakeholder Meeting | 11 | 8.0 |
| SW CoE - OHC Business Progress Dialog | 11 | 5.5 |
| Technical Connectedness - Weekly check-in | 7 | 5.2 |
| SW CoE - a business unit - Business Progress Dialog | 10 | 5.0 |
| SW CoE - a business unit - Business Progress Dialog (Monthly) | 5 | 5.0 |
| a business unit Synergy DevOps Sync up | 8 | 5.0 |
| Philips DevOps CoP : Weekly sync up meeting | 8 | 3.8 |
| Bi weekly- Devops Archi pipeline alignment | 5 | 3.8 |
| SW CoE - HSDP - Business Progress Dialog (Monthly) | 4 | 3.5 |
How this was counted
meetings with colleagues, not the whole calendarSource: Datta's own monthly exports of meetings with colleagues (dot-connects, plus other meetings listed in the 2021 exports). They are not the whole calendar.
The exports hold a date and a length but no start time, so there is no hour-of-day, overlap or time-zone analysis; booked hours are the sum of the meetings' lengths.
A meeting is one date and subject. Days are weekdays; leave and holidays are not known, so working days are all weekdays of the year.
Participants' names, emails and managers are not kept; the exports' organiser is reduced to me, the team account or someone else.
Project Details
Summary
The projects and areas of work in 2021 whose folders show what Datta did: what each one is, when it ran, the leadership actions it shows, and a page for each with facts and figures taken from the documents.
Key insights
The year, project by project
12 projectsEach project
Project pages
choose a project to open its pageTemplatized Black Duck source scan jobs in the AICloud Azure DevOps pipelines (pull request, August 2021)
Aug 2021A pull request in the AICloud Azure DevOps project that creates a templatized job for the Black Duck source scan and invokes it from azure-pipelines.yml, with review comments from colleagues, plus a screenshot of the AICloud project in Black Duck.
What Datta did
- The pull request is shown as raised by Dattatreya Vellal (Datta) from the branch swcoe-devops-pilot into master.
- Datta wrote the pull request description: two things, a templateized job for the Black Duck source scan and its invocation from azure-pipelines.yml.
- Datta replied to review comments, for example that the Docker scan jobs removal was temporary and had been re-enabled.
- Datta pushed a further commit that removed the airgap path and encapsulated it in the step, after a reviewer pointed it out.
- Datta adopted a reviewer's multi-repo checkout suggestion and pointed to the dotnet and node job templates as the example.
Figures
Facts from the documents
- PR title: Docker source scan - templatized job and invocation through azure-pipelines.yml.
- In the template all parameters come through azure-pipelines.yml, so the team controls the branch, the docker image and the Black Duck project name.
- To show reuse across repositories, one dotnet repo scan and one node repo scan were enabled; the docker-image scans were kept intact.
- The change adds a hierarchy of templates and the README.md explains how it works.
- The policy panel shows build succeeded and all comments resolved, with one reviewer blocking at capture time.
- A reviewer asked that the language or ecosystem (npm, dotnet) be taken as a template parameter; Datta answered that the dotnet and node templates now handle it.
- A reviewer asked why the Docker scan jobs were removed, which Datta explained as temporary.
- The reviewer called the encapsulation 'Very good idea' and found a remaining airgappath parameter, which Datta thanked him for and fixed in the step and README.
- The Black Duck screen shows project EDI_AICloud with a Watching Project status and 19 versions.
- The Black Duck project lists docker-image and source components such as algorithm-service-docker-image-1.0.0 and bot-blackduckscan-source-4.0.0.
In colleagues' words
“Very good idea.”