See the world through your user's eyes.

An Empathy Map helps Agile teams and stakeholders develop a shared understanding of the user's experience. It goes beyond demographics, focusing on what users think, feel, hear, see, say, and do—so we can create solutions that truly resonate.

Empathy Maps are often used in SAFe® during Continuous Exploration to support persona creation, problem framing, and feature prioritization.

🧩 Empathy Map Quadrants Explained

💬 SAY

What does the user say out loud in interviews, surveys, or daily use?
Example: "This app keeps crashing when I'm in the field."

🚶 DO

What actions or behaviors do they show?
Example: Avoids using the mobile app, writes data on paper.

👂 HEAR

What do they hear from colleagues, social media, influencers?
Example: "Everyone else is switching to a more reliable tool."

👁️ SEE

What do they see in their environment?
Example: Complex tools, confusing dashboards, peers doing manual workarounds.

🧠 THINK & FEEL

What are they really thinking and feeling (even if they don't say it)?
Example: "I'm afraid I'll get blamed if this tool causes mistakes."

⚠️ PAINS

What obstacles or annoyances do they face?
Example: Slow performance, bad UX, lack of support.

🎯 GAINS

What do they want to achieve? What would success look like?
Example: Faster workflows, trust in the tool, less manual effort.

✅ When to Use Empathy Maps

• Before writing features or user stories

• During design sprints or PI Planning

• When refining or validating personas

• To align stakeholders on user needs

📱 1. Chloe – Online Shopper (Retail E-Commerce)

👁️ SEE

• Endless options on competitor websites

• Flash sales, popups, influencer promotions

• Clean mobile-first designs and fast checkout in other apps

👂 HEAR

• "Shipping took forever."

• "Return process was a pain."

• Influencers recommending specific brands

💬 SAY

• "I want something stylish but affordable."

• "Why do I need to fill in my info again?"

• "This app is slow, I'm going back to Instagram."

🚶 DO

• Adds items to cart but doesn't check out

• Shops on mobile during commute or breaks

• Shares links with friends for opinions

🧠 THINK & FEEL

• Wants to feel smart about her purchase

• Gets frustrated easily if things don't work fast

• Feels unsure about size or fit

• Feels excited when she gets a good deal

⚠️ PAINS

• Confusing checkout process

• No clear sizing guide or reviews

• Long shipping time

🎯 GAINS

• Seamless, fast checkout

• Helpful reviews & return policy

• Personalized recommendations

🧑‍⚕️ 2. Dr. Elena – Hospital Department Head (Healthcare IT)

👁️ SEE

• Complex systems requiring multiple logins

• Staff frustrated with slow imaging systems

• Paper forms being scanned and emailed

👂 HEAR

• "IT takes days to fix issues."

• "This system is outdated."

• Complaints from nurses and junior doctors

💬 SAY

• "I need all the information in one place."

• "Can we get real-time access?"

• "Why are we still printing this?"

🚶 DO

• Delegates data entry

• Spends time in meetings and quick rounds

• Jots down notes by hand due to system lag

🧠 THINK & FEEL

• Feels responsible for patient safety and department efficiency

• Frustrated with system delays

• Wants to focus on clinical decisions, not tech issues

⚠️ PAINS

• Lack of integration between systems

• Delay in accessing test results

• Fear of medical error due to tech gaps

🎯 GAINS

• Real-time integrated EMR access

• Seamless PACS imaging

• Better coordination between departments

🧑‍🏫 3. Teresa – University Administrator (Education Technology)

👁️ SEE

• Disconnected systems for course registration, grades, and student records

• Overwhelmed students and staff

• Spreadsheets everywhere

👂 HEAR

• "I can't find my course."

• "Why do I have to register in two systems?"

• "My grades aren't showing up."

💬 SAY

• "We need to simplify this process."

• "I spend hours reconciling data."

• "Can someone explain why this is so complicated?"

🚶 DO

• Enters data manually across systems

• Sends frequent support emails

• Cross-checks grades with printed reports

🧠 THINK & FEEL

• Feels overwhelmed and burned out during enrollment season

• Concerned about compliance and data errors

• Wants more time for strategic initiatives

⚠️ PAINS

• Manual reconciliation

• Multiple logins and poor integration

• Compliance risk

🎯 GAINS

• Single unified platform

• Real-time student data

• Reduced admin load

Designing for Real People, Not Assumptions

In SAFe®, personas are fictional yet realistic representations of your target users. They help Agile teams develop empathy, focus on user needs, and make better product decisions.

Personas are a key tool within Design Thinking and Continuous Exploration, enabling teams to design solutions that are desirable to real users—not just theoretically sound or technically feasible.

🎯 Purpose of Personas in SAFe®

• Align development with real user needs

• Focus on value delivery by understanding user goals and pain points

• Improve communication across teams and stakeholders

• Prioritize features and stories based on what matters most to users

🧩 Key Elements of a SAFe Persona

A good SAFe persona typically includes:

• Name & photo (humanizes the persona)

• Job title or role

• Demographics (age, location, experience level, etc.)

• Goals and motivations

• Frustrations or pain points

• Behaviors and attitudes

• Preferred tools or channels

📌 Examples of Personas in SAFe

1. Emily – Enterprise Buyer (B2B Software Company)

• Role: CIO of a mid-sized logistics firm

• Age: 47

• Goals: Wants secure, scalable software to streamline supply chain operations

• Frustrations: Long implementation times, hidden costs, lack of vendor support

• Tech-savvy: High – makes decisions with her IT director

• Preferred Info: Case studies, ROI metrics, integration capabilities

2. Raj – End User (Healthcare SaaS)

• Role: Frontline nurse in a busy urban hospital

• Age: 34

• Goals: Save time during patient intake, reduce admin errors

• Frustrations: Clunky software interfaces, slow systems, multiple logins

• Tech-savvy: Low – prefers mobile and intuitive apps

• Preferred Tool: Tablet-based interface during shifts

3. Lisa – Internal Admin (HR System)

• Role: HR Operations Manager

• Age: 42

• Goals: Automate onboarding, reduce manual data entry, generate reports

• Frustrations: Disconnected tools, poor user support

• Tech-savvy: Medium – open to new platforms but needs training

• Preferred Interaction: Desktop dashboard, easy-to-export data

🔁 Using Personas in SAFe

Personas are used throughout the SAFe lifecycle:

• During PI Planning: To ensure features align with user goals

• In User Story Writing: To frame stories with user-centric language ("As Raj, I want to...")

• In UX Design & Testing: To validate designs with specific user types in mind

• In Prioritization: To assess value from the perspective of each persona

🧠 Pro Tip:

Use multiple personas to cover different segments—such as buyers, end users, admins, and support roles. This ensures that you're not optimizing for one group at the expense of others.

Step 1: Start with the Persona's Goals and Pain Points

Identify what the persona wants to achieve and what frustrates them.

Step 2: Translate Needs into Capabilities

Think in terms of what the system or solution should do to solve that need at a Feature level (not just tasks or UI tweaks).

Step 3: Define Acceptance Criteria

Ensure the feature is testable and has a clear outcome tied to value.

Step 4: Link to Business Value

Explain how this feature will improve user satisfaction, reduce waste, drive adoption, or generate revenue.

✍️ Feature Format (SAFe standard):

[Capability or goal] for [persona or user type] so that [business value]

🔍 Examples: Turning Personas into Features

Persona: Chloe – Online Shopper (Retail E-Commerce)

• Goal: Quickly find products she likes

• Pain: Wasting time scrolling through irrelevant items

👉 Feature:

Personalized product recommendations for online shoppers like Chloe so that they can discover relevant items faster and increase conversion rates

✅ Acceptance Criteria:

• AI-based engine shows personalized suggestions

• Learns from click history and past purchases

• Results update dynamically based on behavior

Persona: Mark – Field Technician (Utility Industry)

• Goal: Complete tasks efficiently in remote areas

• Pain: Poor signal causes app failure

👉 Feature:

Offline work mode for field technicians like Mark so that they can access and update job info without relying on network availability

✅ Acceptance Criteria:

• Technicians can download job lists in advance

• Changes sync automatically when back online

• Critical data available even with no connection

Persona: Dr. Elena – Hospital Department Head

• Goal: View imaging data in real time

• Pain: Waiting for IT to retrieve scans

👉 Feature:

Instant imaging access integration for department heads like Dr. Elena so that they can diagnose patients faster and improve care outcomes

✅ Acceptance Criteria:

• Connects PACS system with EMR

• User authentication for secure viewing

• Results load within 3 seconds on hospital network

Persona: Ahmed – Finance Analyst

• Goal: Run customized financial reports

• Pain: Rigid templates and delayed access

👉 Feature:

Custom financial reporting builder for finance analysts like Ahmed so that they can analyze data quickly without IT dependency

✅ Acceptance Criteria:

• Drag-and-drop report builder

• Filters by department, date range, and account type

• Export to Excel, PDF, or dashboards

🔗 Pro Tips:

• Attach personas to features in your backlog tool (e.g., Jira, Azure DevOps)

• Use persona icons or labels on Features during PI Planning for clarity

• Prioritize based on value to the persona and their role in the value stream

• Validate with real users or customer proxies before building

🗺️ What Is a Journey Map?

A Journey Map visually represents the end-to-end experience a user goes through while interacting with a product, service, or system. It helps teams identify pain points, emotions, opportunities, and gaps in the user journey.

Journey maps are super useful for:

• Identifying friction points in the user experience

• Prioritizing features and capabilities

• Building empathy by viewing the journey from the user's lens

• Aligning stakeholders on customer value streams

🧠 What Goes Into a Journey Map?

1. The Persona – Start with a specific type of user (e.g., a student, a nurse, a field technician).

2. The Scenario – What are they trying to do? (e.g., book an appointment, make a purchase, submit a report).

3. The Stages or Steps – What steps do they go through to reach their goal?

4. Their Actions – What are they doing at each step?

5. Their Thoughts & Feelings – What are they thinking, worrying about, or excited about?

6. Their Pain Points – What goes wrong or frustrates them?

7. Opportunities – How can we improve their experience?

🧵 An Example: Booking a Doctor's Appointment

Imagine you're mapping the journey of someone trying to book a doctor's appointment online.

• Step 1: Awareness – They realize they need to see a doctor.
  Feeling: Concerned.
  Pain: Unsure where to go.
  Opportunity: Offer a symptom checker or clear clinic options.

• Step 2: Search for a Doctor – They Google or open your app.
  Feeling: Hopeful but cautious.
  Pain: Too many confusing options.
  Opportunity: Use filters and show top-rated doctors.

• Step 3: Book Appointment – They choose a time and fill out forms.
  Feeling: Slightly annoyed.
  Pain: Long form, asks for info they've already submitted before.
  Opportunity: Autofill with past data or insurance info.

• Step 4: Visit Doctor – They go to the appointment.
  Feeling: Nervous.
  Pain: Long wait time.
  Opportunity: Live queue updates in app.

• Step 5: Follow-Up – They get results or schedule another visit.
  Feeling: Relieved or frustrated, depending on how easy it is.
  Pain: No clear next steps.
  Opportunity: Push notification or email summary.

🧳 1. Business Traveler Booking a Flight (Travel & Hospitality)

Persona: Raj – Busy sales executive
Scenario: Needs to quickly book a flight for a client meeting

Journey:

• Step 1: Needs to Travel
  Raj gets meeting confirmation and needs to book a flight ASAP
  Feeling: Rushed
  Pain: Doesn't know which airline has best schedule
  Opportunity: Smart flight suggestions based on past trips

• Step 2: Searches Flights
  Uses travel app on mobile while in transit
  Feeling: Frustrated with slow loading and too many filters
  Pain: Hard to compare prices and times
  Opportunity: Clean UI, saved preferences, instant compare

• Step 3: Books Ticket
  Chooses flight, enters traveler info
  Feeling: Impatient
  Pain: Too many steps, re-entering frequent flyer info
  Opportunity: Autofill + faster checkout for repeat users

• Step 4: Prepares for Travel
  Gets email with e-ticket, checks bag policy
  Feeling: Slightly anxious
  Pain: Email doesn't include terminal or gate info
  Opportunity: In-app real-time travel assistant

• Step 5: Flies to Destination
  Checks in online and travels
  Feeling: Relieved
  Opportunity: Prompt for feedback, loyalty point reminder

🏥 2. Patient Scheduling a Telehealth Appointment (Healthcare)

Persona: Priya – Young professional with a busy schedule
Scenario: Wants to consult a doctor about a minor health issue from home

Journey:

• Step 1: Recognizes Symptoms
  Priya notices a skin rash and decides to get it checked
  Feeling: Mild concern
  Pain: Not sure if it's worth going to a clinic
  Opportunity: Provide telehealth option right from homepage

• Step 2: Books Appointment
  Visits provider website, looks for online consultation
  Feeling: Hopeful
  Pain: Not clear if this service covers her issue
  Opportunity: Show common concerns treated online

• Step 3: Attends Video Call
  Joins from laptop, speaks with doctor
  Feeling: Comfortable
  Pain: Had trouble connecting camera at first
  Opportunity: Pre-visit device check tool

• Step 4: Gets Prescription
  Doctor emails prescription, suggests follow-up
  Feeling: Satisfied
  Pain: Doesn't know how to get it filled quickly
  Opportunity: Partner with pharmacy for instant delivery

• Step 5: Follow-Up Reminder
  Gets reminder two weeks later
  Feeling: Appreciates proactive care
  Opportunity: Personalized health tips via app

📚 3. Student Applying for a University Program (Education)

Persona: Ahmed – High school graduate
Scenario: Wants to apply to an international master's program

Journey:

• Step 1: Research Programs
  Browses university websites and forums
  Feeling: Overwhelmed
  Pain: Hard to compare tuition, deadlines, scholarships
  Opportunity: Program comparison tool or chatbot

• Step 2: Starts Application
  Registers on the university portal
  Feeling: Motivated
  Pain: Process is long and confusing
  Opportunity: Visual progress tracker, save/resume option

• Step 3: Uploads Documents
  Submits transcript, test scores, essays
  Feeling: Stressed about missing something
  Pain: No checklist or confirmation email
  Opportunity: Smart upload checklist with real-time status

• Step 4: Awaits Result
  Gets email saying decision in 4–6 weeks
  Feeling: Anxious
  Pain: No way to track status
  Opportunity: Real-time application status portal

• Step 5: Accepts Admission
  Logs in and pays deposit
  Feeling: Excited
  Opportunity: Welcome email, next steps clearly laid out

🧱 What is a Story Map?

A Story Map is a way to visualize the journey of a user interacting with your product, and it helps you break that journey down into activities, tasks, and user stories.

You start by identifying the major goals (activities) a user wants to accomplish. Then you drill into the tasks they perform to achieve each goal. Under each task, you break it down even further into user stories—specific pieces of functionality that your team can build.

🛒 Example: Online Shopping App for a Persona Named Chloe

1. High-Level Goal (Activity): Browse and Discover Products

Chloe logs into the shopping app looking for something new. Her intent isn't to buy right away—she just wants to see what's out there.

• She wants to scroll through featured items on the homepage.

• She wants to search for specific products using a search bar.

• She wants to filter and sort results (by price, color, size, brand).

• She also likes saving products she might want later.

From this activity, you extract user stories like:

• As Chloe, I want to search by keyword so I can find items faster.

• As Chloe, I want to filter by size so I don't waste time on unavailable products.

• As Chloe, I want to favorite items to review them later.

2. High-Level Goal: Add to Cart and Make a Decision

Once Chloe finds something she likes, she begins comparing and evaluating.

• She wants to view product details (images, reviews, specifications).

• She wants to check sizing guides or see "fit advice".

• She may add items to her cart while still exploring.

• She might also remove or edit cart items before checkout.

Stories that fall here:

• As Chloe, I want to read customer reviews so I can make a confident decision.

• As Chloe, I want to easily remove items from my cart so I stay within budget.

• As Chloe, I want to view my cart summary at any time.

3. High-Level Goal: Checkout and Payment

Once Chloe decides to buy, she moves into the transactional part.

• She wants to enter delivery information quickly (maybe saved from last time).

• She wants to choose between multiple payment methods.

• She wants confirmation of her order and estimated delivery.

Example user stories:

• As Chloe, I want to save my shipping address so I don't have to re-enter it.

• As Chloe, I want to pay with my preferred method (credit, PayPal, UPI).

• As Chloe, I want a confirmation email so I feel secure about my order.

4. High-Level Goal: Post-Purchase Engagement

Even after buying, Chloe still interacts with the app.

• She wants to track her order status.

• She might want to return or exchange an item.

• She's also open to personalized recommendations.

Stories:

• As Chloe, I want to track my delivery in real-time.

• As Chloe, I want a simple return process if something doesn't fit.

• As Chloe, I want to receive recommendations based on my order history.

🧠 Final Thought

Story Maps are not just a backlog tool—they're a collaborative visual tool that helps you:

• Focus on real user needs

• Identify MVP (minimum viable product)

• Prioritize what to build first

• Tell a cohesive product story across teams

You can build these out in tools like Miro, MURAL, or sticky notes on a wall—and even map them onto your SAFe® epics and features.

1. What is the primary goal of Design Thinking in SAFe?
A) Optimize the architectural runway
B) Increase code quality
C) Drive customer-centric solutions
D) Automate DevOps pipelines
✅ Answer: C
Explanation: Design Thinking in SAFe is all about understanding customer needs deeply and designing innovative solutions that deliver real value.

