So why not start today with the ground notion of a Method?
To make short, the object of a method is to help engineers to design a system under development by garanteeing :
- achievement of customer requirements
- deadlines and costs
- team work
- information sharing
- and so on...
A method must focus on three main aspects to be considered imo as a usable method :
- choice of formalisms, and artefacts
- elements of modelization
- elements of representation
- phases and steps
- activities of producing artefacts
- follow up
- modelisation tools
- control of the models
- development tools
- tests handling
- software configuration management
You'll object me that many companies, many people use methods to develop applications without using all this stuff... Sure, but what I describe here is an ideal toolbox designed to guarantee the quality of the application wrt the customer expectations. It is a kind of roadmap. Once you have this roadmap in mind you can choose in conscience what you want to choose, what you can choose to achieve your goals and the ones of your customers. You don't undergo events, you play with them... and it is in fine a big difference.