[Techies Bytes] The ANATOMY of A Typical Indian software Develope, And Your role as Development Manager.

1 view
Skip to first unread message

Anjani kumar

unread,
Jun 17, 2012, 1:31:00 PM6/17/12
to techie...@googlegroups.com

The ANATOMY of A Typical Indian software Developer and  Your role as Development Manager.
How can you describe a real Developer?
1-      Technical,

2-      Looses concentration,

3-      Works on interest,

4-      Delays on delivery,

5-      Often loves Mentorship

6-      Intelligent and Innovative,

7-      Emotional,

8-      Experimenting,

9-      Rookie,

10-   Straight forward and less diplomatic,

11-   Respect knowledge,

12-   Able to judge his Gurus,

13-   Mature and needs strong bonding to deliver results,

14-   Individual contributor but Collaborative.

15-   Respect thoughts.

16-   Is not just a follower.

17-   Challenges design’s and is open for feedback.

What makes them happy?

·         New and challenging work.

·         An honor and respect which they deserve.

·         A Feeling of being safe.

·         Not being bound to work place.

·         To be freed to work from anywhere.

·         Not being bound to delivery pressures.

·         Not to be asked for testing their products as it’s the tester’s job.

·         Not being strict on time.

·         Party.

What makes them performing?

·         Unless a Task does not interest’s you? You will not be driven to perform.

·         Once a Job interests you, you start getting yourself indulged in to it.

·         And your interest drives your performance.

What makes the Job of Development Manager and Architects tough?

·         Dev Manager and Architects are the heart of any team, They are mentors Guru Brother and Friends.

·         Their stake holders are PM, DEVS, QA and client.

·         It’s their Job to make the boring task interesting while considering delivery commitments with product quality.

·         Quality comes with understanding of the problem and the depth of the technology in which you are designing the solution.

·         How can you deliver quality solution and design to be much independent of underlying technologies? Technology should be a medium to realize your solution artifacts.

·         Another biggest challenge that they face is setting the right expectations between PM and the Development Team, this becomes challenging when you start working with a novice and less mature Program managers and Project managers. There is a quite often chance that you get such people to work with because of porous hiring and promotions policy.





Ah.. So many constraints!! L How can you give Disney effects to your Stake Holders?  When you have to  fight every day to meet your targets respecting  internal commitments as well as external unknown forces such as wrong placed team and PM in itself.

Why not Client?  If you deal with your client on the terms and set the right expectation you are mostly done, however cruel exceptions always exist.

Many of big corporate employee do feels that Doing the JOB right does less than involving yourself in the extracurricular activities like Cricket, Football and social activities, this further gives one an easy promotions as your small work gets easily highlighted to top shots, leaving many talent responsible for the profit of company burning at much lower level than they deserve.

Every day you have to deal with People who are wrong positioned disturbing the complete chain below.

Does this means you panic? No Just get the job done without any fuss.

Some of the best bet to keep writing to your developer “You Rock……….”:-

1.       Understand your team well from capability, aspirations, emotional and social stand point.

2.       When you design a solution add modules which have some out of the box design.

3.       Developers and techies like’s doing and exploring new areas.

4.       Always review the code or have strong code review practice and fall back chain.

5.       Allow unit testing as per the time lines provided.

6.       ASK developers to write down and comment on all the scenarios that they are going to code for and what will be there testing strategy?

7.       Review it with the leads and give instant feedback.

8.       Be as friendly  with your team as you can, this makes you to understand people conflicts and sense it early to fix the team bonding issues.

9.       Take out the individualism from mates and make them to conflict  but able to align to the best solution,

10.   Challenge mates in a natural way to deliver and meet the commitments.

11.   Giving feedback mostly goes negative but praising someone doing good and getting him praised from someone who is underperforming forces the underperformer to perform.
































--
Posted By Anjani kumar to Techies Bytes at 6/17/2012 10:31:00 AM
Reply all
Reply to author
Forward
0 new messages