There are many different kinds of development methodologies that embrace those values and principles. For example, XP.
There are also lightweight management processes, such as Scrum (q.v., The Scrum Guide), that compliment using some sort of agile-based methodology, such as XP.
In my experience, I have never seen Scrum implemented in practice as described by-the-book. At best, maybe a 50/50 blend of Scrum and... umm... Not Scrum; at worst, using Scrum terminology for the parts of a Waterfall heavyweight management process. “In theory, theory and practice are the same. In practice, they are not.”
All that being said, the greatest factor is not the management process, nor the development methodology... it's the people and having a functional team and using The Joel Test as a quick tally sheet.
I'm not sure what the "Agile methodology" is.
The Manifesto for Agile Software Development is a set of four values and twelve principles. It does not prescribe any kind of process.
There are many different kinds of development methodologies that embrace those values and principles. For example, XP.
There are also lightweight management processes, such as Scrum (q.v., The Scrum Guide), that compliment using some sort of agile-based methodology, such as XP.
In my experience, I have never seen Scrum implemented in practice as described by-the-book. At best, maybe a 50/50 blend of Scrum and... umm... Not Scrum; at worst, using Scrum terminology for the parts of a Waterfall heavyweight management process. “In theory, theory and practice are the same. In practice, they are not.”
From my perspective, the practical part of agile software development that makes agile actually agile is Engineering Practices Necessary for Scrum.
All that being said, the greatest factor is not the management process, nor the development methodology... it's the people and having a functional team and using The Joel Test as a quick tally sheet.
I didn't knew Joel test and your conclusion seems good thanks for sharing