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 2020: 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, Oversee, 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. 350 of 457 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 | 11 | of the 11 sessions Recorded |
| Messages and emails from colleagues | 6 | that describe this action |
| Anytime Feedback reviews | 1 | of 65 written reviews |
| Projects | 2 | · |
| Meeting hours | 122 | 87 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 2020: 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 2020 I led 11 sessions, and the work shows in what others say: 156 people answered the session feedback forms, 65 colleagues gave Anytime Feedback and 38 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
• Preparation prior to the interview is paramount (review of the resume, Job Description, past round feedback, red flags) • Evaluation needs to be structured and fact-based coupled with instincts • Rapport building is key. As…
This feedback is not on today's session but for the sessions I attended from the start till last month. Unfortunately because of meeting clashes, I lagged behind considerably post mid Aug. I wanted to provide my view on the…
• Ability to switch between different contexts wrt organizational talent needs across different organizations/ businesses in a seamless manner (switch between needs for Product Owner/Program Manager/Functional manager etc) •…
Projects
Where the year's project work went
Colleagues' recognition
Appreciation emails and messages
In their words
“Eager to improve and inspire: during the training it was hard not to be engaged due to Datta's ability to show and vocalize value. Team up to win: the partnership between TA and SW CoE is refreshing and has shown what can be done if we take cross functional partnership seriously. The result is impressive and between the two groups it allowed a strong delivery of what improvement can and will look like for finding…”
“I have worked with Datta on programs/workshops/sessions for Interview Skills training for R&D managers within Philips to better understand behaviour interviewing. Datta contributes as a competency specialist, Software Center of Excellence and his engagement with different teams globally is phenomenal. His sessions are super interactive, he really gets everyone involved and even creates an open forum where everyone…”
“Brijesh: Vellal, Dattatreya for influencing with out authority. Rani: Datta: Driving Innovation: Building teh confidence on hsi idea, pilot it, influence, inspire and does not give up. Anuradha: Vellal, Dattatreya Very transparent and honest in his approach. Aravind: Vellal, Dattatreya the man who can pull people a crowd puller in our team [emoji] an inspirational speaker , probably I have to learn to…”
“Pankaj 10:43 AM: dropping out - thanks all for the participation - it made the sessions and learning exciting. Meeting ended 46m 8s 10:45 AM. Rahul 10:46 AM: Thanks Datta, Kiran and SCOE team. Kiran 10:50 AM: Again, I thank all participants for their enthusiastic participation. This "I will code" session has been marked by the interest of its participants [emoji]! [Praise card] Kiran sent praise to…”
Learning & Enablement Delivery
Summary
Every training session the folders show Datta delivering in 2020, 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 |
|---|---|---|---|
| SWCoE consultation | 1 | 30 Jan | 30 Jan |
| Coding practice (30 sessions, January to October 2020) | 1 | 31 Jan | 31 Jan |
| Craftsmanship assessment readouts | 1 | 21 Apr | 21 Apr |
| Philips Virtual Learning Summit | 1 | 13 May | 13 May |
| SW CoE discussion sessions | 1 | 2 Jul | 2 Jul |
| Coding practice bootcamp | 1 | 17 Aug | 17 Aug |
| Bar Raiser programme | 1 | 25 Aug | 25 Aug |
| Interviewing and Bar Raisers | 1 | 9 Sept | 9 Sept |
| .waste / .tune | 1 | 16 Sept | 16 Sept |
| .share / .tune | 1 | 22 Oct | 22 Oct |
| Business engagement talks | 1 | 16 Dec | 16 Dec |
How participants scored the sessions
156 responses to "how likely are you to recommend this session", 0 to 10
Every session
11 sessions, with the folder each comes from| Date | Session | Channel | People | Responses | Average | NPS |
|---|---|---|---|---|---|---|
| 30 Jan 2020 | SWCoE consultation sessions on code-quality tooling (Jan to Apr 2020) | Unknown | 14 | 8.93 | 64 | |
| 31 Jan 2020 | Coding practice 2020: weekly Java programming sessions | Online and in-person team sessions for the SWCoE BEQR community | 25 | 85 | 9.4 | 93 |
| 21 Apr 2020 | IT Delivery - EMS Mobile Platform Business engagement: SWCoE report-out | Unknown | ||||
| 13 May 2020 | Quality at Desk and Review of Reviews (Philips Virtual Learning Summit) | Philips Virtual Learning Summit (online) | 270 | |||
| 2 Jul 2020 | Microservices - Reliability and design thinking | Microsoft Teams meeting | ||||
| 17 Aug 2020 | Coding practice bootcamp, afternoon session | Online (Teams chat copied into feedback file) | ||||
| 25 Aug 2020 | Alignment conversation for bar-raisers | Online session with Menti polling | ||||
| 9 Sept 2020 | Interview skilling for the Blumenau team | Remote session (tool not stated; Mentimeter used) | 4 | |||
| 16 Sept 2020 | .waste programme observation pattern samples | Internal SW CoE session (tool not stated) | ||||
| 22 Oct 2020 | .tune (waste removal) programme sharing, Oct 2020 | .share session (tool not stated) | ||||
| 16 Dec 2020 | Transformation Journey for IGT | Not stated |
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 record1,772 people engaged; the list gives the month only Recorded
734 people engaged Recorded
453 h of meetings with colleagues, 2,528 colleague-meetings; 47 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 | 90 |
| .connect - .craft parameters | 19 |
| .connect - Quality @ desk | 17 |
| .connect - Mutation Testing | 9 |
| .connect - jscpd | 4 |
| .connect - Workshop | 4 |
| .connect - Bar raisers | 2 |
| .connect - Automation | 1 |
| .connect - Similarity Check | 1 |
| .waste pilot sessions | 1 |
| .connect - STO | 1 |
| DevOps pilot sessions | 1 |
By business unit, led by me
| Business unit | Sessions |
|---|---|
| PS-I2M | 32 |
| a business unit | 21 |
| HSDP-DP | 10 |
| HSDP-CP | 10 |
| Systems | 9 |
| MR | 7 |
| EMR | 6 |
| EIS | 5 |
| PHD-SI | 4 |
| Mobile Surgery | 3 |
By city, led by me
| City | Sessions |
|---|---|
| Bangalore | 139 |
| Best | 4 |
| Eindhoven | 2 |
| Pune | 2 |
| Bothell | 1 |
The 151 .connect sessions led by me, with the team's remarks
| Month | Kind | Business unit | City | Engaged | Remarks |
|---|---|---|---|---|---|
| Apr 2020 | .connect - Quality @ desk | a business unit | Bangalore | 4 | Quality at Desk: C# |
| Apr 2020 | .connect- General | Systems | Best | 9 | Imaging Unit and SW CoE |
| Apr 2020 | .connect- General | a business unit | Bangalore | 3 | Guardrails and Software CoE in CT |
| Mar 2020 | .connect - Quality @ desk | HSDP-DP | Bangalore | 2 | Quality @ desk - C#,Python:[category:Exploratory][type:business-request]Quality @ [language:Java,C#,Python][subject:Functional test… |
| Apr 2020 | .connect - Quality @ desk | Bangalore | 14 | Quality @ desk - C#,Python: Setting up Configuration of POM to gate for CQ at build | |
| Feb 2020 | .connect- General | Eindhoven | 2 | Datta show facade | |
| Feb 2020 | .connect- General | HSDP-CP | Bangalore | 15 | Pair programming - introduction |
| Feb 2020 | .connect - Mutation Testing | ICAP_SA | 2 | Discussions on C# mutation testing | |
| Feb 2020 | .connect- General | PS-I2M | Bangalore | 2 | PSI2M Software Excellence |
| Feb 2020 | .connect- General | SWCoE | Bangalore | 4 | SW Excellence epic |
| Feb 2020 | .connect- General | PHD-SI | Bangalore | 1 | SIG Technical Validation Session Tuscany iOS for Philips ... |
| Feb 2020 | .connect - Mutation Testing | HSDP-CP | Bangalore | 4 | Mutation Testing Sync |
| Feb 2020 | .connect - .craft parameters | Bangalore | 22 | Training session on Software Craftsmanship assessments - Session # 1 on Basics of Software Engineering | |
| Mar 2020 | .connect - Mutation Testing | a business unit | Bangalore | 6 | CT : Hands on w/s - Mutation Testing |
| Jan 2020 | .connect- General | HSDP-DP | Bangalore | 3 | SWCoE & HSDP CP - catchup, for pair programming exercise Pair Programming with HSDP_CP ,PIC_BLR |
| Jan 2020 | .connect - jscpd | Interoperability Solutions | Bangalore | 2 | Issue with JSCPD |
| Mar 2020 | .connect- General | HSDP-CP | Bangalore | 5 | Unit Testing alignment |
| Feb 2020 | .connect - Workshop | a business unit | Bangalore | 34 | Workshop : CT/AMI Workshop |
| Mar 2020 | .connect - Quality @ desk | HSDP-DP | Bangalore | 8 | Integrating cerberus into PR for java programming metrics |
| Mar 2020 | .connect - jscpd | a business unit | Bangalore | 6 | Running jscpd |
| Feb 2020 | .connect- General | HSDP-CP | Bangalore | 2 | Pair programming slot |
| Feb 2020 | .connect- General | MR | Bangalore | 6 | architectural and software guardrails in MR software |
| Feb 2020 | .connect- General | HSDP-CP | Bangalore | 2 | Pair Programming session with Datta - a colleague/a colleague from Minions team (D&I) |
| Feb 2020 | .connect - Quality @ desk | EMR | Bangalore | 2 | EMR - a healthcare software product : Integrating cerberus into PR for java programming metrics |
| Mar 2020 | .connect - Quality @ desk | PS-I2M | Bangalore | 3 | Explore python guardrails on IDM's codebase. |
| Mar 2020 | .connect - Mutation Testing | PS-I2M | Bangalore | 3 | Mutation testing exploration on IDM's codebase. |
| Mar 2020 | .connect- General | a business unit | Bangalore | 3 | CT : Improvement Hands-on mtg |
| Feb 2020 | .connect- General | HSDP-CP | Bangalore | 5 | Pair Programming with HSDP_CP ,PIC_BLR |
| Feb 2020 | .connect- General | HSDP-CP | Bangalore | 4 | Catch-up: Ideating on how to fast-track managers to techno-managers |
| Feb 2020 | .connect- General | HSDP-CP | Bangalore | 4 | Pair Programming with HSDP_CP ,PIC_BLR |
| Feb 2020 | .connect- General | US | Bangalore | 4 | Architecture and software guardrails |
| Feb 2020 | .connect- General | a business unit | Bangalore | 7 | Architecture and software guardrails |
| Mar 2020 | .connect- General | MDF | Bangalore | 5 | C++ static code analysis on IDE |
| Mar 2020 | .connect - Mutation Testing | PS-I2M | Bangalore | 3 | IoT Cloud RSM - Mutation Testing Tools |
| Feb 2020 | .connect - Quality @ desk | EMR | Bangalore | 2 | Quality @ desk -Code quality as a service |
| Mar 2020 | .connect - Mutation Testing | EMR | Bangalore | 6 | Mutation testing for EMR |
| Mar 2020 | .connect- General | HSDP-DP | Bangalore | 4 | Setting up Cerberus (Program Metrics & Suppress Warning Detector & Trending) tool |
| Apr 2020 | .connect - Mutation Testing | PS-I2M | Bangalore | 9 | PS-I2M : [ASP Team ] : Hands-on session : Code Coverage & Mutation Testing |
| May 2020 | .connect - Mutation Testing | HSDP-DP | Bangalore | 4 | HSDP-DP : Hands-on w/s on Mutation Testing |
| Apr 2020 | .connect- General | PS-I2M | Bangalore | 12 | Code review report tool |
| Apr 2020 | .connect- General | EMR | Bangalore | 4 | [Req Info] Understanding the verification & validation process of EMR |
| Apr 2020 | .connect- General | EMR | Bangalore | 3 | Tools used for V&V cycles of EMR-a healthcare software product |
| May 2020 | .connect - Workshop | HSoP | Bangalore | 3 | Tech Training - Constructive Programming - API testing & coverage - Java |
| May 2020 | .connect - Automation | PS-I2M | Bangalore | 3 | Automation Framework for AngularJS applications |
| May 2020 | .connect - Quality @ desk | a business unit | Bangalore | 10 | Quality @ desk - Working session to detail out the Quality@desk plan |
| May 2020 | .connect- General | PS-I2M | Bangalore | 3 | Nuget package for identifying duplicate code in .NET projects . |
| May 2020 | .connect- General | PS-I2M | Bangalore | 4 | PSC Team: Demo on Cyclomatic Complexity |
| May 2020 | .connect - Quality @ desk | a business unit | Bangalore | 7 | Quality @ desk - Quality@Desk for a business unit |
| May 2020 | .connect - Quality @ desk | a business unit | Bangalore | 2 | Quality @ desk - CT: Code Quality Hygiene : Q@D Gating: Dead Code |
| May 2020 | .connect - .craft parameters | PS-I2M | Bangalore | 4 | PS-I2M: IoT : Support for .craft actions |
| May 2020 | .connect- General | a business unit | Bangalore | 1 | Guardrails demo for Eleva code |
| May 2020 | .connect- General | Bangalore | 3 | Architecture and Software Practice @ PIC with a colleague & a colleague | |
| Apr 2020 | .connect - .craft parameters | Bangalore | 21 | Training session on Software Craftsmanship assessments - Session # 1 on Basics of Software Engineering | |
| Apr 2020 | .connect - Similarity Check | MR | Bangalore | 4 | S101 - Intro and demo |
| Apr 2020 | .connect - Workshop | a business unit | Bangalore | 17 | Workshop : To detail out the SW Improvement Plan |
| Apr 2020 | .connect - Workshop | CLC | Bangalore | 2 | Workshop : Hands-On w/s :Setting up Quality @ Desk parameters for MOM project |
| Apr 2020 | .connect- General | HSDP-CP | Bangalore | 3 | Session/Discussion Reliability |
| Apr 2020 | .connect- General | PS-I2M | Bangalore | 3 | PS-I2M : [PSC Team] : Exploratory call |
| Apr 2020 | .connect - Quality @ desk | Bangalore | 6 | Quality @ desk - Introduction to Quality at desk initiative | |
| Apr 2020 | .connect - Mutation Testing | PS-I2M | Bangalore | 9 | PS-I2M : [ASP Team ] : Hands-on session : Code Coverage & Mutation Testing |
| Mar 2020 | .connect- General | a business unit | Bangalore | 4 | CT/AMI SW improvements |
| Mar 2020 | .connect- General | PS-I2M | Bangalore | 3 | IDM - SWCoE Alignment & Plan for 2020 |
| Mar 2020 | .connect- General | Bangalore | 4 | EMS-Mobile Platform - .craft SW baseline assessment | |
| Apr 2020 | .connect- General | Bangalore | 5 | Unit Testing alignment | |
| May 2020 | .connect- General | a business unit | Bangalore | 12 | SW Quality Improvement Progress Review |
| May 2020 | .connect- General | Bangalore | 5 | Software Excellence - Architecture / Design Modularity measure | |
| May 2020 | .connect- General | PS-I2M | Bangalore | 5 | Automation Framework for AngularJS applications |
| May 2020 | .connect- General | RadOnc | Bangalore | 10 | RADOnc : Discussion on different initiatives taken by SWCoE to support BiU's in continuous improvement |
| May 2020 | .connect- General | PS-I2M | Bangalore | 3 | Guardrails update |
| May 2020 | .connect- General | Bangalore | 9 | Devops assessment schedule | |
| May 2020 | .connect- General | PS-I2M | Bangalore | 2 | Cycle Time Reduction for a product release |
| May 2020 | .connect- General | a business unit | Bangalore | 1 | Session to discuss a resharper and fortify issue on multiple projects |
| May 2020 | .connect- General | Bangalore | 2 | CIP - Meeting | |
| May 2020 | .connect- General | 15 | PIC Strategy: Intake great talent | ||
| May 2020 | .connect- General | Bangalore | 7 | Org Capabilities - Intake Great talent | |
| May 2020 | .connect - Quality @ desk | Systems | Bangalore | 2 | Quality @ desk - Philips Software Center of Excellence - Quality at Desk - a business unit |
| May 2020 | .connect- General | a business unit | Bangalore | 3 | single script to run multiple tools |
| May 2020 | .connect- General | Bangalore | 1 | CodeScene status at Philips and options for .debt | |
| Jun 2020 | .connect - Quality @ desk | a business unit | Bangalore | 3 | Quality @ desk - CT: Code Quality Hygiene : Q@D Gating: Dynamic Analysis |
| Jun 2020 | .connect - .craft parameters | PS-I2M | Bangalore | 6 | Readiness check for 3/11 Q2 Assessment |
| Jun 2020 | .connect- General | a business unit | Bangalore | 1 | CT locallization |
| Jun 2020 | .connect - jscpd | US | Bothell | 2 | U/S: Demo on JSCPD tool - to measure duplication |
| Jun 2020 | .connect- General | SRC-Mobility | Bangalore | 1 | SRC : RCA on defects. |
| Jun 2020 | .connect- General | PHD-SI | Bangalore | 2 | Support needed for reviewing the code scene dashboard for OHC |
| Jun 2020 | .connect - Quality @ desk | SRC-Embedded | Bangalore | 2 | Quality @ desk - SRC : Hands-on session on Q@D |
| Jun 2020 | .connect- General | IAP | Bangalore | 2 | Waste Removal observation session \xe2\x80\x93 CT Business \xe2\x80\x93PICB |
| Jun 2020 | .connect- General | Mobile Surgery | Pune | 1 | a business unit: Understand the structure & challenges of the Embedded team |
| Jun 2020 | .connect- General | PS-I2M | Bangalore | 1 | Maxfailure option for Asp Gating solution |
| Jun 2020 | .connect - .craft parameters | Bangalore | 2 | Discuss .craft aspects for PInS Gateway project | |
| Jun 2020 | .connect - .craft parameters | PS-I2M | Bangalore | 13 | Pre-Assessment for .craft Q2 - ASP & a product |
| Jun 2020 | .connect - .craft parameters | PS-I2M | Bangalore | 3 | |
| Jun 2020 | .connect- General | PS-I2M | Bangalore | 3 | Maven /GradleGating |
| Jun 2020 | .connect- General | CI | Eindhoven | 1 | Cerberus vs TICS |
| Jun 2020 | .connect- General | Bangalore | 7 | Software excellence - review guardrails | |
| Jun 2020 | .connect - .craft parameters | Mobile Surgery | Pune | 6 | .craft Q2'20 - Support on form submission |
| Jun 2020 | .connect- General | PS-I2M | Bangalore | 5 | Hands-on session : Incorporate PMD violations, SuppressedWarnings violations checks via Cerberus |
| Jun 2020 | .connect- General | PS-I2M | Bangalore | 5 | PS-I2M : PSC Team : Review of common components |
| Jun 2020 | .connect- General | Bangalore | 6 | Research & PS I2M R&D Code Merge challenges | |
| Jun 2020 | .connect - Quality @ desk | a business unit | Bangalore | 9 | Quality @ desk - a business unit- Q@D :Hands-on session : Angular |
| Jun 2020 | .connect- General | PS-I2M | Bangalore | 1 | Java Interpretation |
| Jun 2020 | .connect- General | HSDP-CP | Bangalore | 1 | Align on Microservices session |
| Jul 2020 | .connect- General | Systems | Best | 1 | Understanding the SpecFlow cases |
| Jul 2020 | .connect- General | PS-I2M | Bangalore | 6 | PS-I2M :ASP: Discussion on understanding the needed request |
| Jul 2020 | .connect- General | EIS | Bangalore | 6 | EIS: Discussion on a code-quality service & CICD branching strategy |
| Jul 2020 | .waste pilot sessions | PCA | Bangalore | 2 | .waste removal observations<Datta/a colleague> |
| Jul 2020 | .connect- General | MR | Bangalore | 3 | Demo of Cyclomatic Complexity tool |
| Jul 2020 | .connect - jscpd | PHD-SI | Bangalore | 7 | Code Duplication : Token Size |
| Jul 2020 | .connect- General | a business unit | Bangalore | 1 | CT branching + case study - knowledge sharing |
| Jul 2020 | .connect - .craft parameters | EIS | Bangalore | 4 | EIS : Discussion on support needed on : Code Duplication & Code Review |
| Jul 2020 | .connect - Quality @ desk | MR | Bangalore | 2 | Quality @ Desk initiative & making continuous improvement |
| Jul 2020 | .connect - .craft parameters | Systems | Best | 2 | Elaborate on CI/CD improvement for Positioning Department |
| Jul 2020 | .connect- General | Systems | Bangalore | 1 | Conversation about build segregation |
| Jul 2020 | .connect- General | PHD-SI | Bangalore | 1 | How to improve the code scene Scores |
| Jul 2020 | .connect - Bar raisers | Bangalore | 2 | Bar Raisers : Rolling out bar-raisers to the global audience - plan | |
| Aug 2020 | .connect - Bar raisers | TA | Bangalore | 7 | Bar Raisers : Preparing for Bar-raiser trainings |
| Aug 2020 | .connect - .craft parameters | PS-I2M | Bangalore | 2 | .craft Q2'20 results discussion |
| Aug 2020 | .connect- General | EIS | Bangalore | 2 | Dynamic analysis for IBE server prediction |
| Aug 2020 | EMR | Bangalore | 4 | EMR Build Gating Analytics tool | |
| Aug 2020 | .connect- General | HSDP-DP | Bangalore | 7 | Cerberus' JCMD |
| Aug 2020 | .connect - .craft parameters | Systems | Best | 2 | Elaborate on CI/CD improvement for Positioning Department |
| Aug 2020 | .connect- General | HSDP-DP | Bangalore | 2 | Mentoring Engagement Kick-off |
| Jan 2020 | .connect- General | Bangalore | 17 | SWCoE - I will code initiative | |
| Sep 2020 | .connect- General | Systems | Bangalore | 3 | Support for Automatic Intermittent Detector |
| Sep 2020 | .connect- General | HSDP-DP | Bangalore | 1 | Mentoring Program |
| Sep 2020 | .connect- General | PS-I2M | Bangalore | 2 | Updates on TICS upgrade impacts |
| Sep 2020 | .connect - .craft parameters | Bangalore | 4 | Q2'20 .craft review discussions | |
| Sep 2020 | .connect- General | HSDP-DP | Bangalore | 7 | Discussion on CodeScene Deployment in HSDP |
| Sep 2020 | .connect- General | EIS | Bangalore | 1 | Improving technical interviewing skills. |
| Sep 2020 | .connect- General | EIS | Bangalore | 5 | Debrief Meeting - a colleague |
| Sep 2020 | .connect- General | PS-I2M | Bangalore | 5 | PS-I2M :ASP: Discussion on understanding the needed request |
| Sep 2020 | .connect- General | MR | Bangalore | 9 | SW CoE MR DevOps Assessment |
| Sep 2020 | .connect- General | HSDP-DP | Bangalore | 3 | SW CoE HSDP_DP DevOps Assessment |
| Oct 2020 | .connect- General | Bangalore | 15 | Quick catch-up - Bar Raiser program | |
| Oct 2020 | .connect- General | Bangalore | 1 | Understanding Q&R compliance policies | |
| Oct 2020 | .connect - Quality @ desk | a business unit | Bangalore | 3 | Demo on Quality At Desk tool for feedback. |
| Oct 2020 | .connect - .craft parameters | a business unit | Bangalore | 3 | CT - Dynamic Analysis - Dry run for demo |
| Oct 2020 | .connect - STO | a business unit | Bangalore | 3 | STO for CT Demo - practice session |
| Oct 2020 | .connect- General | Bangalore | 5 | Live dashboard feasibility | |
| Oct 2020 | .connect- General | Bangalore | 5 | SW CoE Curriculum | |
| Oct 2020 | .connect- General | Systems | Bangalore | 2 | Software Improvement Proposals-a business unit |
| Oct 2020 | .connect- General | CAO | Bangalore | 2 | Discussion about CAO EPIC Define Common CI-CD pipeline for Harmonized Operations |
| Nov 2020 | .connect- General | MR | Bangalore | 7 | MR SWCoE Readiness review |
| Nov 2020 | .connect - .craft parameters | EOI | Bangalore | 8 | EOI - Code Craftsmanship 2020 Impacts |
| Nov 2020 | .connect - .craft parameters | MR | Bangalore | 2 | Discuss MR SW COE updates |
| Nov 2020 | .connect - .craft parameters | PS-I2M | Bangalore | 3 | Align on the parameters to be rated |
| Nov 2020 | .connect - .craft parameters | PS-I2M | Bangalore | 5 | ASP - CI/CD Discussion |
| Nov 2020 | .connect- General | PS-I2M | Bangalore | 2 | Cerberus exclusion - next steps post demo |
| Dec 2020 | .connect- General | Systems | Bangalore | 2 | Gamifying code-scene: Demo by a colleague, brainstorming on possible expansions |
| Dec 2020 | DevOps pilot sessions | 5 | Philips DevOps: pipeline model - a discussion | ||
| Dec 2020 | .connect - .craft parameters | PS-I2M | Bangalore | 4 | IoT Q2 Assessment Feedback : Compiler Warning |
| Dec 2020 | .connect- General | Mobile Surgery | Bangalore | 10 | IoT Q2 Assessment Feedback : Compiler Warning |
Month-by-month figures
| Month | Dot-connects | Set up by me | Hours | Colleague-meetings | Different colleagues | Cities | Most frequent cities |
|---|---|---|---|---|---|---|---|
| 2020-01 | 8 | 2 | 13.5 | 94 | 87 | 4 | Eindhoven, Pune, Amsterdam |
| 2020-02 | 45 | 4 | 51.3 | 259 | 134 | 9 | Eindhoven, Highland Heights, Shenyang, Murrysville, Pune |
| 2020-03 | 59 | 7 | 68.0 | 254 | 153 | 10 | Blumenau, Pune, Eindhoven, Amsterdam, Shanghai |
| 2020-04 | 68 | 8 | 62.3 | 323 | 173 | 11 | Eindhoven, Blumenau, Best, Amsterdam, Andover |
| 2020-05 | 66 | 2 | 50.6 | 298 | 155 | 4 | Best, Eindhoven, Amsterdam |
| 2020-06 | 65 | 6 | 54.3 | 348 | 168 | 7 | Pune, Eindhoven, Bothell, London, Amsterdam |
| 2020-07 | 46 | 4 | 44.1 | 275 | 147 | 7 | Best, Amsterdam, Pune, Blumenau, London |
| 2020-08 | 25 | 2 | 31.0 | 213 | 122 | 11 | Eindhoven, Blumenau, Amsterdam, Murrysville, Best |
| 2020-09 | 30 | 1 | 29.5 | 156 | 104 | 10 | Blumenau, Best, Amsterdam, Eindhoven, Haifa |
| 2020-10 | 21 | 5 | 15.3 | 60 | 45 | 6 | Amsterdam, Eindhoven, Pune, Andover, none |
| 2020-11 | 24 | 20.0 | 171 | 157 | 10 | Eindhoven, Haifa, Amsterdam, Cambridge, Best | |
| 2020-12 | 14 | 6 | 13.5 | 77 | 72 | 6 | Pune, Eindhoven, Amsterdam, Belfast, Shanghai |
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
348 comments, word for wordUnderstand the integration of Sonar and CPD tools
tool to use to find code duplication locally
IDE setup for Static code Analysis and Code duplication tool.
code improvements as well as some tools
workshop for tools in IDE like eclipse to improve the code quality
Setting up dev environment/Eclipse with code quality tools/plugins
context was to setup development environment with tools so that our code smells good and productive with the minimum effort.
Workshop to setup development environment with tools in Java(Eclipse)
Codecoverage LOC & BRANCH gated- DONE & INTEGRATED- MAVEN BUILD Methold Level Cyclomatic Complexity - DONE & INTEGRATED-MAVEN BUILD DEPENDENCY ANALYSIS CHECK - DONE & INTEGRATED -MAVEN BUILD Duplication gated - DONE & INTEGRATED - MAVEN BUILD PMD Checks- DONE & INTEGRATED - MAVEN BUILD Mutation Testing - DONE & INTEGRATED -MAVEN BUILD Compiler warning gated - DONE & NOT INTEGRATED - MAVEN BUILD
CQ BUILD INTEGRATION OF BELOW THINGS AS PART OF CODE QUALITY Codecoverage LOC & BRANCH gated- DONE & INTEGRATED- MAVEN BUILD Methold Level Cyclomatic Complexity - DONE & INTEGRATED-MAVEN BUILD DEPENDENCY ANALYSIS CHECK - DONE & INTEGRATED -MAVEN BUILD Duplication gated - DONE & INTEGRATED - MAVEN BUILD PMD Checks- DONE & INTEGRATED - MAVEN BUILD Mutation Testing - DONE & INTEGRATED -MAVEN BUILD Compiler warning gated - DONE & NOT INTEGRATED - MAVEN BUILD
Gated solutions for Develops local build using jacoco maven plugings. Gated Build with POM Codecoverage LOC & BRANCH gated Methold Level Cyclomatic Complexity DEPENDENCY ANALYSIS CHECK Duplication gated PMD Checks- Mutation Testing Compiler warning gated -
Static code analysis on IDE
Enabling early detection and fail the build if any of the following are violated a) Check line-coverage on unit-test per class (100%) b) Check branch-coverage on unit-test per class (100%) c) Cyclomatic complexity per method ( < = 3) d) Compiler warnings e) Dependency analysis on defined dependencies (for cyclic/implicit/un-used dependencies) f) Duplication detection with token count of 20 g) PMD checks h) Spotbug checks i) Mutation testing checks j) Google check-style
Got help with integration onto our project
introduced new tool jscpd
Code Duplication tool setup helped team to find duplicates which was minimal to 2 lines.
its good some tools we don't know. it helpful for scale code and some tricks we don't know.
The discussion was informative. The various topics covered on formatting , auto save will be definitely useful to improve developers efficiency. We can have some more discussions on sonarLint and discuss some more rules that can be handy while development.
Learnt about all different code quality plugins available in Eclipse which can be used to integrate and use
i was able to learn about many tools and many tricks so that i can save my time and improve the code quality.
The impact is to make us super faster when we are coding and debugging.
This is a great session to overcome current development code quality issues in local machine instead of depend on CI/CD pipeline. It;s practical session, we have covered all plugin-in implementations which are required for any Java projects.
The impact of the discussion is very high in the business with the help of mutation testing and writing best code and identifying the deepest and shallow test cases. Code quality gated at various parameters and build level which saves time in identifying the issues metrices in code at developer machine. The session was very really helpful and we have integrated with our live code base and we see it as very high value . Code review with these checks will fasten and strengthen the process .
The discussion concludes new learning aspects and New was of implementation of gated solution for the builds.
Training on usage of 'CPPCheck' tool on Eclipse which gives real time analysis of cpp code
It was a great session, learned about lot of plugins which help in writing quality code and detecting the violations early in the development.
The conversation was good. So I don't feel any improvement currently.
we can have a little bit more lengthy session and implement those tools and extensions more.
It was very clear and understandable.
Behavior Vs Feature, Scenarios of addition in a calculator, Trade offs
1.) Imitation is the best form of flattery, but it does not always work ! 2.) Behaviours enable development of scenarios. 3.) Requirements can result in constraints and assumptions.
How to identify behaviors, What is difference between features and behaviors
Interns of a Calculator Behaviour (Additions) Difference between behaviour and a feature Defining behaviours
1.) Behaviours for writing a code 2.)
Mainly on the behavior parts ,what should we think before to start anything on development perspective..
1. Difference between defining the behavior and feature for any product. 2. Dimensions of product design requirement .
Pre-requisites - start writing a code. understanding of intended use of our product.
For calculator what will be the behaviors for addition before writing a test cases.
Defining Behaviors Behaviors are easy to understand
writing specs.
- 2 levels of working of Java (at byte level & then at machine language level) - Installing JDKs & eclipse
1.) Java Runtime Environment 2.) Practical issues in JRE installation 3.) The analogy of Java being like a manually steered car.
We learn the challenges we can get while installing the environment. It is important for us to know it before before starting the coding. This learning will help to pass his to other new members who want join the session later
1.java runtime environment 2.ecllipse installation
What is JDK and JRE
Oops concept Oops concept with regard to human body "is a ..." & "has a..."
topic was "object oriented program" In that we has taken an example as human body. And relating object oriented program features Inheritance, Polymorphism, Abstraction, Encapsulation
"is a" and "has a" - Object Inheritance encapsulation
Basics of OOP To be precise , the 3 pillars ( Inheritance, encapsulation and polymorphism were covered beautifully taking a very basic example . Though Polymorphism word was not used much :-)) Concept was explained very well
Encapsulation, Inheritance and the understandings of " Is a" and "Has a" Creating Digits and grouping / listing
Today learn about basic concepts of Class, encapsulation, inheritance and few other things in the Object Oriented programming. Also learned on to very basic terms or questions we need check while working on class, object etc. "Has a" & "Is a"
Inheritance Encapsulation grouping data
Inheritance, Polymorphism, Encapsulation & Extension
We learnt about polymorphism, extension and differences between them.
Inheritance, Encapsulation, Polymorphism & Extension
Concepts of Encapsulation, inheritance, polymorphism and extension with the very well examples.
Learnt more about Polymorphism, Inheritance, encapsulations and unique properties with examples..
Inheritance, Polymorphism, encapsulation, Public and Private properties of a Class
- Access Modifier (Public and Private) - Structure
Access identifiers(Public,Protected,Private)
Discussed about examples about Polymorphism , Inheritance, Encapsulation, and extension by each one of us.
Examples for Inheritance, Polymorphism, encapsulation and extension. Access Modifier - Public, Protected and Private Program structure
Various examples of OOPS concepts & access modifiers
1.) Examples for polymorphism, inheritance, encapsulation and extension. 2.) Difference between polymorphism and inheritance 3.) Access modifiers
Instantiation, Code structure
Child - parent class, package structures, Coding logic
-What is child and non child class? -Access modifiers and how they could be access
How to write code How to correct the mistake How to use Class
Did my first program
How to write on my own How to resolve errors We just have to dare to start and there are people to help :-)
Coding basics How to rectify errors Overcome the fear of coding
Three points in Java programming are: 1.) For declaring a method or property, ";" is not required as a line terminator. 2.) Return type is required for method. 3.) For some compilers, main() method may be required.
data - int ( short , long), spring (char, string)
Three things I learnt today are: 1.) Some data types in Java 2.) Declaring variables of different types in Java 3.) Smartness of online Java compilers !
DataType Syntex Creation If Condition
Inspirations to learn new things Curiosity Self confidence
Three learning points are: 1.) float data values need to be suffixed with f. 2.) Meaningful variable names aid in maintainability. 3.) Local variables have to be initialised before usage.
Conditional statements (if, else, else if)
If operations
If Else Chaining If else covering boolean
Conditional statements, using If and Else and fixing few coding errors
Conditional operators, Binary operations and Exiting conditions
If Else condition Nested if Else Operators
Conditional operators, Nested ifs, else & Negation!!
1.) In an if statement, = is still an assignment operator not a condition checker. 2.) Maven preferences can help identify variables which are "final" in the Eclipse IDE. 3.) Understanding nested ifs can be complicated.
Far loop - Initialization, condition for termination and the increment / decrement ,
From [name]: 1.) When using &&, if first condition is false, the Java compiler will not evalue other conditions in the && statement. 2.) Extensibility and/ or scalabality of a program needs to be considered when writing it. 3.) for loops help in executing same action multiple times, typically while processing an array.
While loop. If Else, Use of Conditional operators
Three topics learnt today are: 1.) While statement 2.) Cyclomatic complexity and why high values of the metric are considered complex 3.) For difference of two numbers in an array, check for at least two numbers being present in the array !
while do, patterns using loops, diff between i++ & ++i
While do, do while & differences
while Do-while
1.) In a do-while loop, the body is executed at least once. 2.) Quality@Desk can be introduced to demonstrate better craftsmanship practices. 3.) Online compilers also offer features like Eclipse IDE.
GitHub code repository setting
Github, creating file directly in github & editing
1.) Commit text helps to track changes in files. 2.) Master is the "trunk" or "main" branch. 3.) md: mark down -> It is a way to capture text notes in a formatted manner, recognizable to Github.
Git for windows, push & pull into github & syncing with eclipse
Git setup Committing code to GitHub
1.) Gitbash enables one to integrate git and Eclipse IDE. 2.) Git repository created online can be cloned into local PC. 3.) Git commands like git pull -rebase and git push origin master are important ones.
Three topics learnt today are: 1.) Local repository is a clone of the remote repository. A developer would need to work on the cloned. 2.) All files need to be pulled first into local repository so that changes of others are considered. 3.) Principle applied by git in general is to fix things as quickly as possible. This is demonstrated by the need to pull first, do a merge (if there is a conflict) and then push.
Three things learnt today are: 1.) Git branch -a is used to show the current branches. 2.) The active branch is indicated by "*" and different colour. 3.) Pull request branches need to be deleted after the review is completed.
- Constructor & Methods - Testing using unit test - Debugging
Method & class Calling method in another program
1.) In Java, the keyword "static" is used for the class. It is like a template for all instances of the class. 2.) In a way, the constructor of a class extends the "template" behaviour of a class. It can be used for performing initialisation activities and other operations. 3.) If there is no constructor, the compiler creates an empty constructor.
- using this. for passing value to a method - How do we keep the program modular rather than monolithic - how a simple BankAccount details can mean tonnes of lines of code
- Inter class communication - Intra class communication - debugging method
Writing Class & method Calling the method and debugging the code
Three things learned are: 1.) Data types in the constructor need to be matched with the calling method in the test class. 2.) Any public method can be used for inter-class communication. 3.) Step over and Step into are two modes that are available for debugging.
Three points of learning are: 1.) Code review happens during development itself to some extent, using paired programming. 2.) For optimisation, code needs to be studied to identify areas of micro-duplications and duplications in general. 3.) In paired programming, typically one person will be the leader and the other the follower.
New method creation Duplicate elimination
Three topics of learning today are: 1.) The meaning of code de-duplication and its practical application. 2.) The use of Cerberus CPD option. 3.) The meaning of functional programming via a simple example.
This feedback is not on today's session but for the sessions I attended from the start till last month. Unfortunately because of meeting clashes, I lagged behind considerably post mid Aug. I wanted to provide my view on the sessions that I attended 1) Extremely well structured and paced for new learners started from basics . I learn about coding languages, compilers 2) learnt what program is, structure, If, for, what if loops, count if 3)Had great learning for doing coding and making to compile. had great learning on how to debug the code 4)Dutta's examples on real time situations helped to understand better and apply knowledge 5) with knowledge gain, I am more confident of facing technical teams and make meaningful arguments while reviewing documents from Q&R stand point 6) I learnt basics of CI and GIT and code reviews. This helps immensely in my day today work as I can make informed comments and able to get subject better among larger audience Over all had a great learning experience and improved my understanding of Coding and tools used today. I am very thankful for genuine and sincere effort by Dutta to teach me right from the scratch. I would thank Dutta for his efforts and time with us, really worth a minute for me. I will code is certainly a great initiative and has enhanced my understanding in Coding world …. Thanks a ton to Dutta and his team for making this happen. I also would like to mention my friend [name]'s help to catch up the classes when I was behind the schedule. Thank you [name] !!
Three topics learnt today are : 1.) There are several methods for code deduplication. 2.) A separate class can be used for declaring variables. This is a way to demonstrate encapsulation. 3.) PMD is the Programming Mistake Detector. It shows unused variables, which could lead to dead code.
Cerberus Duplicate Code removal Code Violation using FPM
Better to have a training which can accomodate at least 15 people.
Provide an introduction on what is planned in the session.
Sessions giving good knowledge and flow is good.
Would like to understand the SDLC, to understand the process better.
THis first session was very good. As of now what flow and approach has been explained , i don't see any changes as of now.
As of now ,the session is very good ..May be suggestions will come once we starts coding ..
Sessions as good as it is. :)
Good to be conducted in meeting room so that environment is user-friendly.
no improvement required go the way it is going now
Wiki page which Datta spoke about and & Word of mouth, to break the myth of "I cannot code"
Live practical on the job sessions
Session was useful.
You are going good as of now. No comments at this moment.
going good
Little more info on types of JDK and JRE ( use of different versions 32K and 64k etc and way to select) System environment configuration and its use ( why we have to change some of these parameters)
Human body is too complicated a structure to explain the oops concept.
Going good no improvements needed
this session is good today. It would better if any flow diagram or image is there to understand and link the concept better.
Since this was the first class I attended , i would like to answer this question as the session progresses
This was the 1st session I attended. It was very good. Any chances of improvements, I can mention post the next week session.
As of now you are going in very systematic and methodical way which is good to understand. One suggestion: If you can touch briefly on difference between Object oriented programming and other programming’s, it will help me (us) to understand why object oriented programming languages like Java ,C++ are mostly preferred.
6-Mar-2020 class was way beyond what I expected for first class. Hence no comments.
code snippets - to show the concept - as discussed in the session
For online sessions, sharing screen may help. Brief videos or images to show concepts can also be shown.
I feel the f2f discussion was more engaging with the team, though we don't have that option now. Otherwise its fine.
Maintaining the same engagement, tactics, and mechanism in order to create more interesting learning environment.
We are in a difficult situation. For kind of these sessions, F to F interactions are always good.
Super Datta- continue the great work :-) Very nicely structured and the flow/speed is optimal and great
It is engaged
if we can record this session for future,it will be useful for many as i missed few classes.
keep going as it is now
It may help if the session begins with a request for any open points or clarifications from the previous session.
Suggest if we can start coding for the new concepts while learning rather than just listening. This helps in better assimilation of the concept.
It is awesome
Can we identify as a Quality professional is there anything that we need to pay attention and something to look for.
its going amazing...
Datta, I request you to give one or two sentence info on basic terminologies used in the coding.
There were new concepts and ideas discussed while all assignments were presented, but the time taken for completion was more. To enable completion of topics, discussion on assignment could be restricted to 30 minutes or 45 minutes.
it went well for me
Pausing during online programming could help in understanding problems faced (if any) by participants.
its good
Like the way you explain, how the conditional programming like if is used with simple example.
It is suggested to inform the group of features like "Raise Hand" to clarify doubts and questions.
Going on well . explained well
Its going good. We are allowed to write our own code and debug the errors is really good to learn.
Its going good .
We are working with single files. In a project, there are multiple files. How compliation of multiple java files is done and the problems with dependencies (like libraries and header files) can be demonstrated. Since we are learning if statement now, it would be good if the concept of cyclomatic complexity can be explained in a simple if program.
Going great ..
I suggest that a discussion on metrics used by TICS like compiler warnings and cyclomatic complexity in our code examples can be done. If TICS (or similar tool) can be demonstrated even on simple programs, the meaning of the metrics may be clearer to the audience.
All good
[name]'s comment: It would help if it can be demonstrated how compiler settings can be changed to enable stricter checks on code.
all good
One highlight is the way in which good practices or examples of logic from participants are emphasized. This should continue.
All good
I don't know if it will work but asking a participant to demonstrate may be an idea.
All good
[name]: My thanks and appreciation go for the patience displayed with common mistakes made. Learning has become simpler thanks to the patience.
How static analysis tools can help and interpretation of their results on github repository may be a useful addition.
It would be good if it can be shown how SwCoE initiatives like craftsmanship practices of deduplication of code and/ or Quality@Desk principles can be applied in the github repository.
No Comments
Suggestion (probably for futue batches) is to provide more time to participants to practice methods and constructors using simple examples. 20 minutes can be the time limit for each new concept.
Can we have a real requirement & break it into modules & create 1 modules of choice. The requirement can be as simple as POS in a super market..
All good
More time to practice inter class and intra class communication may be useful.
Duplication of code was demonstrated well using practical examples. Such examples can be continued.
no comments
One suggestion is that the harmful effects of duplicate code (slower performance, perhaps?) can be discussed. Audience may wonder: _Why should I be worried about code duplication?_.
1.It could have been icing on the cake on possible places as Q&R can look for pitfalls within the existing code 2. With the job profile of Q&R it would be highly useful, if there is check list or things to look for in legacy code or new code that would have direct impact on CTQ would also help 3. Would kindly request similar training session on TFS as most of the teams are using and as Q&R its important for us to understand and work on this tool. 4. Similar session on Verification would also benefit to Q&R community a lot
It was good to see how the advantage of encapsulation was explained for entering user input. Such examples would help in the future also.
All good
Key take-away: 1. Writing more readable code 2. Avoiding code duplication and shrinking code base without compromising on the feature. 3. Few tips on performance optimization
Code Optimization, Readability/maintainability
The key take-away would be that we should be looking at possibilities of modularizing code and memory efficiency wherever possible even if it is a test code.
Learnt code optimization by taking out duplicate code into one common method.
How we can generalize the logic to make the code more readable
Code review, we were able to capture few improvement items on existing code.
Review comments and coding standard discussions very very helpful to better the code
The way we look at our code and approach to the problem
We got good quality inputs with pair programming. Having more sessions like this , will help us thinking on better approaches.
By reserving more capacity for such discussions during PI Planning
The way we can improve is to have a better topic to program/discuss. And also duration also can be increased up to 1.5 hours.
its good
Hands-on would be recommended
Nothing as such
participation was very good
Collecting the opinion of different panel member.
The session was engaging and use of the Collabedit tool to capture pictorially was helpful
1 hour for this topic i felt was not sufficient, probably 1 more hour would have helped
Session could have been 20-30 mins longer as it was colloborative.
Nothing in particular. The duration was a little less and we could not understand/complete the topics on time. We probably can have more sessions or longer sessions.
The session flow was good. Given the broad topic, I think it was condensed very well already
Please schedule for a longer time since these kind of topics require brainstorming
Session was good with the way it is.
would have loved if done with concrete use case
Sessoin was good as it was like more interactive
We can plan a series of these sessions as we cannot cover the complete topic in one session. However, the content covered was very informative.
Appreciate the depth of the sessions. Happy that its not just another over-view of MicroServices and instead was a real-time understanding.
Fresh perspective
In-depth explanation
The concepts were explained in a interactive way from the scratch which helped even the juniors to get attention\involvement.
like the overall process of training
Open for discussion
I liked the way the way session was conducted. I was able to learn some of the factors to consider while designing the system I would request you to continue this session further and cover other design aspects as well. Thank you very much Datta.
All in your list :)
Design items
keep the audience engaged and energetic for 4 hours
The interaction with the participants.
Very interactive and lots of discussion
Techniques to improve the process and knowledge shared
Content, structure
Engagement and leaving time for Q&A.
Good explanation of good interviewing practices and how the interview process will include the bar raiser.
Lots of interaction, lots of examples.
Plenty of room for Interactivity, discussions Good combination of different (related) topics and viewpoints in the sessions
Finished on time. Breaks (even though one was later). Many people with camera on. Asking for input, interactive session. Good participation by everyone.
Stimulated good conversation and sharing.
It was nice that the session was interactive. The discussion on the order of 5 factors(competence, confidence,etc.) of evaluation was enlightening.
The session was very interactive and it was conducted very effectively.
Interactive
- Asking the right set of questions and taking the discussion through the very important topics - Keeping it very open, without having too many PPT slides, which would have made it boring
STAR concept
A good overview of the topics. STARR and biases discussion was most useful in providing guidance and insights.
Interactive and ensuring engagement from everyone
Lots of great content here for sure...I learned a lot. I like how we tried to get the crowd involved as much as possible...not always easy on a Monday morning though...good attempts by the presenters
more interaction at some points
It was confused about the agenda of the meeting, And I lost some minutes of the second half. So I think would be good if at the beginning present the agenda with all the breaks.
I didn't know much about this program before attending today's session -- I would have liked to have been introduced to it before today.
Been together, more session, more brainstorm, lessons learned
short timeframes for the overall session (2 hrs)
N/A. I thought the 4 hours was short enough to keep us engaged without feeling like it dragged on.
Very long session (4 hours). Might have been better to break this up into smaller sessions across multiple days. Just as a general thought, it would be good to share/have some online tools for interviewing candidates online, e.g. pair programming/coding sandboxes, shard white board tools. Maybe some of that content could be captured and used for the input of of the interview feedback form.
Introduction of participants didn't go really smoothly.
Some topics were missed initially, but questions were asked, so those topics did get covered in the end (like concrete next steps). Maybe add that by default.
Could have asked which people already knew about STAR. Part of that was not that interesting for me, however I do need to note that the experiences shared by the group were very interesting. For a next session maybe discuss STAR itself in less detail, and just have the group discussion on their experiences. Make next actions more clear.
Try and help include the whole group int he conversation and not just the people who are eager to give their opinion/experiences. Make it clear what the next steps are and what is expected of us.
It would be nice if there is a clear description for the follow up events like what are the action and expected outcome.
The session seems repetitive to the earlier session that HR did with some of us. So, not sure if it was intended but could be avoided based on the audience and it didn't add many new elements particularly around the STAR model of assessment.
its good to practice a mock :) , would be helpful and talk about the success for seen in Amazon
- Probably this should be more interactive with some case studies and hands-on tasks (e.g. provide a situation and give voting choices for responses). At the end, there should be a discussion around the responses
Some more practical examples
Skip the emoji-based "voting participation".
Can be made concise. Felt bit long, considering the content that was presented.
It was a long session. Maybe breaking it up over a couple meetings would have been better and you would have had more engagement from all. Outside of that I thought everything was good.
For me everything was very good, the conversation with Datta was really really good.
Technical aspects very clear and valuable for the team. Behaviours I should request more time to work on this topic with the team. Because they are good with a technical question.
All fine.
Team knowledge about the subject and the techniques used for a better interview experience and process.
As this was my first meeting about hiring people, I don't have a strong basis to point out what could improve, for me everything was just right
Elaborate and involve the team on Behaviours questions
More interaction with atendees using "menti.com" - not everybody is confortable in the starting sessions to open the mic and share experiencies.
A more behavioral approach would be good, in some moments, is was a bit too technical, mainly for developers that deal with source codes in a daily basis.
About Technical interview with Datta
Behaviors, how to extract it. whats the best questions for the moment.
Prior to the bar raiser program, my thought process about interviews was oriented primarily from an hiring manager perspective. So the interview would be more around testing the capabilities of the person and fitment for the role. However, now there has been a definite change in developing a more holistic view around the interview process - focusing beyond the immediate needs of a team towards a more organization perspective. This has certainly helped me in engaging the interviewee on different dimensions that I would not have done before and has also helped me strengthening in my own hire interviews.
One of the greatest challenge is to get a different view or a different angle of thinking for hiring the senior roles and hence the right decision. This bar raiser program has helped big way there by leveraging the "collective wisdom" to take the right decision for the organization and PIC
Bar raiser program gives a new colour to the hiring program, in which the interviewer is not driven by the pressures of the project /hiring team. Instead, looks at a holistic view of the candidate and his/her fitment into the Philips culture. It also imbibes into the candidate the Philips behaviours from day 0.
Moving away from the current execution mindset to creating a win-win situation for Philips & the potential new hire. Envisioning the potential hire to contribute and grow in resonance with Philips long term vision and strategy
Bar Raiser program gave an opportunity to look from a different perspective. It is no more just a technical round which I normally used to take but evaluating candidate on Philips culture. This has helped me to appreciate Philips Culture.
It helps our site to have a bai-raisers team, where we are working with them to training them, to have better interviews, we are supporting them to hire the best talents to Philips.
In my role as a hiring manager, I have not yet had an opportunity to leverage the bar-raiser program. Hoping to do so when we have opportunities for hiring new recruits.
My experiences for the bar-raiser sessions were very productive where the hiring department observations and my inputs were in-line (hence minimal discussions during de-brief or the mail conversations). And taking part in bar-raiser interview sessions helped me gain knowledge on hiring talent that fits our organization culture.
1) Having prepared questions based on the role requirement helped me to focus on responses from the candidate rather than looking for question on the fly during the interview. 2) Cross learning from various bar raisers. For example, In one of the de-brief where [name] took the bar raiser round for position in my team, i learnt some good practices of evaluating challenges candidate faced to relate with Philips behaviors. 3) Documenting the interview questions and responses helped in assessing the candidate objectively.
I have had multiple challenges that I have tried to convert into opportunities. Starting with the hiring process itself, and how I pioneered a discussion with the TA and leadership team at PIC to start this new bar-raisers. Currently, while I am part of multiple bar-raisers interviews, I am influencing interviewers to start documenting their feedback in a detailed manner!
Due to my full agenda I haven't been scheduled for an interview yet.
It has certainly helped me to re-affirm my love for talking with people especially on a 1:1 basis, diving deep into how the person's career interests evolved over time and their aspirations in the future. I have also realized that allowing one to introspect and brainstorm by simply setting up a scene familiar to them is a very useful technique to test the personality of a person. This has helped me in my 1:1s and coaching skills.
Haven't facilitated any bar raiser rounds, though there are learnings interms of how the other senior members who are part of bar-raisers are thinking about a particular role and that gave insights to different angle of thinking or expectation of a same role... Ex : [name] brought in a point of how a particular person would think 3+ yrs down the line , taking feedbacks from the candidates about the interview etc.. Liked those.
I personally feel its very important to make the candidate feel comfortable. This should be run more as a free -flowing discussion rather than an interview -- only then do we get insights closer to reality.
Ability to make the other person give his/her best in a time span of 60 mins or so by following the 'Socratic method of questioning'
2 Bar raisers and debriefs. Candidates are very receptive towards this concept and I see them enjoying the experience.
For me was the reflection on the candidate's interest to join Philips. The candidate really wants to join Philips? or are they just doing one more interview?
1. The ability to serve and be of use beyond the interests of my immediate team / current role…through this initiative, I have been fortunate to contribute to a larger cause across the organization. This is enabling me to demonstrate a different dimension of servant leadership and organizational citizenship behaviors within my sphere of influence. 2. I see this as a different way to bring in sustainable change and also be a brand ambassador for Philips. This initiative has provided me an avenue to contribute in every small way possible and I am enjoying it! 3. I really miss the F2F social / human connection with my peers/colleagues at work due to the COVID-19 pandemic WFH situation. Interviewing a diverse set of candidates has enabled to connect (even though for a limited duration) and experience the power of the human connection amidst all the constraints. I have also enhanced my ability to explore and flex through different interaction styles to suit the candidate.
When I select a candidate for the team, I understand the role and hence am able to quickly correlate to the candidate and assess fitment, The Philips values pave the guiding principles and certain inputs shared during our monthly discussions helped me learn and arrive at different questions to assess candidates for our culture fit.
Person's resume could bring you to the interview but one needs to check how would this person succeed in the role that Philips is hiring for. Look beyond the resume. Create role plays. Put person in unchartered territories to bring person's core personality into the discussion.
That when I interview someone, it's a reflection of myself. So, I try to be grounded in terms of the questions I ask. I do not ask any question to which I don't have answers, to which I haven't coded myself, and I know that it can be solved in 40 mins of time, from scratch. It's important for me to solve a problem in more than one way so that I can be better prepared and know my trade-offs well. At times, it also helps in offering new perspectives to the candidate and add value to the conversation.
I haven't taken any yet.
The bar raisers team is a fantastic bunch of people and being in that group, I learnt a lot about how everyone else approaches the interview process. So firstly, chat and learn from others, especially your peers and seniors. Secondly, role play is a great skill in understanding a person and practice that religiously. Finally, start thinking of interviews as a conversation and not an interrogation.
First would like to have a chat over the coffee to understand and get more insights about the person & style to tailor the suggestions. The general suggestion i give to all the new interviewers and have experienced lot doing is "You are not getting interviewed, you are interviewing... So be a listener and talk less ! " . More suggestions can be case by case..
Be prepared before the interview -- on the candidate's role, profile, etc. Plan discussion which starts with introducing oneself and then ask the candidate. Have ice breakers to make the candidate feel at ease. Give example/situations to help the candidate relate to Philips behaviours and then seek his/her past experiences which can relate to the behaviours. Carefully, look for contradictions -- an important indicator of integrity.
- Socratic method of questioning - Role paly scenario - Stone walling techniques
Introduce yourself, explain about the role and the focus of the interview and set the context. This makes the candidate relaxed, which can lead to a productive discussion.
Present a scenario to the candidate and understand how they will react. It could be a source-code, or could be a daily team routine and understand from the candidate: How they will feel. How they will conduct it. And how you can accommodate these behaviors in your team.
• Preparation prior to the interview is paramount (review of the resume, Job Description, past round feedback, red flags) • Evaluation needs to be structured and fact-based coupled with instincts • Rapport building is key. As bar raisers, we have a short window to establish that through the course of the discussion. It is important to create a cordial atmosphere coupled with mutual respect to enable candid conversations. • Start with the basics - invest time to understand if the candidate has clarity about the role based on past discussions with panelists. This is one of the important steps towards calibrating expectations and long term fit to Philips • Different strokes for different folks: (i) A template definitely helps to guide the conversation. On the same token, it is important to tailor the discussion thread based on the candidate’s profile and how the interaction evolves. (ii) It is important for the bar-raiser to effectively elicit from the candidate his / her ability to apply past / current experience to the role. (iii) Key areas that I make it a point to explore are cultural fit, behaviors, maturity, dealing with ambiguity and strategic thinking • Presenting role plays and scenarios provide important insights related to the value system of the candidate • Debrief is critical. (i) It provides the opportunity for the bar-raiser to put forth key insights that could potentially enable the hiring manager to plan the candidate’s transition into the role and ramp-up in a smoother manner. (ii) It can also serve a forum to understand common observations that stand out and also if there are any surprises that are not red flags but need attention. • As brand ambassadors for Philips, it is important for us to role model the Philips behaviors and above all ensure a memorable candidate experience.
Beyond technical and role fitment we need to look into candidates
Role plays helped me personally a lot.
Be prepared. put yourselves in the candidate's shoes, and provide the same experience to the candidate which you'd expect from any other interviewer. It is all about the experience and the value add that we bring to the conversation that helps us convert a potential candidate into an employee of Philips!
Let interviewee talk themselves about real situations and how they acted in those specific situations.
Learnt a lot from Datta - primarily how to document the outcome of an interview and notes from meetings. Also, learnt many new things by interviewing such a diverse set of people - from an operations manager to a senior research scientist.
Personally felt, my influencing and persuading skills went a bit high. Communicating big no as well as big yes in a pleasant way
Yes I learnt from a candidate, new tools on AI.
Soft skills : Critical thinking , Emotional intelligence Technical skills - DevOps
Too early to say.
Sure, mainly the source code aspects, where we can present a piece of the source code and can get answers or make questions around. I thought that it will be difficult due to time difficult, it is a short time for the interview. But, seems that you can guide one or two questions to make it possible. I like this approach.
• Ability to switch between different contexts wrt organizational talent needs across different organizations/ businesses in a seamless manner (switch between needs for Product Owner/Program Manager/Functional manager etc) • Enhanced learning in specific technology areas through my interactions with the candidate and self-preparation prior to the interview • Enhanced learning (breadth) about strategic directions of different businesses within our larger organization (Serviceability, Sleep and Respiratory Care, IGT devices etc). • This opportunity has enabled me to get exposure with regard to how other organizations within Philips and beyond are shaping their strategy in a fast paced world, what are their challenges and how they are addressing them • The ability to interact, present observations and contribute during the debrief sessions has been an enriching experience. These sessions provide an opportunity to interact with functional leaders and technical SMEs across different organizations.
Key learning: probing queries based on experience to understand persons ability to coach, mentor and participate as team player, approach towards problem solving as a team.
every interaction has reviled something new. So generically speaking yes - learnt a lot.
Yes. I have learnt that we don't have to ask complex questions to gauge the behavioural trait of a candidate. It is very important to be a keen observer. I have picked this up from the many mentors I have had in the past and at Philips.
Let interviewee talk themselves about real situations and how they acted in those specific situations.
Absolutely. Don't want to share the candidate name though, we interviewed a candidate for the Functional manager role and i was in a dual mind about the hire. The bar raiser round and the de-brief helped to drive decision on the hire.
Not so far. Though have reached out to the Bar raiser community on the best way to interview. I tweaked the pattern to suit my style and conducted the interview so as to capture all the Philips behaviours.
Yes (a) Felt a candidate has written all the right jargons and the next level depth was shallow ( took help from the bar-raiser community to validate this and it was proved right) (b) In 2 instances based on data - convinced the hiring business manager to take a clear stance "Current execution vs long term needs of the organization"
No such examples from 2 interviews.
Nope.
In situations that I have encountered, I have found that an open conversation with the debrief team has been very helpful to bring up concerns / red-flags / points of consideration and get them clarified.
Not yet.
Yes. I have asked other bar-raisers for second opinion in many scenarios. This helps me to leverage the bar-raiser community as a sounding board and validate some of my opinions with experts.
not yet
I write my first code here and that was a wow movement I may not be able to write a entire complex program on my own but I know how to read it now( will help me with adding value to team) I liked the Cerberus and the pull request process.
Rekindled my interest in coding Learned Github basics
My 3 biggest take-away points are: 1.) Concepts like inheritance and encapsulation were explained in simple manner. 2.) I learnt usage of Github and pull requests. 3.) With [name], I was able to practice paired programming.
- Java programming (& Oops concepts) - Using cerberus & Github - Way to train a complicated subject!
- Without any coding background, having learnt to write code, test it and execute it, it felt good. - Coding using an IDE made a lot of tasks easy for me. - I wrote a lot of code, and it felt good etc.
Yes, I can
Since I missed few sessions, I am not sure if I can help with Github .. but anything with coding I think I should be able to contribute
I can provide offline support for removing syntax errors in Java, using common features of Eclipse IDE, Gitbash, etc.
Can share the experience and code written
nothing as such
I think the course structure is right for any beginner
I have one input: If participants miss an important session, the next time around it becomes difficult to catch up. So the drop-out increases gradually. For important sessions (example: set up of IDE, etc.) it can be informed in advance that this is a key session. Also, recording or detailed notes of that key session may help.
Practical exercises definitely helps
yes , this would help me contribute better
Definitely would explore options to help the business
I have two ideas : 1.) Attempt to enhance a macro developed in VB that can detect empty table cells in a test report, check whether expected and actual results are same (ideally, they should not be), etc. I feel that I can attempt to apply VB :-) ! 2.) Look at the quality of code review comments in tools like Code Collaborator or TFS to ensure that code review is indeed effective.
Automate in my area of work, wherever possible
Could able find deduplications in code would help in order to improve the code quality.
You are just prefect :-)
Probably give some more problems to solve to the participants .
Datta can explain how certain concepts or ideas work in real life projects. For example, if Java Scanners are not closed, it may result in memory leakages, which over time, could result in performance of the system degrading.
Last few sessions were mostly not as effective as initial sessions. Suggest we could have take a actual requirement (in the form of BDD) & started to write test cases & code for the same
People engagement through out the program.
The way you the problem was broken down into pieces and made sure a person who doesn't have any coding background is able to absorb it with real like simple examples and then taking it a little higher in subsequent classes
taking continuous feedback from participants and taking course correction during the session His patience to deal with participants was amazing The way he explained the OOPs concepts using real life examples were simply great Overall enjoyed and gained from this learning session !! Keep up the good work Datta !!!!! You are an amazing teacher !!
Datta's patience is exemplary. His ability to take participants with different levels of maturity along is an amazing talent. Datta needs to continue both these attitudes.
- The lucid way of explaining a very complex concept - Slow & steady phase & engaging all involved. - Format of 1.5 hrs
Endless support and problem solving skills.
Anytime Feedback & Session Feedback
Summary
What other people said about the work in 2020: Anytime Feedback from 65 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
65 respondents| # | From | When | Words |
|---|---|---|---|
| 1 | Ramu | Q2-2020 | 67 |
| 2 | Bharath | Q2-2020 | 76 |
| 3 | Sajith | Q2-2020 | 241 |
| 4 | Brijesh | Q2-2020 | 285 |
| 5 | Miteshkumar | Q2-2020 | 143 |
| 6 | Sameer | Q2-2020 | 246 |
| 7 | Sundaresan | Q2-2020 | 159 |
| 8 | Mahesh | Q2-2020 | 290 |
| 9 | Sitangshu | Q2-2020 | 166 |
| 10 | Kiran | Q2-2020 | 180 |
| 11 | Nikila | Q2-2020 | 141 |
| 12 | Elaine | Q2-2020 | 125 |
| 13 | Sharath | Q2-2020 | 89 |
| 14 | Ajay | Q2-2020 | 682 |
| 15 | David | Q2-2020 | 250 |
| 16 | Jayaraj | Q2-2020 | 346 |
| 17 | Binod | Q2-2020 | 162 |
| 18 | Sapna | Q2-2020 | 149 |
| 19 | Prabha | Q2-2020 | 59 |
| 20 | Darlan | Q2-2020 | 102 |
| 21 | Binu | Q2-2020 | 134 |
| 22 | Aravind | Q2-2020 | 89 |
| 23 | Pattabhirama | Q2-2020 | 51 |
| 24 | Sudeep | Q2-2020 | 236 |
| 25 | Naveen | Q2-2020 | 99 |
| 26 | Maheswararaj | Q3-2020 | 77 |
| 27 | Sannihith | Q4-2020 | 88 |
| 28 | Dimpal | Q4-2020 | 21 |
| 29 | Jess | Q4-2020 | 121 |
| 30 | Lena | Q4-2020 | 372 |
| 31 | David | Q4-2020 | 207 |
| 32 | Pushkaraj | Q4-2020 | 181 |
| 33 | Ryan | Q4-2020 | 350 |
| 34 | Rani | Q4-2020 | 267 |
| 35 | Kiran | Q4-2020 | 244 |
| 36 | Jan | Q4-2020 | 70 |
| 37 | Sudhir | Q4-2020 | 154 |
| 38 | Rahul | Q4-2020 | 248 |
| 39 | Ravi | Q4-2020 | 209 |
| 40 | Suyog | Q4-2020 | 389 |
| 41 | Abhishek | Q4-2020 | 157 |
| 42 | Lakshmi | Q4-2020 | 175 |
| 43 | Kalavathi | Q4-2020 | 252 |
| 44 | Cristina | Q4-2020 | 284 |
| 45 | Manish | Q4-2020 | 169 |
| 46 | Ispiril | Q4-2020 | 144 |
| 47 | Ronald | Q4-2020 | 140 |
| 48 | Sobi | Q4-2020 | 129 |
| 49 | Rashmi | Q4-2020 | 202 |
| 50 | Ashwini | Q4-2020 | 122 |
| 51 | Sreekumar | Q4-2020 | 97 |
| 52 | Kshitija | Q4-2020 | 118 |
| 53 | Srinivas | Q4-2020 | 86 |
| 54 | Caroline | Q4-2020 | 134 |
| 55 | Rajendra | Q4-2020 | 76 |
| 56 | Rodolfo | Q4-2020 | 101 |
| 57 | Tejaswini | Q4-2020 | 102 |
| 58 | Anonymous respondent | 2020-03-02 | 21 |
| 59 | Anonymous respondent | 2020-03-02 | 45 |
| 60 | Anonymous respondent | 2020-03-02 | 30 |
| 61 | Anonymous respondent | 2020-03-02 | 32 |
| 62 | Anonymous respondent | 2020-03-02 | 32 |
| 63 | Anonymous respondent | 2020-03-02 | 57 |
| 64 | Anonymous respondent | 2020-03-02 | 45 |
| 65 | Anonymous respondent | 2020-03-02 | 39 |
Anytime Feedback
65 colleagues repliedWhat colleagues wrote
word for word“Eager to improve and inspire”
“Quality and integrity always Eager to improve and inspire”
To improve: Our interaction was specific to the SWCoE and I dont have enough data to comment on this.
“Datta has demonstrated Eager to Improve and Inspire, Quality and Integrity Always and Team up to Win.”
To improve: Customers First - describe the linkage to end user scenarios especially the UI or Web based applications with the Code Quality metrics being implemented. This would strongly answer the question for the team on how some of these code quality improvements also help from a workflow or a usage standpoint. Take Ownership to Deliver Fast - suggestions to the team on how we can effectively ensure the quality of deliverables we receive from other teams such as Research or BiUs to ensure that integrated delivery can be planned on time with the best available quality metrics.
“Definitely Eager to improve & inspire : This is one of the best quality i have observed in Datta, where he constantly willing improve himself while encouraging others to do so. This quality helped him to reach out to many business and create the acceptance Customers first : Also it is evident from many of the interaction i had with him along with business that he is keen on understanding the customer (Business) pain points and to address the same. He prob lot of question which helps in RCA and uncovering the exact reason for a problem area and also through these question the person answering also forced to think and reflect. This helps in more acceptance when SWCoE provides recommendation.”
To improve: Though there are no specific answer to this question, may be an area to look at would be to Team up to win, Where he could be enabler for more collaboration across team members, Brainstorming sessions on the areas SW CoE is trying to improve on business , approach to business, etc.
“Eager to improve and inspire, Quality and Integrity always and Take ownership and deliver fast are definitely the traits I have seen Datta exhibit from my interactions with him.”
“Eager to Improve and Inspire, Quality and Integrity always”
To improve: in the Bar Raiser team, Datta and few others were found to be more participative while the rest were more latent. Good chance to tap the weaker links of hte team and project them to the fore to drive greater synergies. P.S. This may well also be an area of improvement for the other participants but more from a leadership pov.
“(a) Eager to improve and inspire ; (b) Take Ownership and deliver fast; (c) Team up to win”
To improve: Datta is doing a great job and at this point of time, nothing specific on these areas are striking as areas of improvement. A remark on ' Customers first ' :
“Eager to improve & inspire, : I vouch for Datta's as a SW practices expert. While he is always willing to share his experience/knowledge around SW practices subjects, he also eager to look different approach which other team has taken. He generally opens up a very healthy discussion to look into the pors and cons of each approach and there by helps improve the over all quality.”
To improve: While Datta has immerse knowledge in good SW practices, one area which would make our engagement better would be if you can drive changes aligning with the business needs. If Datta can engage with project teams a bit more and understand the team culture and project priorities it can help him drive the SE transformation more effectively. I share this as an improvement area (from my perception), but newver the less he is already good in this aspect. This comment is just to move up his rating from good to great.
“Eager To Improve and Inspire and Team up to Win are real strengths of Datta”
To improve: Customer First
“In my view, one of Datta's strength is the way in which the Philips' behaviours: Eager to improve and inspire and Take ownership and deliver fast are demonstrated.”
To improve: One possible area of improvement is Team up to win.
“Eager to improve & inspire Quality and integrity always”
To improve: This is the need of the hour for PIC to have experts available as consultants and SMEs
“Eager to improve & inspire”
To improve: Team up to win. I chose this as I believe Datta has a lot to offer other sites beyond Bangalore and would like to see more x-site working through his leadership.
“Eager to Improve and inspire : This is one of the very string cultural behaviour Datta show cases in his work.”
“Eager to Improve & Inspire Your Detailed Approach of work, Solving Problems with in the legacy code of the project(I2M-RADAR) , towards quality initiatives , handling technical debts are amazing which creates a inspiration to all our team members and sets the benchmark with in the team . Peer Programming on handling Code Duplication of reducing 5k Lines of Code with in 2-3 hrs by categorizing the duplicated code and Team up to Win The SWCOE Initiatives & Guidance which are led by Datta to our business unit (I2M-RADAR) , which creates a culture with in the team to improve the code quality & way of writing code , testing it which helps Your diligence and detailed approach towards work have set a benchmark for the”
“Eager to improve and inspire Take ownership and deliver fast”
To improve: Over the last 6 months, I've seen Datta taking further steps related to Team up to win . He is contributing more and more to backlog items outside his default area of influence (PIC-B) and giving visibility on work in Cerberus for instance.
“Based on my past working experience with Datta, I would say Datta is very inspiring and influential person to any of his subordinate. He is a strong contributor for all the Philips behavior and also inspires and influences others on this part. If I have to pick top 2 Philips behaviors of Datta, I would choose Quality & Integrity always and Customer First.”
To improve: I feel at times Datta gets carried away with problems and analysis spending more time. Instead at times if we attack as a team there is a possibility the issue can be fixed in quick time. I way Team Up to Excel is one aspect where there can be improvements.
“Quality and integrity always Eager to improve & inspire”
To improve: Datta came up with excellent tools, that can help any code base repository. ASP is much benefited project from his code quality tool.
“Some of the biggest strengths I see in Datta are: Eager to improve and inspire Customers first Quality and Integrity always”
To improve: My interactions with Datta have begun since the last few months. I currently don't see any area of improvements for him.
“Eager to Improve Quality and Integrity”
To improve: Team up to win
“I've started to work with Datta past year during some actions about Center of Excelence .craft project. Datta has always been a very proactive person always prompt to help and letting us confident about our decisions and always ready to give us some support and many subjects. He is a role model for the Team up to win behavior, I'm always glad to work with him.”
To improve: Haven't seen any improvement area since we have worked just in a few subjects.
“There are the few behaviors which stand out during my interaction with Datta... 1) Team up to win - Always reach out to team and demonstrate passion to collaborate and create larger impact 2) Eager to improve and inspire : Often come up new ideas to improve maturity of craftsmanship in the organization”
To improve: Not a improvement , but would appreciate Datta can contribute to formal mentoring of few senior team members in my team.
“Team up to win”
“Datta is one person who is sought after in SWCoE and in other BU's as well. Especially I like the way he approaches a problem and his problem solving skills. During presentations/workshops, he supports his team members a lot. and sincere appreciations to it. His Articulation and communication is worth emulating.”
“Quality and Integrity always, Team up to win, Eager to improve”
To improve: Customers first, going by the definition of ‘customer’ as ‘payer or user of product or service’. I look forward to see sharper focus on transforming teams to focus on end-to-end quality. BTW I see Datta on this journey already.
“1. Very organized, has data handy at all times. Eager to improve 2. High on quality, tools and has a range of tools to help always.. Quality and Integrity always 3. Available for any queries any times and always eager to help. Team up to win 4. If takes any action, for sure does due diligence and reverts back. Take ownership”
To improve: 1. Many times team felt, can get more support by involving more. Seems there is an expectation mismatch, which has to be clear 2. Giving feedback can be done in a more positive approach than pin pointing mistakes.
“Datta, Thanks for the wonderful training "IWillCode" for the past 7 months. It's of-course not a simple task to make a bunch of people get interested in Java & follow up for such a long time. Your way of training & interactions makes the class very interesting & easy to grasp the fundamentals. I wish you continue & share your unique talent so that lot many others will also benefit from this. Thanks a ton!! Regards, Mahesh”
“Eager to improve and inspire - I admire this quality in you.”
“By my very limited interaction, I have very limited feedback. Datta is very clear in his communication and on his observations.”
“I have worked with Datta on programs/workshops/sessions for Interview Skills training for R&D managers within Philips to better understand behaviour interviewing. Datta contributes as a competency specialist, Software Center of Excellence and his engagement with different teams globally is phenomenal. His sessions are super interactive, he really gets everyone involved and even creates an open forum where everyone contributes their own ideas and thoughts. It would be wrong of me to pick on anything Datta could improve on as I feel I learn a lot from him in these sessions and I can improve myself by being involved in his workshops. I look forward to his sessions as I know I am going to learn something and people will share ideas.”
“Out of the 5 Philips' behaviors I see you are performing specifically strong on: Take ownership and deliver fast & Customers first.”
To improve: I believe you have a lot of potential to improve even further on the Philips behavior: Eager to improve & inspire.
“Datta has been demonstrating these behaviors during our collaboration.”
“Eager to improve and inspire Quality and Integrity always”
To improve: As far as I have known Datta, He adheres to all the 5 Philips' behaviours very well.
“Eager to improve and inspire: during the training it was hard not to be engaged due to Datta's ability to show and vocalize value. Team up to win: the partnership between TA and SW CoE is refreshing and has shown what can be done if we take cross functional partnership seriously. The result is impressive and between the two groups it allowed a strong delivery of what improvement can and will look like for finding the right talent. Take Ownership and Deliver Fast: The original BR roll-out, I jumped on a moving train and was blown away by how well you owned your space and more importantly knew what to own and what not to. Delivering fast was also very impressive when we had to ramp up the Skill Raiser in Blumenau. Because you knew where to jump in and own it things in a certain breadth and depth it was a fast and effecient ramp up”
To improve: Customer first would be the one area to think about. It is not that you don't have that as part of your job but communicating and exhibiting how the change or practice effects our customers could be a good area to bring up.
“you are a role model when it comes to take initiatives to a meaningful level exposure and implementation. There are quite a few example like Bar raiser, cerberus, mutation testing etc.. You have good clarity in communication, quick to understand the complexities, eager to learn and very open in taking feedback. Also working on the feedback. You are an real asset to the team. your keen interest in data/metrics is an added advantage”
To improve: It is not in particular about the behaviors. But how can the impact be measured in terms of outcome impacting end customers is a key area all of us to focus. Also make yourself visible, your thought leadership to guide at PIC dimensions.
“Datta's strengths are in the way in which he practices Eager to improve and inspire and Customers first.”
To improve: Probably, Datta could focus on Quality and integrity always.
“Eager to improve & inspire , Team up to win”
“Datta is very eager to improve and inspire. He was very instrumental in supporting the CPD tool problems and providing suggestions. He placed himself as part of our team to help us with the solution , a clear example for team up to win.”
“No doubt, Team up to win is the most deserved behavior and strength. Taking team to the common goal was the crucial challenge and which he made it possible by putting out of the way efforts.”
To improve: Eager to improve
“Team up to win - Datta has been instrumental in the BAR raisers program design and has contributed in areas outside his domain which shows his ability to collaborate and team up with cross functional teams. Another such instance is Datta's active leadership in driving continous feedback dialoue and culture dialoguesin the SW COE team.”
To improve: Datta has a rich experience of working in various technology companies prior to joining Philips. Datta can add value in brining the outside in perspective to our Sw CoE competency team..
“I have had the pleasure of engaging with Datta on several key initiatives this year - SW Excellence, Bar Raiser and Campus Recruitment Improvements. In all of these, I have seen him displaying all of the Philips behaviors to various degrees. However, I would like to call out 2 specific behaviours - Eager to Improve & Inspire and Take Ownership and Deliver Fast as those that stood out prominently in my interactions with him.”
To improve: Difficult to answer this question! I would recommend that he deepens his knowledge on some of the critical business and customer use cases so that he can align the software excellence initiatives more effectively bringing a tangible connection between software excellence and business value. Also, it would be great if he can take up active mentoring for leaders on technical connectedness if not doing already.
“"Team up to win" and "Eager to improve & inspire"”
“Eager to improve & inspire”
To improve: Team up to win
“Datta is a fine professional who exemplifies all the Philips behaviors, but if I have to prioritize within the 5 behaviors, following are the ones: Take ownership to deliver fast Eager to improve and Inspire team up to win”
To improve: Dutta has very nice way of challenging people with right facts and figures. He could do more of this which will help him personally also in establishing stronger PIC and SW CoE brand.
“Team up to win and Eager to improve and Inspire by having the customer in mind.”
To improve: Here I do not have any input. I could not observe the things that he needs to improve.
“I observe the behavior of training others in you. I associate this with you being eager to improve yourself and also act as an inspiration for others to do the same.”
To improve: I have not yet made enough observations to comment on areas of improvement
“I experienced his eagerness to improve and inspire first hand.”
“Eager to improve & inspire”
To improve: Sometimes, it'd be helpful if you read your audience. In one instance, you were explaining a lot of technical stuff, and I did not get a lot out of it. My suggestion is to read your audience and see how they are receiving the information. You do have a great enthusiasm to let us know.
“Eager to Improve and Inspire. Quality and Integrity always.”
To improve: From my point he is good at what he is doing so I didn't find any..
“Take ownership and deliver fast & Team up to win”
To improve: Eager to improve & inspire Customer First
“Eager to improve and inspire, Quality and integrity always.”
“In my interaction with you , you clearly demonstrated Team up to win, spirit”
“Eager to improve & inspire, Team up to win”
“Great coach, excellent knowledge, very patient in answering questions. Good team player.”
To improve: Continue what you are doing
“Team up to Win comes first in my mind given the very successful collaboration we experienced in 2020 wrt the Software Assessment Program. You helped tremendously since the first time we reached out to you with building the SW.Grow pages, the Bar Raisers concept and trainings, presentations to the SW CoE. I want to highlight that all other behaviors were clearly demonstrated as well . TA is now consolidated data points for the dashboard so that we can make it visible in 2021.”
“Team up to win”
To improve: Did not have much interaction with Datta. Not able to relate to one of the Philips Behavior.
“Quality and integrity always. Take ownership and deliver fast.”
To improve: Eager to improve. Team up to win.
“Datta has been a key contributor and relates to Philips behavior of Eager to Improve & Inspire, where we as a team worked together on improving candidates experience in the campus hiring.”
To improve: Datta has worked on Team up to Win, where working together surely brings in more ideas and better alignment
“Code Readability, Optimization and maintainability”
“He has very good understanding of structuring code properly leading to improved code readability and modularization. Also he has good knowledge on designing code for better testability and maintenance.”
“since Datta has enough experience in programming which adds more value to the coding.”
“During our first pair programming practice he wasn't available, so we can't comment on this section”
“Inspiring and always look for the best possible solution”
“He can add lots of value if we can have proper session with good topics to work on. He is very supportive and collaborative in nature which makes him good for pair programming .”
“Datta's approach was completely different in the processing of solving the bug. Which helped us in thinking out of the box solution.”
“During our first pair programming practice he wasn't available, so we can't comment on this section”
Ratings about Datta
from the Dattas_Dot_Connects record2020 Anytime Feedback about Datta (Q2, Q3, Q4 2020)
57 respondents Recorded
| Item | Answers | Mean | Scale |
|---|---|---|---|
| Likelihood to engage with Datta again | 25 | 9.52 | 1-10 |
| Likelihood to recommend Datta | 25 | 9.52 | 1-10 |
Session feedback
156 responses, average 9.32, NPS 86Every comment is on the page, by series.
Viva Engage
every post and comment from the all-activity page, 2020seen 217 times across communities Recorded
seen 682 times; not added to my own posts' figure
on 11 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 |
|---|---|---|---|---|---|---|
| 28 Apr 2020 | Hello everyone, | the engineering group Software Engineering… | 217 | 2 |
Posts by others that feature the work
| Date | Post | Actions | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|---|
| 18 Jun 2020 | Aravind: What is an easier and simpler way to enhance maintainability of your source code ? | the engineering group Software Engineering… | 270 | 7 | 12 | |
| 6 Aug 2020 | Sreekanth: A wonderful way to spend a Friday afternoon learning together with your colleagues !!! | PIC Bangalore | 274 | 19 | 5 | |
| 4 Nov 2020 | Maneesh: Subramanya Vellal, Dattatreya | Software Center of Excellence… | 138 | 2 |
Posts by others where I commented
| Date | Post | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|
| 6 May 2020 | Anand: Thanks for SW COE team for bringing up discussion about the below presentation and receiving it well.… | the engineering group Software Engineering… | 295 | 5 | 4 |
| 2 Jun 2020 | Chuck: At Philips, are there any coding standards being applied for general purpose C/C++ software? | the engineering group Software Engineering… | 247 | 6 | |
| 27 Jul 2020 | Sundaresan: .grow Learning Ambassadors, | the engineering group Software Engineering… | 246 | 2 | 10 |
| 26 Aug 2020 | Simao: If you had a time machine, what advice would you give to yourself when you first started working in SW? | the engineering group Software Engineering… | 272 | 1 | 2 |
| 2 Sept 2020 | Simao: [Shared message from Simao in the engineering group Software Engineering Excellence, 2020-09-02] | Philips Open Source Software | 46 | 1 | |
| 7 Oct 2020 | Vimal: Hi everyone as we are focusing on quality @ desk, git hook can help for validation as well as gating at… | the engineering group Software Engineering… | 193 | 4 | 9 |
| 13 Oct 2020 | Arun: Is there any library at client side that is used for Creating a ChatBot that can customize components inside… | the engineering group Software Engineering… | 150 | 1 | |
| 14 Oct 2020 | Simao: Can you post a very short snippet of code that makes you feel proud or ashamed and briefly describe why? No… | the engineering group Software Engineering… | 226 | 2 | 2 |
| 22 Oct 2020 | David: Best answer | Software Center of Excellence… | 118 | 2 | 1 |
| 22 Oct 2020 | Zephan: Where can I find & benefit shared observations? | Software Center of Excellence… | 136 | 4 | 2 |
Chat messages and posts
38 transcribed from screenshots“During a discussion with the SW CoE Team a couple of weeks back, Vellal, Dattatreya and Aravind talked about a small Java library called as Lombok and extolled its virtues in reducing the boilerplate code [...] Lombok helped us to reduce nearly 24% of duplication in one of our key modules. [...] Thank you for the session Sundaresan! [Seen by 204]”
“Thanks for SW COE team for bringing up discussion on the below presentation and receiving it well. [...] [reply, Vellal, Dattatreya, May 7:] Thank you very much Anand for taking your time and presenting this to our community. This session was very helpful for us to understand how TA has helped multiple businesses in setting up live KPI dashboards. The session was practical…”
“What is Xlint Java Compiler Warnings? If source code is compiled with -Xlint:all, it gives you other close to 15 types of warning [...] How to report the -Xlint:all warning inline into code review system? [...] Gated Pull Request CI [...] [reply, David, May 26:] Raising the bar to detect and enforce fix of Compiler Warnings at source is cheapest way to prevent potential…”
“We @ PHDSI took an initiative to invest in test automation code-quality, which is yielding us great results: Modularity resulting in low entry barrier for test engineers; Automate by default attitude; Gating test automation quality @ developer desk - Improves efficiency in test automation; Achieving near zero script errors. [...] Sudeep, Vellal, Dattatreya, Krishnan K,…”
“We are partnering SWCoE team on quality at desk initiative for our java-maven repositories. Thanks a lot for this initiative! During this integration we have made small improvements to the existing quality at desk infrastructure [...] 1. Gating for SuppressWarnings annotation [...] 2. Parent POM with quality at desk infrastructure [...] [Seen by 164]”
“The ASP team has been on a continous journey and engagement with the SwCOE team since begining of the year. [...] A big thanks to Vellal, Dattatreya and Aravind from SwCOE team for supporting us in this initiative. [...] In May-June, team had two training session with SwCOE team and were able to implement Two Factory Gates. (Local machine as well in Jenkins pipeline). [Seen…”
“Last Friday, I had a very nice talk with Dattatreya Vellal about my DevOps challenges within my Department. Datta (as he likes to be called) is a very knowledgeable and enthusiast person who already gave me some good tips. In our follow-up sessions, we will dive into more technical details and hopefully we can define together a solid roadmap with improvements. Thank you…”
“Nikila 11:02 AM: Thank you Datta for sharing a fresh perspective. Hareesh 11:02 AM: Thank you Dutta - very informative.... Murgesh 11:05 AM: Thank you very much Datta [thumbs up]. [Header shows 100 in the meeting]”
“Technical excellence in SW Leaders. Topic: Updates and best practice sharing. Presented the Quality @ Desk best practices and CI_CD initiatives undertaken in the Analytics Solution Platform team and my own journey of technically connecting with the Architects and team to bring about a cultural change in developer mindset towards Code Quality. Through some very strong…”
“Happy to share with you all that IGT Bangalore conducted Hackernoon 2020 where we saw 20 teams submitting their very interesting ideas. A 100% virtual event [...] The finals were held on 24th July and we had 3 judges - Dattatreya Vellal, Gernot & Saravanan - quizzing the 10 finalists. [reply, Vellal, Dattatreya: Very happy to have been a part of this hackernoon…”
“Brijesh: Vellal, Dattatreya for influencing with out authority. Rani: Datta: Driving Innovation: Building teh confidence on hsi idea, pilot it, influence, inspire and does not give up. Anuradha: Vellal, Dattatreya Very transparent and honest in his approach. Aravind: Vellal, Dattatreya the man who can pull people a crowd puller in our team [emoji] an inspirational…”
“Thanks Prateek for the good article and @Vellal, Dattatreya for the help ! Quality First !! [quoted post by Prateek: Save valuable time for yourself and your team: Automatic Python Code Linting!] [Seen by 283]”
“Done. All good. It extended because I talked about next week's agenda and had to explain the DEvOps initiative and few other questions he had. My own feedback: Good interactive session with the team as I said. You were clear on the language and speed so I think lack of participation could be mix of remote session + hesitation of some people to speak up [...] I liked your…”
“Great role model behavior for "know what you do, and know why you do it" Datta [emoji] .... good analysis of the pros and cons and good recommendation of an approach. For markdownlint, html, css, yaml and shellcheck (and others that I will add that are not for Java), are you happy for me to make a PR for superlinter with Java checks switched off? [...] it is more a learning…”
“We can combine Datta's LDAP scripting to collect info from sessions with the workday and Philips business org we have in the intranet to be consistent on collecting this data annonymized”
“Well done, Vellal, Dattatreya! The bar raisers initiative is part of the CTO news: [6 thumbs up]”
“[Datta:] Hello Kala, thank you for supporting the Bar-raisers program. I have created a public page of endorsements we have received from leaders, managers and candidates (including ones who were rejected). Wanted to share it with you [...] [Kala:] wonderful Datta... I am a fan of this program. I still remember our initial discussion in my office and your drawing on the white…”
“Manish: Cheers for Bar Raisers going Global ! Sitangshu: great work bar raisers team. Manish: Thanks to Sameer and the team for making PIC proud. Sameer: Thank you Manish, we will keep the steam on this and make sure it exceeds expectations...would like to pass on all credit to the Bar Raiser panels and the PIC LT”
“SWCoE Team Members: Datta, Brijesh, Aravind, Sudeep, Rashmi, Pankaj, Anuradha , Srimathi. Thankyou team for your good efforts in displaying 'Eager to improve and Inspire' and "Team Upto Win" actions and performances in our 1st SWCoE virtual F2F conference. 100+ people from different businesses globally joined the virtual event. [...] Key outcomes were focused directions for…”
“BEQR TMDs (3 of 3) [...] Submission for Q3 target of 7/11 .craft attributes is in progress, 2016/2683 = 75%. Q3 Workday data has been updated [...] Q&R team members have voiced their interest in continuing skill building as part of "I will code". Inputs are collated [...] .connect coverage is 52% (=1407/2683). Target: 40% [...] Risk: PHM business restructuring could impact…”
“S/W CoE Updates [...] Bar-raisers trained for EMEA, US and Blumenau [...] 94 .connect sessions conducted in BLR & EHV till Q3'20 remotely (Unit testing, mutation testing, Q@D, dead & duplicate code removal) [...] .waste: Mass deployment pilots in EDI, CCI-PCA, PM - in progress. 53 sessions covering 72 people as Observer/Observee [...] .source: GiTHub tool maturing & 362…”
“[...] Have you learnt a new skill? Learnt a lot from Datta - primarily how to document the outcome of an interview and notes from meetings. Also, learnt many new things by interviewing such a diverse set of people - from an operations manager to a senior research scientist.”
“However, in general I really like the page! Visually great structured and attractive. Did you ask the bar raisers for their consent? [Datta:] Yes. It's also in mail plus survey topic. There's a disclosure that says your non anonymous response will be used to create a page. [Lena:] Great. Really really well done. Its a great complete story. The TA team can be really happy that…”
“[Datta:] Thank you for your responses Minatee. Your responses have been captured via this page [...] [Minatee:] thanks Datta, we must thank you for drivng this so passionately. Keep it up”
“Sundaresan 10:36 AM: thankyou team. Sanjay 10:38 AM: Thank you entire team and Datta for the time and providing knowledge and skills. Thanks a ton. B, Arpitha 10:38 AM: Thanks a lot ... Datta and Kiran. Pankaj 10:38 AM: Thanks Datta [two cartoon images: BROKE THE BUILD, MERGE CONFLICT]”
“[cartoon images: APPROVED!, CAN YOU REVIEW THIS?] R, Rashmi 10:38 AM: Thanks a lot team. 10:41 AM: Thanks Datta...as always you are amazing. Sapna 10:42 AM: Team, I will have to drop out....thanks all for the wonderful team spirit you all have portrayed!...special thanks to Sundar for his witty comments. Maheswararaj 10:42 AM: I have to drop off now!!…”
“Pankaj 10:43 AM: dropping out - thanks all for the participation - it made the sessions and learning exciting. Meeting ended 46m 8s 10:45 AM. Rahul 10:46 AM: Thanks Datta, Kiran and SCOE team. Kiran 10:50 AM: Again, I thank all participants for their enthusiastic participation. This "I will code" session has been marked by the interest of its participants [emoji]!…”
“Hello Datta, thank you for all your work! I think that it went reallly nicely! [Datta:] It really went well.. thank you again for all your help and support. You are front ending this! [Caroline:] This is a beautiful example of how Team work is so impactful. Onwards with all the other teams now”
“I will join the whole meeting Datta. I saw the bar raiser agenda and would love to be there. I am so happy that what we talked about a year back in my office has become a reality and you are the man behind that. I would be glad to provide my input after you guys share. [Datta:] I am always humbled by your support. [Kala:] Count on my partnership with you on this always. [...]…”
“A big shout out to the SWCoE .tune team (ideator, observers, and volunteering observees) for their effort in identifying the waste patterns and giving an opportunity to tune them, thereby enhancing the SW community at Philips. Thanks to Sundaresan, and Vellal, Dattatreya for sharing their journey thus far in the .tune program with the goal, intent, and the next steps. I am…”
“[Sundar:] HI Datta - just sharing - yesterday post teh Aurora meeting - Simao sent this appreciation [embedded: Simao: Thanks again for the excellent work you are doing in driving .tune. I know how much hard and smart work is involved in pulling this together. You are doing a great job!! ... I have done similar initiative several times in the past and this time it has the…”
“Your Feedback on today's COP session. very informative; liked hands on session; very good; very good one; ok; thanks for the session; good session; good; good initiative; like more such sessions; good exposure to tools; relevant. [11 participants icon]”
“Great job Datta! First assessment done! Value added during year done! All good. [Datta:] Thanks Simao!”
“[Datta:] Hi Sameer, got a min? Wanted to talk about the Philips brand ambassador program. [Sameer:] Hi Datta, just saw your email on this. Would it be easier if we moved this to Dec 2nd week?”
“[Image on share.philips.com/sites/Continuousfeedback: fortune-cookie graphic reading 'Inspiring people to outperform' above a smiley gauge]”
“This is the last topic we planned for. Any additional topics someone would like to address or go more in depth? [Sundar:] we are good - I think. you covered everything well [emoji] [Datta:] Very well orchestrated! [Lena:] Thanks Datta for jumping in on the modules on the spot. We were not planning for it but it seems that it added value to the conversation. Thanks”
“I have had multiple challenges that I have tried to convert into opportunities. Starting with the hiring process itself, and how I pioneered a discussion with the TA and leadership team at PIC to start this new bar-raisers. Currently, while I am part of multiple bar-raisers interviews, I am influencing interviewers to start documenting their feedback in a detailed manner! [...]”
“Thanks Datta for your continuous support and guidance to the team. [Datta:] Happy to have helped Hemant. [Hemant:] thanks.. i tried by best with my experience in RI... But your guidance was very impactful. [Datta:] Looking forward to a productive 2021. I will be happy to engage with the team from the beginning so that we can hae a measurable and impactful changes and take the…”
Capacity & Time Investment
Summary
Where meeting time with colleagues went in 2020, from Datta's own monthly exports: 457 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 2020 to 31 Dec 2020 · from my own monthly exports473 meetings, 1.7 h per weekday across 262 weekdays Recorded
5 days had 6 h or more; hours are summed, overlaps are not removed
Meeting time by leadership action
each meeting counted once, under its strongest actionHours by action
From the meeting title and kind; 107 h in 132 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 |
|---|---|---|
| SWCoE Program new initiative-i will code | 27 | 40.0 |
| Weekly - Org Capabilities - Tech connectedness | 11 | 5.5 |
| Architecture and software guardrails | 5 | 5.0 |
| Pair programming slot | 4 | 4.0 |
| Elaborate on CI/CD improvement for Positioning Department | 4 | 4.0 |
| Org Capabilities - Intake Great talent | 6 | 3.0 |
| Recurring meeting for mentoring program | 3 | 3.0 |
| Sync meeting (Guardrails, Test automation and CI/CD) | 5 | 2.5 |
| Quick catch-up - Bar Raiser program | 3 | 2.2 |
| Sync Up | 3 | 1.5 |
| Sync up on Quality @ Desk | 3 | 1.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 2020 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
19 projectsEach project
Project pages
choose a project to open its pagePhilips Brand Ambassador interview and articles, leadership development centre, and a software architect job description
Aug 2020 to Dec 2020Material for a Philips employer-brand article about Datta (a transcript of his interview and two draft articles), the paperwork of a two-day Leadership Development Center, a Teams message about the brand ambassador programme, and a job description for a senior software reliability architect.
What Datta did
- The interview transcript is Datta speaking in the first person about his Philips work, starting as senior architect and then moving to the Software Centre of Excellence.
- In a Q&A article Datta answers on DevOps culture.
- Datta says in the transcript he runs Coding practice 202x and is a maintainer of two open-source repositories at Philips.
- Datta's Teams message to Sameer about the brand ambassador programme (screenshot) is shown on 23 Nov 2020.
Figures
Facts from the documents
- Self-reported in the transcript: about 29 workshops in 2019, with effectiveness 8.93 out of 10 and engagement 4.5 out of 5.
- Self-reported: unit test coverage in his earlier team rose from 63% to 86% in six months.
- Self-reported: Coding practice is a six-month programme started in February 2020, one 90-minute session a week, for quality coaches from a non-technical background.
- Self-reported: interviewing programme data of 71 Amazon interviews and 21 Philips interviews (counts only).
- Self-reported: he planned interviewing workshops for teams in the Netherlands, North America and Ireland.
- The 16 Sep and 25 Sep drafts of the article name Datta as competency specialist at Philips' Software Center of Excellence.
- The article states he is a maintainer of the open-sourced SCA project.
- The Q&A article's advice: know what is important, measure it, and improve it continuously.
- The Leadership Development Center was a two-day event on 3 and 4 December 2020 with a group exercise, validation interviews and a customer role play.
- The development centre folder holds a 360 feedback report (survey launched 11 Nov 2020, report generated 1 Dec 2020) and a leadership development report dated December 2020; their content is personal and is not recorded.
- The job description is for a Senior Software Architect / CG 70 in the IAP team, covering a software reliability framework, fault tolerance and capacity management.
- The job description asks for 15+ years experience and .NET C# development.
In colleagues' words
“Would it be easier if we moved this to Dec 2nd week?”