The Agilist
Scrum Life
To be or not to be
Toyota
MansaMillions
100

Development (DEV) Team

Self organizing and cross functional team working together to develop the product.

100

Story Points

An arbitrary measure used by Scrum teams to determine the difficulty of implementing a given story.

100

Daily Scrum

A 15-minute daily meeting where the team has a chance to get on the same page and put together a strategy for the next 24 hours. Also called a Daily Standup. What have you completed since the last meeting? What do you plan to complete by the next meeting? Are there any blocks, obstacles or impediments that keep you form doing your work?

100

Servant Leadership

Servant leadership is a leadership philosophy in which the goal of the leader is to serve. This is different from traditional leadership where the leader's main focus is the thriving of their company or organization.

100

Jira 

An agile project management tool that supports any agile methodology, be it scrum, kanban, or your own unique flavor. From agile boards, backlogs, roadmaps, reports, to integrations and add-ons you can plan, track, and manage all your agile software development projects from a single tool.

200

Velocity

Predicts how much work can be completed in a sprint and how much time is required to complete a project. The number is obtained by adding all the story points from the last sprint’s stories.

200

Retrospective

Discuss current sprint activity, Plan for further improvements for future sprints. Identify what went well, what could have been done better and what action items to show improvement.

200

Artifacts

Product backlog, Sprint backlog, Product Increment

200

Xtreme Planning (XP)

An agile software development framework that aims to produce higher quality software, and higher quality of life for the development team. XP is the most specific of the agile frameworks regarding appropriate engineering practices for software development.

200

Product Owner (PO)

A member of the Agile Team responsible for defining Stories and prioritizing the Team Backlog to streamline the execution of program priorities while maintaining the conceptual and technical integrity of the Features or components for the team.

300

Burn UP Chart

Tracks the progress of the project. Illustrates the amount of work completed.

300

Impediments

The obstacles or issues faced by a scrum team which slows down their speed of work. If something is blocking the scrum team from getting their work done, it is considered an impediment.

300

Scrum of Scrums

The meeting after the daily scrum where a responsible person from each scrum team (in the case of multiple scrum teams) attends to discuss their work and to answer questions.

300

Kanban

Kanban is a scheduling system for lean manufacturing. Taiichi Ohno, an industrial engineer at Toyota, developed kanban to improve manufacturing efficiency. The system takes its name from the cards that track production within a factory. Kanban is also known as the Toyota nameplate system in the automotive industry.

300

Sprint Review

An informal meeting held at the end of a sprint, in which the Scrum team shows what was accomplished during this period.

400

Burn DOWN Chart

Tracks the progress of the project. Illustrates the amount of work remaining to complete the project. Tracks the sprint status.

400

Scrum

A lightweight framework that implements agile mindset, values and principles.

400

Product Owner (PO)

Responsible for the work the team should complete. Motivate the team to achieve the goal and the vision of the project. Makes the major decisions.

400

Continuous Improvement

Also known as kaizen: is a method for identifying opportunities for streamlining work and reducing waste that grew out of the agile model. Continuous improvement can be used flexibly, allowing companies to deviate from the practice if necessary, and is highly beneficial when put to work.

400

Backlog Refinement

Formerly known as backlog grooming; is when the product owner and some, or all, of the rest of the team review items on the backlog to ensure the backlog contains the appropriate items, that they are prioritized, and that the items at the top of the backlog are ready for delivery.

500

User Stories

A tool used in agile development which represents a small piece of business value that a team can deliver in a sprint.

500

Sprint

A repeatable and regular work cycle in scrum methodology during which work is accomplished and kept ready for review.

500

Waterfall

The waterfall model is a breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one and corresponds to a specialization of tasks. The approach is typical for certain areas of engineering design

500

Time Box

A defined period of time during which a task must be accomplished. Timeboxes are commonly used to manage software development risk. Development teams are repeatedly tasked with producing a releasable improvement to software, timeboxed to a specific number of weeks.

500

Sprint Planning

An event that establishes the product development goal and plan for the upcoming sprint, based on the team's review of its product backlog.