Software Excellence Competency Lead, Software Engineering · 1 Jan 2021 to 31 Dec 2021
Dattatreya Subramanya Vellal

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 it

Mentor

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 led3of the 3 sessions Recorded
Messages and emails from colleagues2that describe this action
Anytime Feedback reviews1of 31 written reviews
Projects4 · · ·
Meeting hours4051 meetings, from the calendar Recorded

Meeting time by action

Hours per month, each meeting counted once under its strongest action

JanFebMarAprMayJunJulAugSepOctNovDec
DefineAssessAlignDelegateOverseeAuthorizeMentorHireReportEvangelize

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.

3 sessions  83 NPS
15 responses, averaging 9/10.
Promoters 5Passives 1Detractors 0
31 colleagues
wrote to me through Anytime Feedback
575 dot-connects
meetings with colleagues on Software Excellence, 443 h in all · 17 .connect sessions in the team list
14
messages of thanks from emails, Viva Engage comments and chats
Email or Viva Engage commentChat message
6 posts  2,312 views
seen 2,312 times across communities
Views per post of mine
606 h
in meetings with colleagues, from my monthly exports
Meeting hours per month

Ten leadership actions

records and hours behind each

What came of it

Teaching

Sessions led, by series

MentorEvangelize
Interviewing / Bar Raisers1 sessionsShift left1 sessionsVirtual Software Excellence…1 sessions

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.…
Shift left quality (quality-at-desk), 10 Feb
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…
Shift left quality (quality-at-desk), 10 Feb
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…
Shift left quality (quality-at-desk), 10 Feb

Projects

Where the year's project work went

Aug 2021 to Aug 2021
Jan 2021 to Feb 2021
Nov 2020 to May 2021
Jan 2021 to Mar 2021
Feb 2021 to Dec 2021
Feb 2021 to Nov 2021
May 2021 to Oct 2021

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…”

Chetan

“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…”

Satish

“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…”

Simao

“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…”

Mariélle

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 series
JanFebMarAprMayJunJulAugSepOctNovDec
Interviewing / Bar RaisersShift leftVirtual Software Excellence Conference…Dot size grows with the participant count where one is stated

Series

Sessions led, with the answers to the feedback forms Recorded

3 rows
SeriesSessionsFirstLast
Interviewing / Bar Raisers126 Feb26 Feb
Shift left18 Jun8 Jun
Virtual Software Excellence Conference 2021117 Jun17 Jun

How participants scored the sessions

15 responses to "how likely are you to recommend this session", 0 to 10

012345671893102
Promoters, 9 and 10 (5)Passives, 7 and 8 (1)Detractors, 6 and below (0)
9
average
83
NPS

Every session

3 sessions, with the folder each comes from
3 rows
DateSessionChannelResponsesAverageNPS
26 Feb 2021Interviewing tips with a partner teamOnline session (Menti poll used)6983
8 Jun 2021Less work, more value: why everyone is shifting left (Brazil conference)Conference session (folder name Brazil Conference)
17 Jun 2021Observability 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 record
17.connect sessions in the team list

120 people engaged; the list gives the month only Recorded

5led by me

13 people engaged Recorded

575dot-connects

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

37Jan64Feb74Mar25Apr50May46Jun40Jul51Aug46Sep52Oct56Nov34Dec

By kind, led by me

4 rows
KindSessions
.connect- General2
.connect - CodeDojo1
.connect - Quality @ desk1
.connect - jscpd1

By business unit, led by me

4 rows
Business unitSessions
TA2
ICAP_SA1
PCA1
Systems1

By city, led by me

