Abstract
Many IS departments have adopted prototyping as a flexible alternative to traditional software development methods. Yet when not carefully planned and managed, prototyping can lead to chaos. Understanding when prototyping is useful and tactics for avoiding pitfalls of the prototyping process can help ensure a successful project.