A project is a temporary endeavour producing a unique outcome — bounded in time, cross-functional, introducing change. Distinct from business-as-usual (“BAU”) work.
Key facts
Six characteristics: change, temporary, cross-functional, unknown, unique, varying size/time.
Software projects historically fail at ~70%: only ~20% wholly succeed.
Top success factors: executive sponsorship (15%), emotional maturity (15%), user involvement, skilled resources.
What is a project?
A temporary endeavour to create an unique product, service or outcome.
Provides strategic alignment of key activities and visibility at the appropriate levels.
Mechanism to prioritise activities (Benefits, Regulatory, HW Refresh).
Allows organisations to deliver change in a structured and formal manner outside of BAU.
Effective and efficient management of organisations limited resources (people & $‘s).
Establish ownership and accountability - Process and the Benefits.
Provide clarity, buy-in and agreement across what will be done, when who why and outcomes.
Software Projects
History tells us we have failed (over 70%) Roughly 30% are successful, 50% are challenged (excess in time, budget or people) and only about 20% are completely successful.