CitySessions
Bangalore4
The 5 .connect sessions led by me, with the team's remarks
5 rows
MonthKindBusiness unitCityEngagedRemarks
Jan 2021.connect - CodeDojoICAP_SA5Handling Legacy Code - Dojo Session
Jan 2021.connect - Quality @ deskPCABangalore1PDP 2.0 and Architectural Guardrails
Jan 2021.connect- GeneralTABangalore2Data SW
Jan 2021.connect- GeneralSystemsBangalore3CodeScene gamification by IGT
Jan 2021.connect - jscpdTABangalore2Exceptions with JSCPD
Month-by-month figures
12 rows
MonthDot-connectsSet up by meHoursColleague-meetingsDifferent colleaguesCitiesMost frequent cities
2021-0137926.51156411Eindhoven, London, Amsterdam, San Diego, Best
2021-02641351.733116515Eindhoven, Blumenau, Pune, Cambridge, San Diego
2021-03743250.126916322Eindhoven, Pittsburgh, Cambridge, Bothell, Blumenau
2021-0425121.5106689Eindhoven, Blumenau, Bothell, Haifa, Amsterdam
2021-05501139.023015614Bothell, Eindhoven, Best, Boeblingen, San Diego
2021-0646833.126014712Best, Eindhoven, Bothell, San Diego, Rancho Cordova
2021-07401226.319711217Eindhoven, Cambridge, San Diego, Rancho Cordova
2021-08511435.821913815Eindhoven, Best, Blumenau, Aachen, Bothell
2021-09461538.529715618Eindhoven, Cambridge, Hamburg, Bothell, Haifa
2021-1052346.940817218Eindhoven, Cambridge, Boeblingen, Blumenau, Haifa
2021-115647.338122419Eindhoven, Cambridge, Pitsburg, Boeblingen, Haifa
2021-1234326.416210814Eindhoven, 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 word
Quality 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.
Shift left quality (quality-at-desk), 10 Feb · Why did you opt into choosing quality-at-desk? (Can you please help give concrete business examples which pushed you to opt into this?)
- 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.
Shift left quality (quality-at-desk), 10 Feb · Why did you opt into choosing quality-at-desk? (Can you please help give concrete business examples which pushed you to opt into this?)
To promote First Time Right quality mind set within the team.
Shift left quality (quality-at-desk), 10 Feb · Why did you opt into choosing quality-at-desk? (Can you please help give concrete business examples which pushed you to opt into this?)
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.
Shift left quality (quality-at-desk), 10 Feb · Why did you opt into choosing quality-at-desk? (Can you please help give concrete business examples which pushed you to opt into this?)
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.
Shift left quality (quality-at-desk), 10 Feb · Why did you opt into choosing quality-at-desk? (Can you please help give concrete business examples which pushed you to opt into this?)
Compiler Warnings, Coding Standards, Unit tests
Shift left quality (quality-at-desk), 10 Feb · What measure did you choose to observe and gate via quality-at-desk? (eg: Coding standards, duplication etc.)
- Code Coverage - Cyclomatic Complexity - Compiler Warning - Coding Standards - Code Duplication - Dead Code - Suppressed Warning
Shift left quality (quality-at-desk), 10 Feb · What measure did you choose to observe and gate via quality-at-desk? (eg: Coding standards, duplication etc.)
Class Test Functional & Branch Coverage TICS Coding Standard Level 1 - 4 CodeScene Delta Analysis
Shift left quality (quality-at-desk), 10 Feb · What measure did you choose to observe and gate via quality-at-desk? (eg: Coding standards, duplication etc.)
Coding standards Code duplication Unit test cases Mutation test cases Dead code Compiler warning Static analysis
Shift left quality (quality-at-desk), 10 Feb · What measure did you choose to observe and gate via quality-at-desk? (eg: Coding standards, duplication etc.)
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.
Shift left quality (quality-at-desk), 10 Feb · What measure did you choose to observe and gate via quality-at-desk? (eg: Coding standards, duplication etc.)
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
Shift left quality (quality-at-desk), 10 Feb · Why did you select these specific measures? Can you help quantify some of these measures before adopting quality-at-desk?
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.
Shift left quality (quality-at-desk), 10 Feb · Why did you select these specific measures? Can you help quantify some of these measures before adopting quality-at-desk?
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.
Shift left quality (quality-at-desk), 10 Feb · Why did you select these specific measures? Can you help quantify some of these measures before adopting quality-at-desk?
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
Shift left quality (quality-at-desk), 10 Feb · Why did you select these specific measures? Can you help quantify some of these measures before adopting quality-at-desk?
More than 2 years ago, the effort estimated on the rework associated with controlling the above code-quality parameters was exceeding 250K USD.
Shift left quality (quality-at-desk), 10 Feb · Why did you select these specific measures? Can you help quantify some of these measures before adopting quality-at-desk?
Almost negligible as it is ensured at the build time itself.
Shift left quality (quality-at-desk), 10 Feb · After adopting quality-at-desk, how much time are you spending now, for each of the identified measures?
- 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.
Shift left quality (quality-at-desk), 10 Feb · After adopting quality-at-desk, how much time are you spending now, for each of the identified measures?
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).
Shift left quality (quality-at-desk), 10 Feb · After adopting quality-at-desk, how much time are you spending now, for each of the identified measures?
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.
Shift left quality (quality-at-desk), 10 Feb · After adopting quality-at-desk, how much time are you spending now, for each of the identified measures?
The time spent on rework associated to the above mentioned parameters is negligible now.
Shift left quality (quality-at-desk), 10 Feb · After adopting quality-at-desk, how much time are you spending now, for each of the identified measures?
Better quality and time/effort saved in general of the whole team
Shift left quality (quality-at-desk), 10 Feb · What were your biggest benefits/gains of adopting quality-at-desk?
- 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.
Shift left quality (quality-at-desk), 10 Feb · What were your biggest benefits/gains of adopting quality-at-desk?
The identified measure are automatically maintained by the way of working of the team and explicit effort is not required to maintain the quality.
Shift left quality (quality-at-desk), 10 Feb · What were your biggest benefits/gains of adopting quality-at-desk?
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)
Shift left quality (quality-at-desk), 10 Feb · What were your biggest benefits/gains of adopting quality-at-desk?
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.
Shift left quality (quality-at-desk), 10 Feb · What were your biggest benefits/gains of adopting quality-at-desk?
Abstract Interpretation and Fortify
Shift left quality (quality-at-desk), 10 Feb · What are some potential measures you would like to observe in the future?
- Mutation Coverage - Will be using Cerberus for Cyclomatic instead of JACOCO
Shift left quality (quality-at-desk), 10 Feb · What are some potential measures you would like to observe in the future?
Code Duplication Code Size Test Execution Time
Shift left quality (quality-at-desk), 10 Feb · What are some potential measures you would like to observe in the future?
Provision to include custom parameters such as Project specific logging rules and gating Project specific coding standards
Shift left quality (quality-at-desk), 10 Feb · What are some potential measures you would like to observe in the future?
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.
Shift left quality (quality-at-desk), 10 Feb · What are some potential measures you would like to observe in the future?
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.
Shift left quality (quality-at-desk), 10 Feb · Why would you like to measure these specific measures? (What is the business gain? Ballpark quantification would be very helpful).
- Mutation coverage will help us to improve our test cases quality. - The main reason to use Cubers as getting all matrix from one framework.
Shift left quality (quality-at-desk), 10 Feb · Why would you like to measure these specific measures? (What is the business gain? Ballpark quantification would be very helpful).
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
Shift left quality (quality-at-desk), 10 Feb · Why would you like to measure these specific measures? (What is the business gain? Ballpark quantification would be very helpful).
This would reduce our code review efforts at least by 10%
Shift left quality (quality-at-desk), 10 Feb · Why would you like to measure these specific measures? (What is the business gain? Ballpark quantification would be very helpful).
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).
Shift left quality (quality-at-desk), 10 Feb · Why would you like to measure these specific measures? (What is the business gain? Ballpark quantification would be very helpful).
More insights on way of interviewing a candidat4e
Interviewing tips - an interactive session with Datta, 26 Feb · What were you three top learnings from this discussions?
1. Assessing the candidates behavioural aspects. 2. How to start the interview
Interviewing tips - an interactive session with Datta, 26 Feb · What were you three top learnings from this discussions?
1) How to analyze Behavioral aspects of the candidate 2) Asking 5 why's
Interviewing tips - an interactive session with Datta, 26 Feb · What were you three top learnings from this discussions?
How to judge candidates behavioral aspects How to judge candidate is the best fit for the project How to check candidate is proactive
Interviewing tips - an interactive session with Datta, 26 Feb · What were you three top learnings from this discussions?
1. How to understand a candidate's team playing abilities 2. How to start an interview 3. Stone walling technique
Interviewing tips - an interactive session with Datta, 26 Feb · What were you three top learnings from this discussions?
practices like flip flop, problem solving skills of the candidate,proactive learning based interview techniques
Interviewing tips - an interactive session with Datta, 26 Feb · What were you three top learnings from this discussions?
- Behavioral questions - Data Driven than opinion driven
Interviewing tips - an interactive session with Datta, 26 Feb · From this conversation - what tips/techniques will you adopt in your interviewing style?
5 WHYs is good technique to start the interview.
Interviewing tips - an interactive session with Datta, 26 Feb · From this conversation - what tips/techniques will you adopt in your interviewing style?
1) I will try to analyze behavior of the candidate 2) I will try for some practical questions rather than theoretical questions
Interviewing tips - an interactive session with Datta, 26 Feb · From this conversation - what tips/techniques will you adopt in your interviewing style?
5 why technique
Interviewing tips - an interactive session with Datta, 26 Feb · From this conversation - what tips/techniques will you adopt in your interviewing style?
Starting an interview, how to also asses the behavior of the candidate while taking a technical interview.
Interviewing tips - an interactive session with Datta, 26 Feb · From this conversation - what tips/techniques will you adopt in your interviewing style?
discussing with manager to understand the requirements for the team and role the candidate is interviewed
Interviewing tips - an interactive session with Datta, 26 Feb · From this conversation - what tips/techniques will you adopt in your interviewing style?
Overall session covered on all aspects of interview.
Interviewing tips - an interactive session with Datta, 26 Feb · [Optional] What else can we do to add value to this conversation/topic/concern? (Think about other conversations/workshops/roleplays we can have, other ways in which we can improve interviewing with P
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.
Feedback about today's conversation, 19 Mar · [Optional] What three key points did you take away as your key learning from today's discussion?
Consider having unit tests focus on behavior rather than structure.
Feedback about today's conversation, 19 Mar · [Optional] What three key points did you take away as your key learning from today's discussion?
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
Feedback about today's conversation, 19 Mar · [Optional] What three key points did you take away as your key learning from today's discussion?
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.
Feedback about today's conversation, 19 Mar · [Optional] What three key points did you take away as your key learning from today's discussion?
More often to more folks! We all need to learn this.
Feedback about today's conversation, 19 Mar · [Optional] From today's conversation, what suggestions do you have to improve sessions of this sort?
Before the meeting, ask participants to have a juicy code examples ready to go.
Feedback about today's conversation, 19 Mar · [Optional] From today's conversation, what suggestions do you have to improve sessions of this sort?
Wrap up about 10 to 15 minutes before the end of the scheduled time, to debrief and capture action items.
Feedback about today's conversation, 19 Mar · [Optional] From today's conversation, what suggestions do you have to improve sessions of this sort?
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).
Feedback about today's conversation, 19 Mar · [Optional] From today's conversation, what suggestions do you have to improve sessions of this sort?
Good dialog using real examples.
Feedback about today's conversation, 19 Mar · [Optional] What went well in this conversation?
Great topics. It took a while to get warmed up with juicy examples, but great discussion overall.
Feedback about today's conversation, 19 Mar · [Optional] What went well in this conversation?
Engaging discussion driven by the participants.
Feedback about today's conversation, 19 Mar · [Optional] What went well in this conversation?
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.
Feedback about today's conversation, 19 Mar · [Optional] What went well in this conversation?
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.
Feedback about today's conversation, 19 Mar · [Optional] Are there other topics that you'd like SWCoE to follow-up on?
Not at this time.
Feedback about today's conversation, 19 Mar · [Optional] Are there other topics that you'd like SWCoE to follow-up on?
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.
Feedback about today's conversation, 19 Mar · [Optional] Are there other topics that you'd like SWCoE to follow-up on?

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
31 rows
#FromWhenWords
1Anonymous respondent2021-04-051056
2Anonymous respondent2021-04-12678
3Anonymous respondent2021-04-14904
4StevenQ2-2021927
5GauravQ2-2021901
6BrijeshQ2-2021795
7SudeepQ2-2021848
8Anonymous respondentQ2-2021532
9Anonymous respondentQ2-2021665
10SimaoQ2-2021707
11SuyogQ2-2021329
12LenaQ2-20211133
13AravindQ2-2021662
14VishravarsQ2-2021412
15PankajQ2-2021680
16IanQ3-2021544
17ElizabethQ3-2021418
18DavidQ3-202136
19NandhiniQ4-202179
20PrabhaQ4-202124
21AshokQ4-2021458
22ChetanQ4-2021113
23RichardQ4-2021103
24StefQ4-202141
25FernandoQ4-202120
26SrimathiQ4-202139
27AlexandraQ4-202199
28ChandraQ4-2021625
29SatishQ1-2022117
30SitangshuQ4-202171
31SundaresanQ4-2021139

