What are the 3 artifacts of Scrum?
Successful Scrum teams keep their artifacts visible, current, and aligned with goals. Using a collaborative work management tool like Wrike makes this easier — teams can update the product backlog, track sprint progress with boards and dashboards, and document increments in one shared workspace for full transparency.
The most effective Scrum teams track sprint progress daily using visual tools such as Kanban boards or burndown charts. In Wrike, teams can create custom dashboards to monitor velocity and task completion in real time, helping them identify bottlenecks early and keep sprints on target.
Alignment comes from visibility and communication. Wrike provides real-time task updates, comments, and shared dashboards so everyone, from developers to product owners, can see priorities, dependencies, and blockers as they happen, reducing confusion and last-minute surprises.
Teams can standardize their definition of done by using consistent task templates, checklists, and approval workflows. Wrike supports this by letting teams embed quality criteria directly into tasks and automate handoffs, ensuring every increment meets agreed-upon standards before it’s marked complete.
Scrum is built around three roles, five events, and three artifacts that create structure and transparency in Agile projects. The three roles are the product owner who manages priorities and vision, the Scrum master who facilitates the process and removes roadblocks, and the developers who deliver the work. The four events include sprint planning, daily Scrum, sprint review and sprint retrospective to keep teams focused and improving. The three artifacts are the product backlog, sprint backlog, and product increment, which represent planned work, active tasks, and completed deliverables.
Scrum officially defines three core artifacts: the product backlog, sprint backlog, and product increment. However, many teams also recognize four additional artifacts — the product goal, sprint, definition of done, and burndown chart — that support transparency and alignment. Altogether, these seven artifacts help teams plan, track, and deliver work more effectively within the Scrum framework.
The four Scrum events, also called ceremonies, are:
- Sprint planning — the team defines what will be delivered during the upcoming sprint and how the work will be achieved.
- Daily Scrum — a short daily meeting where team members discuss progress, upcoming work, and any blockers.
- Sprint review — held at the end of the sprint to inspect the completed work and gather feedback from stakeholders.
- Sprint retrospective — the team reflects on the sprint to identify what went well, what didn’t, and how to improve in the next cycle.
The sprint itself is sometimes referred to as a fifth event, encompassing all four, but officially, these are the four events.
The four Agile values, outlined in the Agile Manifesto, are:
- Individuals and interactions over processes and tools — teamwork and communication matter more than rigid systems.
- Working software over comprehensive documentation — delivering functional results takes priority over excessive paperwork.
- Customer collaboration over contract negotiation — engaging with customers ensures the final product meets real needs.
- Responding to change over following a plan — flexibility and adaptability are valued more than sticking to a fixed roadmap.
Agile is a project management philosophy that emphasizes flexibility, collaboration, and iterative progress toward goals. It’s based on the Agile Manifesto, which values individuals and interactions, working software, customer collaboration, and responding to change.
Scrum, on the other hand, is a specific framework within Agile. It provides a structured way to apply Agile principles using defined roles (product owner, Scrum master, developers), events (like sprints and daily stand-ups), and artifacts (such as the product backlog).
In short, Agile is the mindset, and Scrum is one of the most common methods used to implement it.
