This certainly is a great self help group ;o) I'm going through many of the issues cited by others and the advice given is very helpful. I'm currently battling our management's shiny new toy - SCRUM. They want sprints delivering real customer value starting today, but we don't have a single architectural decision made, we are still at the "should this be java or .net" stage of the project.
One thing that is a catch 22 for an engineer is that it is sometimes appealing to take the project management job in order to be able to obtain the responsibility to make the technical decisions. I've done this previously, I took the PM job and got to make the decisions. I then faced the other issues of double jobbing and long hours. Currently I am purely technical and in an "advisory" role so I have to be very careful to avoid being labelled as "arrogant, disruptive, non- business focused etc". Neither role is ideal and it comes down to the old saying "no matter what they tell you, it's a people problem". And I must realize, that I am part of that problem. My best ever job was when I effectively "partnered" with a PM, he trusted my judgement and I totally respected his managerial skills. We worked as a team and achieved a great deal and shared the success. So my advice is to find the right people to work with. Look for trust, mutual respect and complementary skill sets. Paul
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