Anytime Feedback

31 colleagues replied

What 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.

Steven

“The energy you into listening and providing constructive & efficient ways of moving forward with topics.”

To improve: Your doing a great job!

Gaurav

“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.

Brijesh Report

“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 :)

Sudeep

“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!”

Simao

“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.

Suyog

“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.

Lena

“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

Aravind

“Effective communicator and subject knowledge”

To improve: Inner source contributions as examples

Vishravars

“guide teams to improve via connects”

To improve: build your brand, may be articles/blogs in external platforms might help

Pankaj

“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.”

Ian

“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.

Elizabeth

“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

David AssessHire

“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.

Nandhini Mentor

“- Clarity of thoughts - Drive to excel and make a difference - Eager to improve and inspire”

To improve: Continue with the good work :)

Prabha

“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.”

Ashok

“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.

Chetan

“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.

Richard

“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.

Stef

“Technical background, listening, business vision, organization”

To improve: For the short time we work together, I miss pairing more in some activities.

Fernando

“Simplicity... Keep up the good work of supporting ( when asking immediate assistance to sort out the things easily)”

Srimathi

“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!”

Alexandra

“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.”

Chandra

“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.

Satish

“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.

Sitangshu

“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

Sundaresan

Ratings about Datta

from the Dattas_Dot_Connects record

