tag:blogger.com,1999:blog-4215962051788443675.post4921191287489767700..comments2023-11-16T01:11:44.811-08:00Comments on IMistaken: The Mistake Programmers makes with RequirementsLior Friedman:http://www.blogger.com/profile/09488722485273801828noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-4215962051788443675.post-78409203779088628162012-06-13T22:00:39.059-07:002012-06-13T22:00:39.059-07:00@yael, Communication is the only way to get knowle...@yael, Communication is the only way to get knowledge from one place to another.<br />problem is, many of us developers has the notion that we can stay passive and that knowledge will be handed to us on a silver plate. When that doesn't happen we say "the requirements are not good enough"Lior Friedman:https://www.blogger.com/profile/09488722485273801828noreply@blogger.comtag:blogger.com,1999:blog-4215962051788443675.post-26942794237396837212012-06-13T21:56:34.227-07:002012-06-13T21:56:34.227-07:00@Yogev, if you can reach that state that is great....@Yogev, if you can reach that state that is great. Most often then not people involved in defining the requirements (product, analysts,...) and the people who actually develop the feature consider themselves to be different team. which of course is one of the things that needs to be changed. in that state they find it very hard to really share responsibility. And most often they they use role & responsibility to prevent this sharing: we are the ones in charge of writing the spec, you are in charge of developing & tetsing it.Lior Friedman:https://www.blogger.com/profile/09488722485273801828noreply@blogger.comtag:blogger.com,1999:blog-4215962051788443675.post-91857443536995164232012-06-13T20:10:56.647-07:002012-06-13T20:10:56.647-07:00From my experience the best way to succeed in this...From my experience the best way to succeed in this is communication. having frequent reviews, also including QA people, achieves the best requirements understanding and design, that all parties feel they own, since they were involved in its design. Also, different people, with different points of views see different holes in the design and usually brings different ideas for solving them.Yaelnoreply@blogger.comtag:blogger.com,1999:blog-4215962051788443675.post-22300631058229609722012-06-13T03:37:42.760-07:002012-06-13T03:37:42.760-07:00Hi Lior,
great issue, and very well put in words.
...Hi Lior,<br />great issue, and very well put in words.<br />in my personal opinion there shouldn't be your or mine responsibility rather our responsibility. (for both programmers & Project managers).<br />when looking at this issue in the 'Agile way' - there is a challenge, and there is a team. The team will have the best achievements when working together on it.<br />putting into practical - it should be a process of tuning between the programmers need and the project managers to apply.<br /><br />Thanks,<br />Yogev Tal,<br />consultant & DevManageYogev Talhttps://www.blogger.com/profile/09406900861928276027noreply@blogger.com