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. Transparency : Scrum artifacts create transparency of needed information. Transparency enables Inspection. Inspection without transparency is misleading and wasteful. Inspection : Four formal Scrum events enable opportunities for inspection and adaptation. Inspection of the information enables to know if the actual resutls match or deviate from the desired results. Adaptation : Four formal Scrum events enable opportunities for inspection and adaptation. If during the inspection, the actual resutls is found to deviate from the desired results, we can adapt the input, so the desired results can be achieved.

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.

A framework could be a collection of guidelines, rules and elements that provide a structure and boundary but not the prescription to achieve something. For Example: The game of Chess (a framework) offers: The chess board (8x8 squares) The chess pieces (Material) The rules about how each piece is placed, how each piece moves across the board A chess player gets to decide their strategy, which piece they move and where, how they secure their king and how they use their queen. The game of the Chess doesn't prescribe any of this.

The Definition of Done (DoD) is a set of criteria for quality and completeness of the increment, against which the increment is evaluated. DoD creates transparency and shared understanding of what work was completed as part of the Increment. The Definition of Done is common across Product Backlog Items and consistent for a Product. The DoD is established before the work begins and is expanded (as needed) over the period. The Definition of Done is different from the Acceptance Criteria (AC). The AC is focused on functional scope of one PBI where as the DoD is focused on quality scope of the entire product. See also : Increment , Acceptance Criteria

A complex system is a collection of interdependent parts, modules, and/or variables. A perfect understanding of individual parts does not automatically convey a perfect understanding of the whole system's behaviour. The state of a complex system can't be predicted due to the reason that it's parts dynamically change and every change influences the state of other parts and the overall system. Is your work environment Obvious, Complicated, Complex or Chaotic? Please analyze your current work environment, and identify which of these variables change in your work environment? Customer Needs Technology Talent/People Competition Organizational Goals Marketplace Government Regulation All of the Above If you answered All of the above (or many of the above) your work environment is Complex.

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

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

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.

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.

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.

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. Also see: Incremental Development

A coaching intervention that is focused on helping teams, leaders and organizations to improve their ability to gracefully change / adapt to changing needs, may be identified as Agile Coaching.

Facilitation is an intervention through which a group improves the way it communicates, examines and addresses problems, and makes decisions. A neutral and unbiased facilitator would create the environment, design the structure and may use various facilitation techniques to help a group improve it's effectiveness.

Developers are cross-functionally skilled people in the Scrum Team who contribute to develop a usable Increment each Sprint. The Developers are accountable for: Planning the Sprint work; Execution and adapting their plan each day toward the Sprint Goal; Creating a quality Increment that adhers to their Definition of Done; Holding each other accountable as professionals.

Most popular results

Agile Software Development

Empiricism

Agility

Framework

Definition of Done

Complex System

Agile Manifesto

Scrum Team

Product Roadmap

Sprint Retrospective

Product Backlog

Increment

Agile Coaching

Facilitation

Cross-Functional Team

Developers