As new information is learned, the team must negotiate with the Product Owner regardless of what it is. If the Developers feel strongly about something they think something needs adjusting, they are responsible for communicating the changes to the Product Owner before acting.

Agile scrum artifacts are information that a scrum team and stakeholders use to detail the product being developed, actions to produce it, and the actions performed during the project. The main agile scrum artifacts are product backlog, sprint backlog, and increments.

The term artifact is often associated with archaeological ruins and ancient relics. Yet in software development, the term artifact refers to key information needed during the development of a product.

Agile scrum artifacts are information that a scrum team and stakeholders use to detail the product being developed, actions to produce it, and the actions performed during the project. These artifacts provide metadata points that give insight into the performance of a sprint. They are essential tools for every scrum team since they enable core scrum attributes of transparency, inspection, and adaption.

Scrum Master Responsibilities:
1. Implement Project Management/Best Practices;
2. Keep all Parties on Track and Informed;
3. Introduce Agile Engineering Practices;
4. Coach Team Members;
5. Host Daily Stand-up Meetings;
6. Assist the Product Owner With the Product Backlog. It is the product owner’s responsibility to create and maintain the product backlog. The Scrum Master helps the product owner refine and maintain the backlog by using information gathered from standup meetings. They schedule review meetings and prioritize work on user stories.
7. Remove Roadblocks;
8. Teach Scrum Practices and Principles.

The daily scrum is designed for the team to coordinate and adapt its progress within the sprint. At a minimum, the product team should be in attendance. Typically, the invite list should also include the product manager and scrum master or delivery manager.
Although stakeholders and others outside of the team are generally welcome to attend, the intended audience is the team. Any attendees outside of the team should be observers only.

Product Backlog refinement is an ongoing process in which the Product Owner and the Development Team collaborate on reviewing and revising detail, estimates, and orders for items in the Product Backlog.

The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion. The Product Owner isn’t part of the Development Team and can invest as much time as necessary and enlist the help of other members of the Scrum Team.

The Sprint Backlog represents the work that a Development Team needs to pull from the Product Backlog to achieve the Sprint Goal. The Sprint Goal is an objective set by the Scrum Team during Sprint Planning and captures the hypothesis that the team wants to test, a goal it wants to achieve, or an experiment to run. Although the Sprint Goal is fixed during the Sprint, the Sprint Backlog is not. This would be unwise considering the core premise of Scrum: we can't create detailed plans for the future. Even if that future is a single Sprint, it is entirely possible that new insights or impediments emerge as the Development Team works through the Sprint Backlog.

A team might learn that a technology they picked does not perform as expected. Or a key feature needed to reach the Sprint Goal was missed during the Sprint Planning. As issues emerge, changes to the Sprint Backlog may be warranted in order to reach the Sprint Goal. The Development Team will then re-negotiate the Sprint Backlog with the Product Owner. In short; a Sprint Backlog is flexible, as long as changes do not distract from the focus on the Sprint Goal.

The Daily Scrum presents Development Teams with an excellent opportunity to inspect and adapt upon their progress to the Sprint Goal and make adjustments to the Sprint Backlog when deemed necessary.