Projects can be of varying sizes and complexities. It involves a set of elements such as Cost, Time and Resources. These elements are no doubt the driving force of projects. The sufficiency or otherwise of these elements defines the success or failure of a project. It is important to state that an element that drives a project needs to be controlled. When projects fail, often times, people are blamed and queried either for their action or inactions. A project is likely not to fail if a methodology exist and more importantly, if it is adhered to. A very good methodology is PRINCE2. This methodology has proven over time to be a set of best practices which if followed on projects, the outcome is Success! Below are some of the reasons why Projects fail. 1. Lack of a Business Case: A business case as it were is the justification for embarking on a project. 2. Poor estimation of cost 3. Poor estimation of time 4. Lack of control check which results in sub standard products 5. Lack of objective project status review 6. Poor communication with project owners 7. Non adherence to product acceptance criteria 8. Lack of ownership of project management roles 9. Poor scheduling as a result of poor coordination of resources. 10. Lack of planning In subsequent postings, I will touch on these areas in more details

Some name

Kehinde is a senior SAP Security and GRC consultant. He has several years of SAP authorizations, GRC, and Basis experience. In the past, he managed teams to coordinate security, GRC, and Basis administration activities within a multinational environment and operated as an independent consultant, performing SAP system audits and SAP GRC Access Control implementations.