Question 1

Definition of Done

Accepted Answer

The Definition of Done (DoD) is a set of criteria for quality and completeness of the increment, against which the increment is evaluated.

Establishing the DoD before the work begins, creates transparency and shared understanding of what work was completed as part of the Increment

Question 2

Product Backlog Item (PBI)

Accepted Answer

Items in the Product Backlog are called Product Backlog Items (PBIs) in Scrum.

A PBI may represent any need such as: Business Functionality, Technical Enhancement, Change request, Defect, Support ticket, etc.

Scrum does not prescribe any specific way to write PBIs. Many teams find lightly written [User Stories](https://agileforgrowth.com/blog/how-to-write-good-user-stories/) (a practice from XP Engineering Practices) to be a useful practice.

Suggested Reading:

1. [How to Write Good User Stories by Kamlesh Ravlani](https://agileforgrowth.com/blog/acceptance-criteria-checklist/).

2. [Becoming User Centric with User Stories by Kamlesh Ravlani](https://agileforgrowth.com/blog/becoming-user-centric-with-user-stories/).

3. [Benefits of Effective User Stories by Kamlesh Ravlani](https://agileforgrowth.com/blog/userstory-benefits/)

Question 3

Empiricism

Accepted Answer

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed (Most recent, Factual, Information).

Scrum is founded on the three pillars of Empiricism: Transparency, Inspection and Adaptation.

Question 4

Scrum Master

Accepted Answer

The Scrum Master is responsible for promoting and supporting Scrum. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.

Scrum Master is not a new name for the traditional (Project) Manager. Rather, the Scrum Master is a true leader who leads through serving.

The Scrum Master serves the Developers, the Product Owner and the Organization through Educating, Facilitating and Coaching them to higher performance and agility.

Question 5

Product Owner

Accepted Answer

The Product Owner is accountable for maximizing the value of the product/service being built.

The Product Owner owns the decisions related to funds, works with the stakeholders and steers the direction of the product to optimize the outcomes and impact for the customers.

Question 6

Sprint Retrospective

Accepted Answer

The Sprint Retrospective is one of the prescribed Scrum Event - an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The Team may inspect their processes, communication and interactions among people, and tools used to identify opportunities to simplify processes, automate steps, reduce any waste, reduce hand-offs etc.

The result of the Sprint Retrospective is improved effectiveness of the Scrum Team and better qualify product/solutions.

The end of the retrospective marks the end of the Sprint.

Question 7

Product Backlog

Accepted Answer

The Product Backlog is one of the Scrum Elements.

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product.

The Product Backlog is an emergent artifact and creates transparency of the upcoming work.

It's owned by the Product Owner.

Question 8

Scrum Framework

Accepted Answer

Scrum is a light weight framework that helps people generate value through adaptive solutions for complex problems.

Scrum Framework is built on empiricism and lean thinking.

Scrum employs an iterative, incremental approach to optimize predictability and to control risk.

Question 9

Sprint Backlog

Accepted Answer

The Sprint Backlog is one of the Scrum artifacts that creates transparency of the work of the current Sprint.

It is set of Product Backlog Items selected by the Developers for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

Question 10

Increment

Accepted Answer

The increment is the sum of all the Product Backlog items completed during a Sprint and the increments from previous Sprint.

Increment creates transparency of the value created to date.

Example: If a Scrum team is writing a book, a chapter of the book could be an increment.

Question 11

Impediment

Accepted Answer

An Impediment is anything that prevents a team from moving forward, and from getting work Done. Also knowns as a Blocker.

Impediments add delay and overprocessing (form of waste) to a team's work.

Impediments could be intra team, inter team and organizational.

Impediments can be effectively addressed when team members facing an impediments quickly announce it and create transparency about it.

Question 12

Agile Manifesto

Accepted Answer

Established in 2011, the Manifesto for Agile Software Development (also referred as Agile Manifesto) is a set of four Values and 12 Principles that manifesto authors believe are essential to be adaptable for a team or an organization.

Refer: [Manifesto for Agile Software Development](https://agilemanifesto.org)

Question 13

Scrum Team

Accepted Answer

The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.

Scrum Teams are cross-functional, self-managing, small (10 members or less).

Question 14

Agility

Accepted Answer

Agility is an ability to gracefully adapt to changing needs.

In a dynamic and changing environment many variable such as: Customer's Needs, Technology, Market Conditions, Competition may change requiring a team / product / organization respond to these changes to stay relevant in the market.

Question 15

Product Roadmap

Accepted Answer

Product Roadmap	visually represents the strategy and vision of the Product Owner. It may contain the high level requirements in order of customer value, and the direction of the product over time.

Question 16

Coaching

Accepted Answer

Coaching is a form of development intervention in which a coach, supports a learner or a coachee in achieving a specific personal or professional goal.

The coach provides a structure, accountability and space within which the coachee's wisdom emerges and capability grows to:
*  clarify a problem they like to solve/address, 
*  identify possible solutions to try, and
*  take action to address the matter.

Providing answers, opinions, and telling others what to do is NOT coaching.

Unlike a mentor, a coach doesn't need to be an expert in the field in which a coachee aims to excel.

See also: [The Scrum Master as a Coach](https://agileforgrowth.com/blog/scrummaster-coach/)