RAD in Action: The "Quick Lunch" App Challenge

Objective: This 60-minute exercise simulates the Rapid Application Development (RAD) process. You will work in pairs to build and refine a simple application concept, experiencing first-hand the principles of prototyping, user feedback, and iteration.

Roles (Work in Pairs):

• The User (Client): You have a problem—you can never decide what to eat for lunch. Your job is to describe your initial idea, provide clear feedback on the prototypes, and change your mind as you see new possibilities. Remember: In RAD, changing your mind is part of the process!
• The Developer: Your job is to listen carefully to the User, quickly build a simple prototype that meets their requests, and be ready to change or discard your work based on their feedback. Your goal is speed and responsiveness, not perfection.

Tool: We will use Figma, a free, browser-based design tool that's perfect for creating interactive prototypes without writing any code. Go to www.figma.com and create a free account.

The Exercise: Step-by-Step

Phase 1: The Initial Requirements (10 minutes)

1. The User's Problem: The User explains their problem to the Developer: "I have 5-6 favorite lunch spots near campus, but I can never choose one. I want an app that just picks one for me."
2. JAD Session (Mini): The Developer asks clarifying questions to understand the absolute minimum viable product (MVP).
   • "So, you just want to see one restaurant name at a time?"
   • "What happens after you see the name? Does anything else need to be on the screen?"
   • "What's the most important thing for version 1?"
3. Agreement: Both partners agree on the single, core feature for the first prototype.
   • Example Agreement: "Okay, the first version will just have a single button that says 'Find Lunch!'. When you click it, it will show the name of a random restaurant."

Phase 2: Build Prototype v1.0 (20 minutes)

1. Developer's Task: The Developer opens Figma and builds an interactive prototype of ONLY the core feature agreed upon.
   • Create a starting screen with a title ("Quick Lunch") and a button ("Find Lunch!").
   • Create a second screen that shows a restaurant name (e.g., "The Burger Joint").
   • Use Figma's "Prototype" tab to link the button on the first screen to the second screen.
2. User's Task: While the developer is working, the User writes down 2-3 new ideas or features they might want after seeing the first prototype (e.g., "What if I don't like the suggestion?" or "I wish I could see a picture of the food.").

Phase 3: Feedback & Iteration Cycle #1 (15 minutes)

1. User Review: The Developer presents the working prototype to the User. The User clicks the button and sees the result.
2. Gather Feedback: The Developer asks: "What do you think? Does this solve the basic problem? What is the first thing you want to change or add?"
3. New Requirement: The User gives their feedback.
   • Example Feedback: "This is cool! But what if I don't want burgers? I need a 'Try Again' button to get another random suggestion."
4. Developer's Task: The Developer modifies the prototype on the spot to incorporate the new feedback. They add a "Try Again" button on the results screen that links back to the first screen (or to another result).