<?xml-stylesheet type="text/xsl" href="https://emersonexchange365.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>No more rolling the dice when accessing project cost and risk. Why not try a crystal&amp;#160;ball?</title><link>/services/b/implementbuild/posts/no-more-rolling-the-dice-when-accessing-project-cost-and-risk-why-not-try-a-crystal-160-ball</link><description>Emerson’s Gordon Lawther shared ideas in project cost estimation and risk assessment. His abstract: Every company has a method to estimate cost and access risk when compiling a business case. In many instances the data resides in a spreadsheet containing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator></channel></rss>