Click here to receive your FREE subscription to Campus Technology
News
Agile Process Showcased at IT Architect Event
10/25/2007
Last week, IT architects put their profession squarely on the map at the first annual IT Architect Regional Conference for Southern California. This local San Diego-based event, part of the International Association of Software Architects (IASA), wasn't just a typical forum for punditry on the sometimes obscure topic of service-oriented architecture (SOA). It was more a meeting of colleagues. The keynotes and sessions were frequently paused to answer spontaneous questions and remarks from attendees.
The first keynote speech, by Scott Ambler, IASA Fellow and IBM Rational practice leader for agile development, wasn't about SOA at all. It was about the agile software development process, which Ambler predicted would probably become the norm by 2010. Ambler spoke on "Agile Strategies for Enterprise Architects."
The agile process is usually defined as the use of small teams to create frequent software builds and releases. Agile teams typically create solutions without slowing down to document the process. In that sense, agile development is often contrasted with the traditional waterfall software development approach, which is heavily documented and prescribed. While that's a common way to characterize agile development, Ambler said no formal definition for the term really exists.
The majority of companies appear to be engaging in the agile software development process. Ambler cited a March 2007 Dr. Dobbs Journal survey of agile development where 69 percent of respondents said that their organizations were doing one or more agile projects.
Ambler called the concept of following repeatable processes in software development a "stupid idea." He said that teams work together differently and that the development process should stop catering to constructs formed by bureaucrats. People are not going to follow repeatable processes for the sheer joy of it, he said. What is really wanted is repeatable results.
In practice, you can't make decisions based on your documents (a traditional waterfall approach). There's nothing wrong with documentation, but agile developers are smart about it and don't try to write speculative documentation, Ambler said.
Writing the requirements first is not practical, for a number of reasons that Ambler described.
"We build software to meet the changing needs of our stakeholders," he said. "The stakeholders will change their minds. Trying to write a requirements specification -- trying to set up a design document early in the lifecycle -- is absolutely crazy. People are not good at defining up front what they want. We've known this for a couple decades now."
One reason to go with agile software development is that 45 percent of software functionality is not used on successful software development projects, per data from the Standish Group that Ambler didn't specify. Under traditional methods, developers may spend nearly half of their time creating functionality that their customers won't use and don't really want.
Recommended Reading
- Tufts Grants Rights for Mileage-Increasing Transportation Technology to Electric Truck
Tufts University has optioned rights to a technology that can recharge the batteries of any hybrid electric and electric-powered vehicle while it is driven. The Tufts-developed technology could increase by 20 percent to 70 percent the miles per gallon or total driving range performance of vehicles like the Honda Civic, Ford Escape, and Toyota Prius hybrids and the Tesla Motors and Phoenix Motorcars electric vehicles.
- U Florida and Cyntellect Collaborate to Unlock Mysteries of Cancer Stem Cells
The University of Florida has entered into a research agreement with life sciences company Cyntellect. The university's Interdisciplinary Center for Biotechnology Research will work with the company to focus on a variety of research areas including the purification and analysis of cancer stem cells (CSCs), rare cells believed to be directly involved in propagating cancers.
- George Mason U Receives Grant To Deploy Intergraph Apps for Intelligence Curriculum
George Mason University (GMU) in Fairfax, VA has been awarded a grant from Intergraph to enable students enrolled in GMU's Geospatial Intelligence Graduate Certificate program to use the company's geospatial production and exploitation software as part of their core curriculum.
- Institute for Cyber Security at U Texas, San Antonio Opens Incubator
The University of Texas at San Antonio (UTSA) Institute for Cyber Security (ICS) has launched a new Internet security incubator. The incubator was developed to commercialize promising technologies that address major cyber security and privacy issues. The first companies to enter the incubator are Denim Labs and SafeMashups.
- ISO/IEC Publishes Office Open XML Standard
ISO/IEC has published the Office Open XML (OOXML) file format standard, formally known as ISO/IEC 29500:2008. It describes file formats originally designed by Microsoft for its Office 2007 productivity suite, which are used in presentation, spreadsheet and word processing applications.
- Dynamics NAV 2009 ERP Coming Next Month
Microsoft exec Kirill Tatarinov Wednesday described some new features to expect in the forthcoming Microsoft Dynamics NAV 2009 enterprise resource planning solution. He gave the keynote address at Microsoft's Convergence 2008 event in Copenhagen, Denmark.
