2014
The year I moved from contributor to leading work for the India team: point of contact for the application intake redesign, a phased clean-up plan from a root-cause analysis, My Accounts moved to the data layer and a place for the India team in re-architecting the product. Led the India team through a 400-fix release on its planned date, the standard 834 enrollment messaging proof of concept and the plan selection rewrite. Founded TExeter, a company-wide tech community that leadership formally thanked me for after six months.
In numbers
- 400+bug fixes in one release
- 3consecutive reviews rated consistently exceeds
- 834enrollment messaging end to end
TExeter from idea to company-wide in 6 months. 3-part design patterns course.
What mattered most
- 01
Thanked for six months of leading TExeter
Six months after TExeter began as a meeting-room discussion, the managing director and HR head wrote to thank me for the leadership and guidance that made it a company-wide community.
- 02
Rated for bringing the India team into the re-architecture
My review said I had built enough credibility with the US architecture team for the India team to become stakeholders in re-architecting the product. It also credited the My Accounts migration, the enrollment messaging proof of concept and how I led junior engineers.
- 03
Proving standard enrollment messaging end to end
I led the proof of concept for sending standard 834 enrollment transactions through an EDI integration platform and demonstrated it to the product and partner teams. A week later, files were processing end to end.
- 04
Leading a 400-fix release to its planned date
I led the India developers on a release that cleared the bug backlog with over 400 fixes. The India team did almost all of the work from development to QA, and the release shipped on its planned date.
- 05
A clean-up plan from one reopened defect
A portal defect kept getting reopened. I took the developer's root-cause analysis, found the same dead, repeated and tangled code across several portal controllers and proposed a three-phase clean-up to the delivery head.
What people said
“You all did a bang up job in getting this release out.”
By month
Also in 2014
- 16 December 2014Leading the plan selection rebuildProject
- 15 December 2014Joined the office emergency response team and wrote up its first categories and protocolsProgram
- 20 November 2014Set the India team's ticket rules for measuring quality: due dates, status, deployment links, root causeProject
- 21 October 2014Volunteered to interview at a campus drive and first asked HR for the metrics we were hiring againstHiring
- 15 October 2014Organized a one-day code-a-thon for the new hire training program, recognized by company leadershipProgram
- 16 July 2014Launched TExeter Times, the company's internal tech newsletter, with the TExeter teamProgram
- 11 July 2014Prepared and taught a three-part design patterns course for colleagues in the Exeter University programTalk
- 4 July 2014Bringing every project into one tech communityProgram
- 23 June 2014Q2 2014 review (Mar to Jun): consistently exceeds; mentored the support team and joined the redesign teamReview
- 19 May 2014Listed in the exchange product's US development and support structure next to the US product leadsRole
- 21 April 2014LinkedIn recommendation from my former IBM manager, an executive architect, on reliable deliveryRecognition
- 3 April 2014Owned the My Accounts revamp through releaseProject
- 28 March 2014Rated consistently exceeds for initiatives beyond the projectReview
- 20 March 2014Named India point of contact for the application intake redesign, which adopted the portal UI I had shownRole
- 4 March 2014Organized the fun events and puzzle contest at Tarang 2014, the company's annual eventProgram
- 11 February 2014Trained about 30 Exeter engineers on adopting agile-like practices in the company training programTalk
- 7 January 2014LinkedIn recommendation from the department head whose students and staff I taught in a 2012 Java seminarRecognition