...what is wrong with the entire development process...
...what is wrong with the entire software development lifecycle process in the company? what went wrong? my first initative was to check on the entire project - tms, what went wrong in the project. was the project in a successful mode?
after investigating on the project with the outcome as posted earlier on, now, my next focus is, was there anything wrong at all with the technical side or rather the development process...
i have the privilege talking to my newly elected technical lead in the project, which i strive hard to get the pm to endorse him. we had a wonderful chat over the phone and a face to face chat. so, i ask, is there anything wrong or rather anything that causes distress in the development team? hohoho...indeed there are alot of issues with the programmers. when i heard the stories, i was like, wtf man...and people is always blaming requirements that is the main problem. dohh, sa have our own processes, our own documentation, download session, etc...but, wtf, how about the programming side? the technical side?
things i gathered from this colleague of mine:
1. no technical documentation at all.
2. architects has the final word.
3. coms are given to me and i am supposed to follow. no question asked!
4. i don even understand wtf this com is all about. need time to understand.
5. the com cant even do wht is required.
6. reuse codes - f man. what! i cant even understand the "high" level of this guys coding.
7. f man. these codes have no comments. how to expect us to read and understand.
it seems that programmers need a download session and to be re-trained again on the standards and processes in our company. now, who knows all the things in the programming side. what are we supposed to do. who are we supposed to listen for standards? listen to my experience? do we really have the standards and documentation set? if yes, where are there? are there no enforcement? which is more important - setting standards or enforcement of standards.
the more i look at things in this project, the more i learn how important teamwork is. not only teamwork is important, but the communication within members. yes, "gods" might be right, but how do we challenge "gods" and give them a piece of our mind.
WHAT CAN WE DO TO MAKE THINGS BETTER?
after investigating on the project with the outcome as posted earlier on, now, my next focus is, was there anything wrong at all with the technical side or rather the development process...
i have the privilege talking to my newly elected technical lead in the project, which i strive hard to get the pm to endorse him. we had a wonderful chat over the phone and a face to face chat. so, i ask, is there anything wrong or rather anything that causes distress in the development team? hohoho...indeed there are alot of issues with the programmers. when i heard the stories, i was like, wtf man...and people is always blaming requirements that is the main problem. dohh, sa have our own processes, our own documentation, download session, etc...but, wtf, how about the programming side? the technical side?
things i gathered from this colleague of mine:
1. no technical documentation at all.
2. architects has the final word.
3. coms are given to me and i am supposed to follow. no question asked!
4. i don even understand wtf this com is all about. need time to understand.
5. the com cant even do wht is required.
6. reuse codes - f man. what! i cant even understand the "high" level of this guys coding.
7. f man. these codes have no comments. how to expect us to read and understand.
it seems that programmers need a download session and to be re-trained again on the standards and processes in our company. now, who knows all the things in the programming side. what are we supposed to do. who are we supposed to listen for standards? listen to my experience? do we really have the standards and documentation set? if yes, where are there? are there no enforcement? which is more important - setting standards or enforcement of standards.
the more i look at things in this project, the more i learn how important teamwork is. not only teamwork is important, but the communication within members. yes, "gods" might be right, but how do we challenge "gods" and give them a piece of our mind.
WHAT CAN WE DO TO MAKE THINGS BETTER?
posted by jeeyon at 6:49 PM
0 Comments:
Post a Comment
<< Home