Team Work

In life, when faced with failure, sometimes it is appropriate to work harder and put in more effort. Sometimes it is appropriate to change strategy and try something different. And sometimes it is appropriate to do both.

When we stop competing against a rival and instead start competing against the situation, we perform far better.

Checkout the complete Team Work PPT

Technical Management

Exception Hierarchy

• Exception hierarchy based on the project modules & module depth.
  

Utilities Package

• Utilities classes based on the module they are used the most.
• Keep common utility methods/functions in one place.
• Date Conversion, data type converter.

My Project Management Learning

Project Management

Technical Presentations/Brown Bag Sessions.

This technique worked very well both in IBM and Oracle. I always got an edge among the team members for taking presentations/brown bag sessions, both technically and financially (good appraisal ratings.)

More than one project at a time if free/wait time is more in one project.

Steve was right to put me on more than one project at a time when I was waiting on PeopleTools team for a hotfix on the defect I raised on IB message segmentation. I was able to utilize my free/wait time in one project to complete work on other project.

Actually Steve lended me to another team. :-)

This technique boots the personal learning and increases an individuals productivity.

However, this requires an extra bit of managerial efforts. Rajesh worked that out well by planning the number of days required to complete my work on CRM4HE and then he used to share my availability to Sunita for her project planning.

As a lead, one should always try to enhance (formatting, readability, clarity of idea) & track the emails sent by developers to management.

Rajesh used this technique as he used to ask us to write a draft emails and used to sit with

us to enhance the readability, visibility & flow of the emails to customers or external people.

Intranet document to track the issues / defects among the team members and later we can share the same to PMs for acceptance testing to open further defects.

This technique was cool and made me time independent. As I used to get the latest updates from the kix page on a particular defect/issue and since Kix has the "Notify" facility. It made easy to send notification to people when I used to put some updates.

Closure of the smallest issues in email chains.

Rajesh always emphasized on closure of all the discussion in email chains, regardless of the importance of the issue being discussed in email chains. This helped a lot firstly this used to keep everyone updated on oiur take of the issue. And enhanced clarity onclosure. And kept the managers informed too.

Developer should not spend time sitting with Q & A teams explaining the functionality instead a formal demo & hand off to Q & A should be targeted.

This is required as QA team might end-up replicating the same development test cases.

Exploit your manager's capabilities and make him look the best in a presentation.

Learn about the audience from your manager. Prepare the PPT in the flow and information manager thinks is the best for the audience. As the extra technical information in the PPT may raise anxiety or questions among some of the members of audience which may distract the presenter and rest of the audience from the actual planned flow of the presentation.

Always involve team members in technical/process discussions.

This adds an extra layer in the discussion wherein for the other required information manager can come in picture to get the complete picture.