Software Development Process Quotes & Sayings

Software development is the process of creating a computer software.
It includes preparing a design, coding the program, and fixing the
bugs. The final goal of software development is to translate user
needs to software product, while continuously improving the team
and the process. — Paulo Caroli

The problem with traditional approaches to abstraction and encapsulation is that they aim at complete information hiding. This characteristic anticipates being able to eliminate programming from parts of the software development process, those parts contained within module boundaries. As we've seen, though, the need to program is never eliminated because customization, modification, and maintenance are always required-that is, piecemeal growth. — Richard P. Gabriel

If the DHS insists, as bureaucracies are apt to do, that open-source must be certified via a sanctioned, formal process, it will interfere with the informal process of open-source itself. It seems to me the DHS is trying to turn an open-source development project into a Microsoft (or IBM or Oracle) software development project. And we know what that means: more, not fewer, errors
security and otherwise. — Mark Hall

The process of software development doesn't feel any better than it did a generation ago. — Rob Pike

There is really no bad software development process. There is only how you are doing it today and better. — Gary Gruver

It's harder than you might think to squander millions of dollars, but a flawed software development process is a tool well suited to the job. — Alan Cooper

Improve performance through process improvements introduced with minimal resistance. Deliver with high quality. Deliver a predictable lead time by controlling the quantity of work-in-progress. Give team members a better life through an improved work/life balance. Provide slack in the system by balancing demand against throughput. Provide a simple prioritization mechanism that delays commitment and keeps options open. Provide a transparent scheme for seeing improvement opportunities, thereby enabling change to a more collaborative culture that encourages continuous improvement. Strive for a process that enables predictable results, business agility, good governance, and the development of what the Software Engineering Institute calls a high-maturity organization. — David J. Anderson

Worse yet is the rejection of upfront requirements. The basic observation is correct: requirements will change, and are hard anyway to capture at the beginning. In no way, however, does it imply the dramatic conclusion that upfront requirements are useless! What it does imply is that requirements should be subject to change, like all other artifacts on the software process.

[...]

The agile advice here is irresponsible and serious software projects should ignore it.The sound practice is to start collecting requirements at the beginning, produce a provisional version prior to engaging in design, and treat the requirements as a living product that undergoes constant adaptation throughout the project. — Bertrand Meyer

Kanban is not a software development lifecycle methodology or an approach to project management. It requires that some process is already in place so that Kanban can be applied to incrementally change the underlying process. — David J. Anderson