a self-​managing team con­sis­ting of one Scrum Mas­ter, one Pro­duct Owner, and De­ve­lo­pers.

any mem­ber of a Scrum team who com­mits to crea­ting any aspect of a us­a­ble in­crement in each sprint.

is a role on a Scrum team that is re­spon­si­ble for the pro­ject's out­co­me. The Role seeks to ma­xi­mi­ze a pro­duct's value by ma­na­ging and op­ti­mi­zing the pro­duct back­log.

role within a Scrum team that is re­spon­si­ble for coa­ching, sup­por­ting and gui­ding a Scrum team and its en­vi­ron­ment to pro­per­ly un­der­stand and apply Scrum.

a short mee­ting, in­ten­ded to be less than 15 mi­nu­tes, where a team in­vol­ved in a pro­ject meets and dis­cus­ses what they've worked on since the last mee­ting.

is a simp­le frame­work that helps people, teams and or­ga­niza­ti­ons crea­te value th­rough ad­ap­ti­ve so­lu­ti­ons to com­plex pro­blems.

is a me­thod for pro­cess ori­en­ted pro­ject de­ve­lo­p­ment in ‘sprints’, pro­mo­ting a sup­por­ti­ve work en­vi­ron­ment for rapid com­ple­ti­on.

is a sin­gle ele­ment that is pre­sent in the Pro­duct Back­log. It can con­tain user sto­ries, epics, spe­ci­fi­ca­ti­ons, cri­te­ria or chan­ge re­quests.

A scrum board that con­sists of an or­de­red list of work to be done to crea­te and sus­tain a pro­duct. Ma­na­ged by the pro­duct owner.

Be­ne­fit of the pro­duct from the per­spec­ti­ve of the the user.

the team gathers to eva­lu­a­te com­ple­ted work and de­ter­mi­ne whe­ther ad­di­ti­o­nal chan­ges are nee­ded

Just ask a few ques­ti­ons – What went well? What didn't go well? What did we learn? It re­flects on the past to im­pro­ve the fu­ture.

is a short, time-​boxed pe­ri­od when a scrum team works to com­ple­te a set amount of work.