Content tagged with: software process
The important thing is not your process, the important thing is the process for improving your process.
SEMAT (Software Engineering Method and Theory) is an initiative to reshape software engineering such that software engineering qualifies as a rigorous discipline. SEMAT and Essence are big thinking for software developers.
The maddening thing about most of our organizations is that they are only as good as the people who staff them. Wouldn’t it be nice if we could get around that natural limit, and have good organizations even though they were staffed by mediocre or incompetent people? Nothing could be easier—all we need is (trumpet fanfare, please) a Methodology.
I have recently added the 3000th article on Softdevarticles.com. This directory provides pointers to articles that cover all areas of software development: programming, software quality, (project) management, databases, requirements, process improvement, ….
At the end of the past century, the approaches and methodologies (Information Engineering, RUP, CMMI) that were trying to improve software development processes and projects had a huge documentation on how to do things, initially on large documents sets and then on CDs. Checklists were often used as gateways between project phases and you had to confirm that every goal of the phase has been addressed. Then came the Agile Manifesto that proposed a new approach preferring “Individuals and interactions over processes and tools”.