2. Which mindset underpins Design Thinking in SAFe?
A) Fixed Mindset
B) Lean-Agile Mindset
C) Waterfall Mindset
D) Business-Centric Mindset
✅ Answer: B
Explanation: SAFe promotes a Lean-Agile mindset, which emphasizes flexibility, innovation, and customer centricity—all of which are core to Design Thinking.

3. What is the key principle of customer centricity in SAFe?
A) Deliver software frequently
B) Prioritize internal efficiency
C) Focus all efforts on customer needs and experiences
D) Minimize product cost
✅ Answer: C
Explanation: Customer centricity means placing the customer at the center of every decision to ensure maximum value delivery.

4. In SAFe Design Thinking, what is a "persona"?
A) A stakeholder representative
B) A fictional archetype of a user
C) A Scrum Master role
D) A technical architect
✅ Answer: B
Explanation: Personas are fictional, yet research-based representations of target users to guide design decisions.

5. What is the purpose of an empathy map?
A) To create architecture designs
B) To track Agile metrics
C) To capture what users say, think, do, and feel
D) To define release schedules
✅ Answer: C
Explanation: Empathy maps help teams understand the user's emotions and behavior to design better experiences.

6. Which of the following tools is used to visualize a user's end-to-end experience?
A) Sprint Backlog
B) Kanban Board
C) Journey Map
D) Roadmap
✅ Answer: C
Explanation: A journey map outlines the steps a user takes to accomplish a goal, helping identify pain points and opportunities.

