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, Monday.com, 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.

7. Finally, submit the ticket, which then gets assigned to the appropriate developer or 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 and
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.

8. Explain the Iterative Process and give some examples.

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. Bring out some differences between Agile vs Waterfall.

Agile and Waterfall are two contrasting methodologies used in software development, each with

distinct principles and workflows.

| Feature | Agile | Waterfall |

|------------------------|-------------------------------------------|-------------------------------------------|

| Development Style | Iterative and Incremental | Linear and Sequential |

| Flexibility | Highly adaptable to changing requirements| Rigid; difficult to accommodate

changes |

| User Involvement | Continuous interaction and feedback | Feedback mainly after final

delivery |

| Testing | Performed after every iteration | Conducted only after full development |

| Delivery Model | Frequent and partial releases | Single delivery at the end |

| Best Use Case | Dynamic projects like mobile/web apps | Stable projects like flight control
systems |

Agile is best for innovative and user-driven products, whereas Waterfall works well in predictable

and structured environments.

10. 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.

RCA is often applied after a failure or defect is discovered in a system or product. It uses 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
and increasing overall effectiveness.