A Burn Down Chart is a graphical representation of work completed vs. remaining work over time. Explanation: Example Burn Down Chart:

A Sprint is a fixed-length development cycle (usually 1-4 weeks) in Scrum methodology. Explanation:

A Product Backlog is a prioritized list of features, enhancements, and fixes to be implemented in a product. Explanation: Example: A to-do list for a task management app might include:

A Scrum Master is responsible for ensuring that the Scrum framework is followed in Agile development. Explanation:

Code refactoring is the process of restructuring existing code without changing its behavior. Explanation: Example: Before Refactoring (Bad Code) pythondef calculate_price(price, tax): return price + (price * 0.15) # Hardcoded tax After Refactoring (Good Code) pythondef calculate_price(price, tax_rate=0.15): return price + (price * tax_rate)

Pair programming is a technique where two developers work together on the same code. Explanation:

A code smell is a symptom in code that indicates potential design flaws or bad practices. Explanation: Example (Bad Code – Code Smell) java int calc(int a, int b) { return a * b * 3.14; // Magic number (3.14 should be a constant)} Fix (Refactored Code): javafinal double PI = 3.14;int calc(int a, int…

Non-functional requirements (NFRs) define the quality attributes of a system, such as performance, security, and usability. Explanation: Example: For a banking app, an NFR could be:

Functional requirements define what a system should do, describing features, capabilities, and behavior. Explanation: Example:

A stakeholder is any individual, group, or organization that has an interest or influence in a software project. Explanation: Example: