1. What is emphasized in D.T.? Explain empathy mapping with an example.

Design Thinking (D.T.) emphasizes deeply understanding the user's needs, emotions,

and experiences to create innovative and user-centered solutions. At the heart of D.T.

lies the principle of Empathy, which involves seeing the world through the user's eyes

and stepping into their shoes to understand their challenges and motivations.

One popular tool in this phase is the Empathy Map, which is divided into four main

quadrants: Says, Thinks, Does, and Feels. It helps teams gather insights about user

behavior, thoughts, and emotions, allowing for better problem-solving and design

strategies.

Example:

A company developing a new food delivery app uses empathy mapping to understand

user experience:

- Says: "I want fast and reliable food delivery."

- Thinks: "Will my food be fresh and on time?"

- Does: Repeatedly checks the delivery status.

- Feels: Frustrated when food is late or inaccurate.

By analyzing this map, designers may introduce features like real-time GPS tracking

and accurate estimated delivery times to improve user satisfaction.

2. What is testing in D.T.? Explain one with an example.

Testing in Design Thinking is the phase where developed prototypes are tested with

real users to validate assumptions, gather feedback, and identify improvement areas. It

allows designers to understand how the user interacts with the product, whether the

solution solves the problem effectively, and what changes are required before the final

implementation.
Example:

A team develops a smart water bottle that reminds users to drink water through LED

lights. They create a prototype and give it to users for a trial day. Feedback includes:

- "The lights are too bright in dark rooms."

- "The reminders are useful during work hours."

Based on this, the team adjusts the brightness settings and adds customizable

reminder options, improving the user experience significantly before final production.

3. What is Mind Mapping? Explain with an example.

Mind Mapping is a creative and visual tool used to organize information around a

central topic. It helps break complex problems into smaller parts, encourages

brainstorming, and provides a clear overview of ideas. The structure starts with a

central concept and expands with branches to show relationships and subtopics.

Example:

Central Topic - Online Learning Platform

- Courses: Live classes, pre-recorded lectures, quizzes

- Features: Certifications, progress tracking, chat support

- Users: Students, teachers, admins

- Technology: Web interface, mobile app, cloud storage

Using this map, developers and stakeholders can plan the project comprehensively and

ensure nothing important is overlooked.

4. What is Brainstorming? Explain with an example.

Brainstorming is a group technique aimed at generating a large volume of ideas to

contribute, and wild or unconventional ideas are welcomed because they may spark

innovative solutions.

Example:

During a brainstorming session to enhance a university app, suggestions may include:

- Implementing AI chatbots for student queries

- Real-time timetable updates and notifications

- Integrating a student feedback system

- Providing digital ID cards

All ideas are listed without criticism, and after the session, the team evaluates and

refines the best ones for implementation.

5. What is the Agile method? Give one real-time example.

The Agile method is a flexible, iterative approach to software development and project

management. It focuses on breaking down the project into smaller, manageable units

called sprints, usually lasting 1-4 weeks. Each sprint delivers a working product or

feature that can be reviewed and tested by stakeholders. This method promotes

continuous feedback, collaboration, and the ability to adapt quickly to changing

requirements.

Agile values:

- Individuals and interactions over processes and tools

- Working software over comprehensive documentation

- Customer collaboration over contract negotiation

- Responding to change over following a plan

- Sprint 1: Implement login and user authentication

- Sprint 2: Add payment gateway integration

- Sprint 3: Redesign UI based on user feedback

After each sprint, the team conducts a review session with users or clients, collects

feedback, and adapts the next sprint's goals accordingly. This ensures that the product

evolves in alignment with user needs and market trends.

6. Mention some tools for project management. With the help of Teera, explain

the steps for creating a ticket for reporting your bug.

Project management tools are essential for organizing, assigning, monitoring, and

streamlining tasks within software development or product teams. These tools improve

collaboration, communication, and transparency, enabling teams to work efficiently.

