When we launched our IT initiative in late 1995, we followed some basic guidelines that are standard now, but were pretty radical back then. They still serve us well today:
Take an agile path-based approach to software development
We build Web applications in small, incremental steps, rather than a few giant leaps. This lets us use short cycle times for early testing and improvement, adds value throughout the life of a project (not just at the end), and creates a climate of growth, change, experimentation, and learning.
Build modular, reusable platforms, tools, and templates
We take a "building-block" approach to development, in which we assemble applications from standard components. This lets us share code and concepts easily across applications, quickly adapt technology for new uses and audiences, integrate the best in available software, and make sure everything we use meets our open standards.
Keep it simple with Web-based applications
We seek to use only Web-based applications and Internet protocols. With technology changing daily, this approach gives us the flexibility to make changes and integrate new tools without affecting our infrastructure. It also makes our applications accessible from any Web-enabled location, on campus or around the world.
