1. Key difference between a project manager and a scrum master

❌ PM is a coach, SM is a task manager
❌ PM creates Kanban board, SM focuses on sprint
✅ PM assigns work, SM coaches team to be self-managed
❌ PM removes impediments, SM documents risks

Explanation:
Scrum teams are self-managed; the scrum master coaches, while project managers traditionally assign work.

---

2. What should be included in a user story?

❌ Technical details, timeline, risks
❌ Agile methodology, testing criteria, responsibilities
❌ User feedback, bug reports
✅ Business value, assumptions, and definition of done

Explanation:
A user story includes value, assumptions, and acceptance criteria (DoD).

---

3. True statement about Epics in Agile

✅ Epics describe stories too large to complete within a sprint
❌ Small stories completed within a sprint
❌ Stories unrelated to project goals
❌ Unimportant stories

Explanation:
Epics = large work items broken down into multiple user stories.

---

4. Best description of story points

✅ A metric to estimate the difficulty of delivering a user story
❌ Track progress
❌ Prioritize stories
❌ Estimate time

Explanation:
Story points measure effort + complexity + uncertainty, not time.

---

5. Anti-pattern related to evaluating user stories

❌ Evaluate by effort & complexity
❌ Break down big ideas
❌ Use abstract difficulty measures
✅ Evaluating user stories based on wall-clock time

Explanation:
Estimating in hours is an anti-pattern; Agile uses relative estimation.

---

6. What is true about the product backlog?

❌ Only fully detailed stories
❌ Only sprint plan stories
❌ Only completed stories
✅ Includes stories in sprint plan, icebox, and backlog

Explanation:
Product backlog includes everything planned, upcoming, or on hold.

---

7. What defines team velocity?

❌ Number of tasks
✅ Maximum story points a team can finish in one sprint
❌ Hours worked
❌ Speed of completing sprint

Explanation:
Velocity = story points completed per sprint.

---

8. Purpose of the Sprint Review

❌ Define sprint goal
✅ Get feedback and convert it into new backlog stories
❌ Create sprint plan
❌ Assign story points

Explanation:
Sprint Review = inspect increment + adapt backlog.

---

9. Purpose of the Sprint Retrospective

❌ Plan and assign stories
❌ Document stakeholder feedback
❌ Measure team health
✅ Assess process health and reflect on the sprint

Explanation:
Retrospective = improve process, team collaboration, tools.

---

10. Who should attend the Sprint Retrospective?

❌ Scrum Master + development team
❌ Scrum Master + stakeholders
✅ Scrum Master + Product Owner + Development Team
❌ Only Scrum Master

Explanation:
The entire Scrum team attends the retrospective.

---

🧾 SUMMARY TABLE

---