Widely used project management tools include Jira, Trello, Asana, ClickUp, [Link],

and Notion. These platforms allow users to track issues, assign responsibilities, set

deadlines, and visualize progress through boards, timelines, and dashboards.

Teera, a tool similar to Jira, is used for task tracking and bug reporting. The process of

creating a bug ticket in Teera involves the following steps:

1. Login to your Teera account using valid credentials.

2. Navigate to the project dashboard and click on "Create Issue" or "New Ticket".

3. Choose "Bug" as the issue type to indicate a software defect.

4. Fill in the necessary details such as bug title, comprehensive description, related

project name, severity, and priority.

5. Document the steps to reproduce the bug so that developers can recreate the issue

reliably.

6. Attach relevant evidence like screenshots, video clips, or log files to help the team

understand the issue better.

team for resolution.

This systematic approach ensures issues are clearly reported, efficiently resolved, and

properly tracked throughout the development cycle.

7. What is the Waterfall Model? Explain by giving some real-time examples.

The Waterfall Model is a traditional software development methodology that follows a

linear sequential approach, where each phase must be completed before the next one

begins. The phases typically include Requirements Gathering, System Design,

Implementation (Coding), Testing, Deployment, and Maintenance. It is often compared

to a waterfall, where progress flows steadily downward through each phase without

returning to previous steps.

This model is best suited for projects with fixed, well-defined requirements where

changes are unlikely during development. It is valued for its structure, clarity, and

predictability.

Real-time Example - ATM Software Development:

- Requirements: Features like card reading, PIN verification, balance inquiry, and cash

dispensing are clearly defined.

- Design: UI layout and backend system architecture are planned in detail.

- Implementation: Developers write code according to the design.

- Testing: The complete system is tested to ensure it meets the requirements.

- Deployment: The software is installed on ATM hardware units.

- Maintenance: Post-deployment support and updates are provided as needed.

This model is often used in aerospace, defense, government, and embedded systems,

where changes mid-development are costly or impractical.

The Iterative Process is a software development approach where the product is built in

small, manageable parts (iterations). Each iteration goes through a cycle of planning,

design, implementation, and testing, and the results are evaluated before moving to the

next cycle. The goal is to refine the product gradually based on continuous feedback and

learning.

This model offers flexibility and early detection of issues, making it ideal for dynamic

projects where requirements may evolve.

Example - Chatbot Development:

- Iteration 1: A basic chatbot is launched with predefined FAQ support.

- User Feedback: Requests for voice interaction.

- Iteration 2: Voice input/output is integrated into the chatbot.

- Feedback: Users want multi-language support.

- Iteration 3: Multiple language options are added to enhance accessibility.

The cycle continues until the product meets performance and usability goals. This

approach is commonly used in Agile development, UI/UX design, and modern product

innovation, allowing for rapid adjustments and continuous improvement.

9. What is RCA? How does it help to overcome problems in product

development?

Root Cause Analysis (RCA) is a problem-solving technique used to identify the underlying

cause of a problem instead of just addressing its symptoms. By targeting the root cause,

teams can implement long-term solutions that prevent recurrence.

methods like "5 Whys," Fishbone diagrams, or Failure Mode and Effects Analysis (FMEA)

to drill down into the source of an issue.

Benefits of RCA in product development:

- Helps eliminate recurring issues.

- Improves product quality and user satisfaction.

- Saves time and costs by solving the real issue early.

- Enhances decision-making by exposing process or design flaws.

Example - Finance App Uninstalling Issue:

Symptom: Users frequently uninstall the app shortly after installation.

- Investigation: Metrics show low engagement and high drop-off at the onboarding

stage.

- Root Cause: The user interface is overly complex and unintuitive.

- Solution: Redesign the UI to be cleaner and provide step-by-step onboarding tutorials.

By fixing the core problem, RCA helps build more reliable and user-friendly products,

reducing risk