7. What is a solution hypothesis?
A) A guaranteed business model
B) A final feature list
C) An assumption about how a solution will deliver value
D) A risk matrix
✅ Answer: C
Explanation: Solution hypotheses test whether a proposed feature or product will meet customer needs and provide value.

8. Which of the following is NOT a step in the Design Thinking process?
A) Empathize
B) Define
C) Ideate
D) Monitor
✅ Answer: D
Explanation: "Monitor" is not a Design Thinking step. The core stages are Empathize, Define, Ideate, Prototype, and Test.

9. After defining a problem in Design Thinking, the next step is to:
A) Prototype
B) Empathize
C) Ideate
D) Build
✅ Answer: C
Explanation: After understanding the problem, teams brainstorm ideas (ideation) to find creative solutions.

10. What does "Test" mean in Design Thinking?
A) Run automated unit tests
B) Validate the prototype with users
C) Execute regression test scripts
D) Test API integrations
✅ Answer: B
Explanation: In Design Thinking, "testing" means evaluating the prototype with real users to gather feedback and improve.

11. What's the purpose of prototyping in SAFe Design Thinking?
A) To reduce team size
B) To validate ideas quickly and cheaply
C) To build complete systems
D) To finalize UI designs
✅ Answer: B
Explanation: Prototypes are quick, inexpensive versions of a product used to test and learn before building the real thing.

