.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal

Post New Resource Bookmark and Share   

The Growth of software professional

Posted By:Santhakumar M       Posted Date: November 25, 2010    Points: 50    Category:    URL: http://www.dotnetspark.com  

The primary goal of this article is to make a programmer comfortable to work practically on projects adhering to proper software quality processes.

The Growth of software professional

If you are self taught programmer or working in a company which is not process oriented the title of this section can sound a bit bureaucratic to you. A good software product other than source code has proper documentation and process at place.

Every young developer in his initial part of the software career is hot blooded and full of enthusiasm.

The only goal he has in his mind is to complete the project. For these kind of young developers source code is the most important section in the complete project.

As time passes by and the young developer starts gaining experience depending on the type of the company and his number of year of exp his view point changes.

As to developer becomes senior source code becomes an insignificant entity and documentation form the most important part of the project from his perspective.

Maturity level of Software Professional

Level: (0-2 yrs)

                Developers having experience in this range give importance to source code.

They take pride and enjoyment to write cryptic and heroic logic. Developers falling in the category think documentation as bureaucratic. If not controlled properly they rarely will think to even comment codes. But yes software professionals in this level range have great technical enthusiasm. They love to get involved technically.


Level: (3-5 yrs)

                Software professional in this category have lot of maturity in technical section. They take pride in architecture work of the project. In fact many of the developers would like to see themselves as architecture in the coming times. That's a different thing as they get to more senior position they want to see themselves as project managers rather than in to technical. Software professional in the level think source code with proper comments and technical documentation as the most important deliverable. They have less focus on project planning, estimation and testing.


Level: (6-8 yrs)

                Software professional in this level give importance to technical documentation, estimation and source code. But they are bit soft when it comes to project planning and testing.


Level: (9 above yrs)

                This is the time he becomes a complete senior.


o   Source code deliverable

o   Planning

o   Monitoring

o   People issues

o   Escalation and Estimation


He starts following processes like CMMI and SIX SIGMA religiously

Above figure shows how senior and junior view project deliverables 


Further Readings:


No response found. Be the first to respond this post

Post Comment

You must Sign In To post reply

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend