There&#x27;s very little evidence whatsoever about <i>any</i> software development methodology or practice working well or poorly. That said, most experienced developers I&#x27;ve interacted with consider most of the Agile principles to be wise -- either common sense, or shown to be true via decades of experience.<p>Here are the principles:<p>* Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<p>* Welcome changing requirements, even late in development. Agile processes harness change for the customer&#x27;s competitive advantage.<p>* Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<p>* Business people and developers must work together daily throughout the project.<p>* Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<p>* The most efficient and effective method of conveying information to and within a development 
team is face-to-face conversation.<p>* Working software is the primary measure of progress.<p>* Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<p>* Continuous attention to technical excellence and good design enhances agility.<p>* Simplicity--the art of maximizing the amount of work not done--is essential.<p>* The best architectures, requirements, and designs emerge from self-organizing teams.<p>* At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<p>Which of these would you argue aren&#x27;t wise principles for all of us to use when developing software?  Now, if your beef is with Scrum (or some other branded methodology) in particular, I&#x27;d be more inclined to agree.