tag:blogger.com,1999:blog-35841277.post5045897277150812491..comments2022-03-31T08:17:06.018-04:00Comments on Pavel Veller's blog: RequirementsPavel Vellerhttp://www.blogger.com/profile/11955809016226023639noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-35841277.post-10130081821584452662008-11-12T17:46:00.000-05:002008-11-12T17:46:00.000-05:00It's a big mystery for me over the last few years:...It's a big mystery for me over the last few years: why major part of people (80% I believe) in any software team I have seen do not have instinctive perception and understanding that documentation of what you should do and what you are doing is NECESSARY. No matter if you agile or something else, this is derived from something else, like you must have a meal at least once per day or you need to breath.<BR/>My suggestion (I'm not a psychologist) that such things can't be teach in any school. Maybe the good solution is to detect a proper person for a software job by some sophisticate criteria when that person is young enough yet and leave "unintentionally" few good books on software development processes on that boy's table. Maybe it will help.<BR/>Nowadays there are almost no software projects which can be regarded as "easy" projects. But still I see that most of developers never even comment there code.<BR/>BUT there are also good signs. I see in my current team some guys who do comment the code, who are not thinking in standard way like "I am developer and I don't give a shit for writing some requirements and documentation". I like to work with those who can help me as a PM in my PM work, who can take an idea and advance it on paper to a description of a task. I believe that I can be the engine turning round such abilities in a part of the team and that makes my life brighter and brings some fun :)Alexander Arendarhttps://www.blogger.com/profile/03197601507172567746noreply@blogger.com