The success of a software project developed using an adhoc development approach relies heavily on the:

An ad-hoc development approach, often termed the "code-and-fix" model, lacks formal processes, structured planning, and comprehensive documentation. In this unstructured environment, there are no detailed requirements or design specifications to guide the team. Consequently, the project's success or failure is almost entirely contingent on the technical proficiency, experience, problem-solving skills, and informal communication of the individual team members. The team must compensate for the absence of a defined methodology through their personal expertise and "heroics" to deliver a functional product.

A. The ad-hoc model is fundamentally characterized by a lack of high-quality, stable requirements; success must therefore depend on other factors.
B. Detailed design specifications are a hallmark of structured, plan-driven methodologies (e.g., Waterfall), which are the antithesis of an ad-hoc approach.
D. Due to the absence of upfront planning and estimation, ad-hoc projects are notoriously difficult to manage and are often late and over budget.

1. Pressman, R. S., & Maxim, B. R. (2020). Software Engineering: A Practitioner's Approach (9th ed.). McGraw-Hill. In Chapter 4, "Process Models," the text describes the "code-and-fix" model, noting its applicability for very small projects where "the developer's memory and skill are all that is needed to create a successful outcome." This highlights the direct reliance on individual capability.

2. Sommerville, I. (2016). Software Engineering (10th ed.). Pearson. In Chapter 2, "Software Processes," Sommerville discusses informal and agile processes. Ad-hoc development is the most extreme form of an informal process, where the development team invents the process as they work. In such a scenario, the "competence and experience of the people in the development team" (Section 2.1.3) become the critical success factors.

3. University of Calgary, Department of Computer Science. (n.d.). SENG 403: Software Development Methods and Tools, Lecture 02 - Software Process. Course materials often describe the ad-hoc model as relying on the skill of the developers. It is noted that this model works only if the developers are highly skilled and can manage the complexity without a formal process structure.