12. What makes an MVP valuable in Design Thinking?
A) It includes all planned features
B) It reduces deployment frequency
C) It tests hypotheses with minimum effort
D) It guarantees high profits
✅ Answer: C
Explanation: MVPs are used to validate assumptions with the least amount of effort and investment.

13. Which SAFe Continuous Delivery Pipeline domain does Design Thinking primarily support?
A) Continuous Integration
B) Continuous Exploration
C) Continuous Deployment
D) Release on Demand
✅ Answer: B
Explanation: Design Thinking lives in the Continuous Exploration domain, where teams explore what to build and why.

14. Which of these is a benefit of using Design Thinking in PI Planning?
A) Increases team velocity
B) Reduces cycle time
C) Aligns features with validated user needs
D) Reduces scope
✅ Answer: C
Explanation: Design Thinking ensures features planned during PI Planning are based on user empathy and real-world validation.

15. What's the difference between a persona and a stakeholder?
A) Personas represent users; stakeholders represent any individual or group that can impact the outcome of a project
B) Stakeholders use empathy maps; personas don't
C) Stakeholders are fictional; personas are real
D) No difference in SAFe
✅ Answer: A
Explanation: Personas are user-focused; stakeholders are people with influence or interest in the solution's outcome.

16. Which tool is best used to capture a user's emotional journey?
A) Product Backlog
B) Technical Map
C) Empathy Map
D) Architectural Model
✅ Answer: C
Explanation: Empathy maps provide insights into user emotions and behavior, critical for understanding their journey.

