tag:blogger.com,1999:blog-7285826952643196670.post5801978053960576553..comments2009-05-20T12:56:27.767-04:00Comments on Richard Kasperowski <br>agile, mobile, technology, and more: Why there should be a "release backlog"Richardhttp://www.blogger.com/profile/13955040745900922376noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7285826952643196670.post-15866647752255770592009-05-20T12:50:18.634-04:002009-05-20T12:50:18.634-04:00Mike suggests that the context of his argument is ...Mike suggests that the context of his argument is "all projects that are not being done as fixed-scope contracts". Your say your teams operate in that context. It seems you actually agree with him. <br /><br />In any event are there any other contexts in which a release backlog is appropriate?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7285826952643196670.post-64964891989822976352009-03-09T04:13:00.000-04:002009-03-09T04:13:00.000-04:00Have not checked the referenced posts yet (feel th...Have not checked the referenced posts yet (feel they are worth). Fully agree - fixed price contracts (fixed scope contracts) need to have limited set of features. In addition to the facts enlisted in this post, may add that usually fixed scope contracts may imply final payment upon acceptance. Periodic enhancement of the backlog may lead to additional obstacle with acceptance (payment).mikaljahttp://www.blogger.com/profile/00233276968941567756noreply@blogger.com