Any person involved in software development has always known that it
usually is a typical scenario where instead of Newton's Law's of Physics
being applied there, its Murphy's laws that dominate. Now, why does this
happen? Many undefined factors play a major role in most software projects.
Even after defining requirements to the dot and designing a project that
should deliver without a fuss, projects do tend to fail. Heavy weight
processes like Rational Unified Process (RUP) have tried to bring in some
amount of order and symmetry to processes, but even then there are many
reasons for the failure of software development processes.
Enter SCRUM. Not another acronym, but a term that's synonymous with successful
and agile processes today. Well, it originated in the sport of rugby a
name given to the formal conglomeration of forwards who bind together
in specific positions when a scrum down happens. Ikujiro Nonaka and Hirotaka
Takeuchi first used it to describe hyper-productive development in 1987.
Scrum is a lightweight process that manages and controls development
work. And controls chaos situations and improves communications and maximizes
productivity. A tall order? Read on to see
how it works
the Open Source Eclipses
The open source world has come a long way in evolving from command
line based geeks operating systems to a powerful competitor for the
commercial giants of the industry.
ADO.NET is designed to build on the strength of the ADO programming
model, while providing an evolution of data access technology to meet
the changing needs of the developer.