17. Why is customer feedback important in Design Thinking?
A) It increases technical complexity
B) It ensures the solution meets business goals
C) It helps refine solutions and avoid waste
D) It slows down releases
✅ Answer: C
Explanation: Continuous user feedback reduces risk and ensures the team is building the right thing.

18. What is a common outcome after testing a prototype?
A) Product launch
B) Sprint demo
C) User feedback for iteration
D) Release to production
✅ Answer: C
Explanation: Testing a prototype results in feedback, which is then used to refine the design or pivot the approach.

19. Which of the following best represents an MVP mindset?
A) Let's launch everything at once
B) Let's build it perfectly the first time
C) Let's learn fast and pivot if needed
D) Let's finalize UI before user testing
✅ Answer: C
Explanation: MVPs are about experimentation, learning quickly, and adjusting based on user validation.

20. What is the final goal of using Design Thinking in SAFe?
A) Deliver fast
B) Automate processes
C) Reduce costs
D) Deliver solutions that customers love
✅ Answer: D
Explanation: Design Thinking ensures that teams build solutions that not only solve problems, but also delight the customer.

1. 🖼️ Low-Fidelity Prototypes

• Purpose: Quick, inexpensive, and easy to change.

• Examples: Sketches, wireframes, paper mockups.

• Used For: Early exploration of ideas, concept validation, initial user feedback.