Feedback for Datta - 360 pilot form (Apr 2021)

3 respondents Recorded

6 rows
ItemAnswersMeanScale
Engagement351-5
Knowledge34.331-5
Promptness351-5
Approachability351-5
Problem resolution33.671-5
Leadership34.671-5

2021 Anytime Feedback about Datta (360 Details, Summary and Raw Data…

28 respondents Recorded

14 rows
ItemAnswersMeanScale
Team up to win454.21-5
Take ownership & deliver fast394.261-5
Patient safety, quality & integrity always424.331-5
Customer First364.361-5
Eager to improve & inspire454.421-5
Engagement99.221-10
Knowledge98.781-10
Promptness99.561-10
Approachability99.561-10
Problem resolution98.331-10
Leadership991-10
Work with Datta again109.31-10
Recommend Datta99.331-10
Consult Datta for mentoring/coaching109.11-10

Session feedback

15 responses, average 9, NPS 83
9/ 10
average recommend score
83NPS
5 promoters, 1 passives, 0 detractors
3forms
63 written comments

Every comment is on the page, by series.

Viva Engage

every post and comment from the all-activity page, 2021
6posts by me

seen 2,312 times across communities Recorded

3comments and replies by me

on 8 threads

My posts

A post shared to several communities is one row; its views are the sum across them

6 rows
DatePostActionsCommunitySeen byReactionsComments
27 Jan 2021The new SW Hiring & Assessment process is live globally!
Hire
People Function Community + 1 more5401411
28 Jan 2021Has anyone been able to use the office 365 API's to automate some flows?
Microsoft 365 Users1863
2 Mar 2021Dear PIC Bangalore community, we need your support:
HireEvangelize
PIC Bangalore1922
2 Mar 2021Dear fellow employees, we need your support:
Hire
Philips Indian Subcontinent144
8 Sept 2021How would you avoid duplication of functionality?
the engineering group Software Engineering…533121
1 Oct 2021Hello everyone,
the engineering group Software Engineering…717530

Posts by others where I commented

2 rows
DatePostCommunitySeen byReactionsComments
28 Jan 2021Sitangshu: Is Microservices Architecture Shooting up Maintenance and Trouble Shooting effort..
Philips Innovation Architecture19965
27 May 2021Sundaresan: A warm welcome to all participants. As a reminder, you can post your questions in the Yammer channel and our…
Monthly Technical Sharing…20912

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”

Datta · Teams meeting chat '.tune observations<Datta/Xiangyu>' · 26 Feb

“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…”

Ben · Teams channel post · 9 Mar

“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]”

