Blue Elephant Tony DiCola Mauktik Gandhi Jeff Mathew Tim McConnell Todd Sahl Eugene Talagrand

Process Choice and Baseline Agile Methodologies  Lightweight Unified Process T Approach Project Status Technology

Agile Methodologies Response to monumental methodologies. Adaptive vs. Predictive People vs. Process Oriented “Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan” 1 1. Manifesto for Agile Software Development

Examples Extreme Programming Cockburn’s Crystal Family Open Source Highsmith’s Adaptive Software Development Scrum Feature Driven Development Dynamic System Development Method Source:

Lightweight Unified Process Created by Craig Larman to mold a unified process into an agile methodology. Deemphasizes artifacts. Driven by use cases.  Management  Metrics

Lightweight Unified Process Source:

T Approach Create broad and thin user interface. Implement entirely a core requirement. Push out to implement more requirements. Source: User Interface Prototype Requirements

Project Status Meeting with client on campus. Creating use cases. Integrating technology. Developing prototype.

Technology Java Servlets and JSP Struts Hibernate, MySQL Eclipse, Ant, CVS, Bugzilla, Sharepoint

Questions?