2. 💻 High-Fidelity Prototypes

• Purpose: More detailed, closer to the final product.

• Examples: Interactive UI mockups, near-functional apps, clickable Figma designs.

• Used For: Usability testing, stakeholder reviews, simulating real interactions.

3. 🔁 Throwaway (Disposable) Prototypes

• Purpose: Built quickly to test specific ideas and then discarded.

• Examples: Temporary mock services or screens.

• Used For: Validating assumptions, fast learning, low cost of change.

4. ⚙️ Evolutionary Prototypes

• Purpose: Built with the intention of evolving into the final product.

• Examples: MVPs, early-stage working code or systems.

• Used For: Progressive elaboration, continuous learning, integration into the solution.

5. 🧪 Exploratory (Technical) Prototypes

• Purpose: Validate feasibility of a technical approach or integration.

• Examples: API stubs, PoCs (Proof of Concept), spikes.

• Used For: Technical risk reduction, architecture validation.

1. What is the primary purpose of using prototypes in SAFe's Design Thinking approach?

A. To finalize the design before implementation
B. To delay development until requirements are confirmed
C. To validate ideas and gather feedback early
D. To reduce the number of Agile teams required

✅ Answer: C. To validate ideas and gather feedback early
Explanation: Prototypes are used to quickly test assumptions, gather customer feedback, and validate ideas before full-scale development, reducing risk and waste.

2. Which type of prototype is typically used for quick validation and is discarded after use?

A. Evolutionary Prototype
B. Throwaway (Disposable) Prototype
C. High-Fidelity Prototype
D. Technical Prototype

✅ Answer: B. Throwaway (Disposable) Prototype
Explanation: These are quick, low-cost prototypes built to test a specific concept. They are discarded after use and not intended to evolve into the final product.

3. In SAFe, where does prototyping typically occur in the Continuous Delivery Pipeline?

A. Continuous Integration
B. Continuous Exploration
C. Continuous Deployment
D. Release on Demand

✅ Answer: B. Continuous Exploration
Explanation: Prototypes are mainly created during Continuous Exploration as part of Design Thinking, to define "what" to build and validate customer needs.

4. What distinguishes a high-fidelity prototype from a low-fidelity one?

A. Cost of development
B. Number of features
C. Level of detail and interactivity
D. Use of agile teams

✅ Answer: C. Level of detail and interactivity
Explanation: High-fidelity prototypes closely mimic the final product in terms of design and user interaction, while low-fidelity ones are simpler and used earlier in the design process.

5. Which prototype type is likely to be incorporated into the final solution?

A. Throwaway
B. Technical
C. Low-Fidelity
D. Evolutionary

✅ Answer: D. Evolutionary
Explanation: Evolutionary prototypes are developed incrementally and refined continuously, often becoming part of the final deliverable.

6. A technical prototype is mainly used to:

A. Test UI layouts
B. Validate customer interest
C. Explore feasibility of a technical solution
D. Finalize system documentation

✅ Answer: C. Explore feasibility of a technical solution
Explanation: Technical prototypes (or spikes) help teams understand technical challenges or test architectural approaches before committing to full implementation.