tag:blogger.com,1999:blog-19452212.post5715691286014277469..comments2023-09-20T10:44:57.760-05:00Comments on Zen, Product Management, and Life: RequirementsBob Tarnehttp://www.blogger.com/profile/09907970828978458221noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-19452212.post-75654368320157912552010-02-21T05:08:23.625-06:002010-02-21T05:08:23.625-06:00interestingly i read it,it is so useful in project...interestingly i read it,it is so useful in project managment<br /><br />and we provide a project managment course,I wish u could have a look on it.....<br /><br />http://afdy.com/pmi<br />thankssarabecomhttps://www.blogger.com/profile/16939695177387151219noreply@blogger.comtag:blogger.com,1999:blog-19452212.post-17726190388611306132010-02-17T19:30:57.485-06:002010-02-17T19:30:57.485-06:00Ray - Thanks for the comment. I think the trick is...Ray - Thanks for the comment. I think the trick is to get enough info on a project to evaluate it against other projects so you can take on the most important one first. Then you start gathering more details on the project you're working on.Anonymoushttps://www.blogger.com/profile/04759182316367746632noreply@blogger.comtag:blogger.com,1999:blog-19452212.post-34658207953279590842010-02-15T07:49:26.274-06:002010-02-15T07:49:26.274-06:00Great post. Got to it from a tweet from @projectsh...Great post. Got to it from a tweet from @projectshrink. At the present time, we have a backlog of ~100 projects with 'Functional User Specs'. These are planned to be implemented over the next few years. Most of them are obsolete. Many address functionality no longer required, or changed in such fundamental ways that they no longer describe either the problem nor the solution. Yes, we do revisit the both the problem & the solution when the project finally gets the go-ahead. I'm not upset at this, because it's unreasonable to expect someone to know everything that's needed in advance, especially in light of such a rapidly changing environment.Ray Almonte, PMP., CSM, CSPO, Retiredhttps://www.blogger.com/profile/15254962655472826325noreply@blogger.com