.png)
Context
In a recent study with a sample of well over 100 web development projects, 76% of web application development projects sampled, reported their app dev project FAILED to meet timeline, budgeting objectives, and/or technical specifications... But, why did these app dev projects fail? What is our take away from the data? What is the common thread?
The 6 Most Common Points of Failure in the IT Project Engineering & Implementation Process
POF #1: UNREALISTIC PROJECT TIMELINE EXPECTATIONS
Without a realistic project timeline, the software project is destined to disappoint the product owner, from the beginning. We must set realistic timelines for project turnaround that take into account; actual tech resources available.
POF #2: UNREALISTIC PROJECT RESOURCE ALLOCATION (HUMAN & CAPITAL)
Without a realistic allocation of project resources, the software project is destined to disappoint the product owner, from the beginning. As a matter of best practice, we should set proper expectations for project turnaround that take into account; realistic human resource allocation and overall capital expenditure expectations.
POF #3: LACK OF EFFECTIVE WORKFLOW MANAGEMENT & LEADERSHIP
So many times I see this common mistake... Managers mistakenly hyper-focus on micro-managing the people underneath their department instead of concentrating on managing the workflow. Talented people will thrive within a structured workflow that is clearly defined, realistic, easy to use, and ready to roll. Talented people do not need babysitting. they need the proper structure and tools to do their jobs.
POF #4: LACK OF A STRUCTURED & STANDARDIZED DEPARTMENTAL WORKFLOW
Without a very clearly defined and structured departmental workflow, the software project is doomed from the beginning. It's a classic case.. "If you fail to plan out and implement a workflow, then you plan to fail...". People will thrive within a structured workflow that is clearly defined and realistic.
POF #5: LACK OF A STRUCTURED & STANDARDIZED INTERDEPARTMENTAL WORKFLOW
Without a very clearly defined and structured interdepartmental workflow, the software project is doomed from the beginning. It's a classic case.. "If you fail to plan out and implement a workflow, then you plan to fail...". Different departments and whole companies will thrive within a structured workflow that is clearly defined and realistic.
POF #6: COMPANY LEADERSHIP FAILURE - BLAMING THE SYSTEM ENGINEERS & DEVELOPERS HAS BECOME NORMALIZED COMPANY CULTURE
If a company continues to see high turnover of Engineers & Developers, then the problem usually lies within the overall structure (or lack thereof) of the company workflow itself. Leaders should always keep their egos in check and realize that if their department or entire company has high turnover, the problem is usually not the employees, but the lack of structure or instruction/training in workflow. Stop blaming the workers for the lack of proper structure, instruction, and training! When blaming the employees for the failures of leadership has become the company wide accepted norm.. then the issue has become a cancer within and company is destined for failure.
Conclusion
It is crucial to the success of the company that the leadership realize an important truth... If there is continued high-turnover of employees within the department, company, or project, then the problem usually lies within the overall structure (or lack thereof) of the project workflow itself. Leaders should always keep their egos in check and realize that if their company has high turnover, the problem is usually not the workers themselves that are the point of failure, but a failure of leadership to provide structure in workflow and/or instruction in proper workflow. It is time to stop blaming the workers for the failures of leadership to provide proper structure, instruction, and training.
.png)