Pragya · Teams chat · 9 Mar

“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!”

Pushkaraj · Teams chat · 10 Mar

“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!”

Caroline · Teams chat · 11 Mar

“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…”

Santosh · Teams chat after a call · 8 Apr Define

“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…”

Simao · Teams chat · 1 Jun Hire

“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”

Gernot; · Teams meeting chat · 17 Jun

“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]”

Simao · Teams chat · 24 Jun

“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.”

Simao · Teams chat · 24 Jun

“Hi Datta, Thanks for managing the candidate really well Regds, Gopi”

Gopikrishnan · Email · 30 Aug Hire

“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…”

Mariélle · Teams chat 'Reverse mentoring Dattatreya Vellal' · 2 Sept MentorReport

“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”

Mariélle · Teams chat 'Reverse mentoring Dattatreya Vellal' · 2 Sept Mentor

“[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…”

Sundaresan · Teams chat · 13 Sept AlignAuthorize

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 exports
606h in meetings

795 meetings, 2.3 h per weekday across 261 weekdays Recorded

38%set up by us
Set up by me or the team 231 hOthers invited me 375 h
43days of 4 h or more

12 days had 6 h or more; hours are summed, overlaps are not removed

443h dot-connects

163 h are other meetings listed in the same exports

Meeting time by leadership action

each meeting counted once, under its strongest action

Hours by action

From the meeting title and kind; 173 h in 262 meetings carry no action Estimate

● Oversee128 h● Align62 h● Define59 h● Assess45 h● Mentor40 h● Hire30 h● Authorize26 h● Report22 h● Evangelize12 h● Delegate10 h

Month by month

Meeting hours per month, by action

JanFebMarAprMayJunJulAugSepOctNovDec
DefineAssessAlignDelegateOverseeAuthorizeMentorHireReportEvangelize

Every weekday

hours of meetings per day
MonWedFriJanFebMarAprMayJunJulAugSepOctNovDec
No meetingsup to 2 h2 to 44 to 6over 6 hHoliday or leave

By kind of meeting

Hours by kind, grouped by words in the title Estimate

Other meetings170 hDevOps, pipelines and GitHub120 hCode quality and technical debt75 hTeam and 1:1 syncs63 hBusiness progress dialogues45 hWorkshops and knowledge sharing43 hHiring and bar raisers32 hCoding practice, mentoring and pairing23 hAssessments and evidence17 hTech connectedness and communities11 h.connect sessions6 h

Month by month

Meeting hours per month, by kind

27Jan67Feb50Mar22Apr48May64Jun51Jul69Aug55Sep59Oct66Nov28Dec
Other meetingsDevOps, pipelines and GitHubCode quality and technical debtTeam and 1:1 syncsBusiness progress dialoguesWorkshops and knowledge sharingHiring and bar raisersCoding practice, mentoring and pairingAssessments and evidenceTech connectedness and communities.connect sessions

By weekday

Hours of meetings, Monday to Friday

115Mon137Tue154Wed111Thu87Fri

Largest recurring meetings

Meetings that came back three or more times; individual and small-group meetings are not listed

12 rows
MeetingTimesHours
Software Excellence Program- Cont Value Delivery (DevOps Pilots)…2524.8
Docker Desktop usage in Philips109.2
Preventive monitoring and alerting Pilot weekly call129.0
GitHub SaaS Global Stakeholder Meeting118.0
SW CoE - OHC Business Progress Dialog115.5
Technical Connectedness - Weekly check-in75.2
SW CoE - a business unit - Business Progress Dialog105.0
SW CoE - a business unit - Business Progress Dialog (Monthly)55.0
a business unit Synergy DevOps Sync up85.0
Philips DevOps CoP : Weekly sync up meeting83.8
Bi weekly- Devops Archi pipeline alignment53.8
SW CoE - HSDP - Business Progress Dialog (Monthly)43.5

How this was counted

meetings with colleagues, not the whole calendar

Source: 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 projects
JanFebMarAprMayJunJulAugSepOctNovDecEnd-to-End DevOps whitepaper, Philips… Software Competency Lead role for USA and… .connect visualisation dataset of 2020… .grow Software Capability Building pitch… dotTune observations, Software Engineering… Interviewing tips, Bar Raisers onboarding… 2021 recognition: CTO annual address award… Shift-left talk (Brazil conference),… Bangalore ICTO organisation chart, 2022… DevOps (CI/CD) assessments for ISAI and… Observability for Customer Delight… Templatized Black Duck source scan jobs in…
Bar = earliest to latest dated file in the folders.

Each project

Project pages

choose a project to open its page

Templatized Black Duck source scan jobs in the AICloud Azure DevOps pipelines (pull request, August 2021)

Aug 2021

A 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.

AuthorizeEvangelize

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

19 versionsBlack Duck versions listed for the AICloud project Recorded
2 repo scansdotnet and node repository scans enabled as examples Recorded

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.”

Bhargava, Reviewer on the pull request