Agile methodology uses war room type collaboration and short iterations to produce incremental versions of software to meet the changing requirements of stakeholders.
- Working software is key measurement
- Requirements are done in iterations
- A War Room type collaboration
- Minimal documentation - Just enough documentation is created and maintained
Basic principles
- Customer satisfaction by rapid, continuous delivery of useful software
- Welcome changing requirements
- Working software is delivered frequently
- Working software is the principal measure of progress
- Close, daily collaboration between business and IT
- Face-to-face conversation is the best form of communication
- Projects are built around motivated individuals, who should be trusted
- Continuous attention to technical excellence and good design
- Self-organizing teams
- Regular adaptation to changing circumstances
To Make it Work
- Adopt short iterations no more than four weeks in length
- Focus on the delivery of working software, as a general rule, an iteration should be seen as a failure if all it produces is documentation
- Promote quality oriented techniques such as test first development, coding conventions and refactoring
- Remove as many barriers to communication and collaboration as you possibly can by making it as easy as possible for people to work together.
- Make sure that everyone involved, including business stakeholders, data professionals and quality assurance professionals work in an evolutionary if not Agile manner
- Streamline RUP as much as possible, less is definitely more
From: Overcoming the Myths of IBM Rational Unified Process (RUP) and Agile Development
Myths
- No documentation
- Undisciplined
- Not scalable to large, complex projects
- No traceability
- Issues and risk management is not done
Resources
Overcoming the Myths of IBM Rational Unified Process (RUP) and Agile Development -IBM
Manifesto for Agile Software Development – Agile Manifesto
The Experts’ Take on Business Analysis and Agile – Modern Analyst
RUP and Agile Development Overcoming Myths – IBM
Agile software development – Wikipedia, the free encyclopedia









At least once in your career you will have to deal with duplicate rows causing havoc on you application. This post will help you get through that dilema. I have Oracle and MySql examples below.