Archive for the “Where does the value go?” category
Where does value go: Value loss through project delays
by jed simms on June 23, 2010
You can destroy value by delivering the projects late thereby delaying the start of benefits realization. Each day/week/month the project is delayed the benefits are also delayed. The actual value lost is at the end of the value realisation period (…)
Where does value go: 20% of available value delayed due to late benefits delivery
by jed simms on June 16, 2010
You can delay the realisation of benefits that could be generated and ‘banked’ during the project by not focusing on their progressive realisation. If you see benefits as being enabled and delivered only at the end of the project you‘ll (…)
Where does value go: 5% of value lost after realization – gained but not sustained
by jed simms on June 9, 2010
You can destroy value by not actively sustaining achieved benefits, allowing old habits, old processes and unnecessary extra steps to be reinstalled, diminishing the net value realized. Once gained, benefits need to be actively sustained. Value loss, after all of (…)
Where does value go: 5%-50% value loss from failing to realize the benefits at the time of implementation or post project
by jed simms on June 2, 2010
You can lose value by not effectively planning, tracking or governing the delivery of benefits at the time of implementation and post-project, thereby allowing them to ‘fall by the wayside’. Post-project benefits can frequently represent over 50% of the available (…)
Where does the value go: 5%-100% value loss from scope changes
by jed simms on May 26, 2010
You can lose value by ‘adjusting’ the project’s scope to fit within the project’s timeframe or budget. As few projects can actually align their project activities to the planned benefits, any scope changes are usually done with little to no (…)