Loading...

    Glossary: Scrum

    Acceptance criteria are conditions a user story must meet to be accepted as complete. They define expectations for a feature and provide a shared benchmark for implementation and verification.
    A daily 15-minute meeting where the developers discuss progress since the last Daily Scrum and plan what to do next.
    An arrangement made by the product owner and developers to define when a unit of work can be considered "done" and therefore potentially delivered to the customer.
    An agreement reached between the product owner and developers to define which requirements or elements of the product backlog are ready to be included in the next sprint.
    Developers are self-organised professionals who develop and deliver the product. They are responsible for implementing increments within a sprint and make common decisions to get the work done.
    An ordered list of user stories containing all the functionalities, requirements, improvements and bug fixes needed for the product being developed.
    The product owner is responsible for maximising the value of the product and managing the product backlog. He or she communicates the requirements and priorities to the developers and decides on the release of results.
    A clear and inspiring description of the long-term goals and purposes of the product. It serves as a guide for the whole team and helps to focus on the key business achievements.
    A continuous process where developers review, refine and update the product backlog at regular intervals to ensure it is always relevant and prioritised to enable better planning and implementation of sprints.
    The Product Backlog, Sprint Backlog and Increment are Scrum artefacts. They make requirements, planned work and completed results transparent and provide a shared view of product progress.
    The Scrum Master is responsible for the implementation of Scrum and supports the team to achieve maximum effectiveness. He / she removes any barriers and ensures that the team collaborates efficiently.
    A time frame of one to four weeks in which the development team creates a completed product increment.
    A selection of user stories from the product backlog to be implemented by the development team during the sprint.
    A meeting at the beginning of the sprint in which the developers set the goals and the backlog for the sprint.
    A meeting at the end of the sprint in which the developers reflect on what went well in the sprint, what can be improved and how the team can improve its processes and collaboration.
    A meeting at the end of the sprint in which the development team discusses the finished increment with the product owner and other stakeholders.
    Stakeholders are people or groups who have a share in or are affected by the success of the product. They are responsible for providing feedback and prioritising requirements and have an influence on the product.
    A user requirement or use case from the user's perspective that serves as the basis for planning and implementing software features.

    Contact request

    You can contact us at any time

    Stop! Playing in the meantime?
    Stop! Playing in the meantime?
    Stop! Playing in the meantime?

    Stop! Playing in the meantime?

    Break the highscore

    Press Start
    Contact request
    Screenreader label
    Security question 
    S46_________RMA______
__8____3______A___KBO
__3___KG9_____L______
__1____5______4___4GA
__7___________L______