I'm agree with you :)
If I may, the artifacts are backlog, sprint backlog and increment. Increment is not sprint burn down chart. As I know, scrum guide never mention any chart :)
I added increment to the artifacts. The Scrum Guide does mention the burn down chart, but in passing and not in depth.
I grant you that it isn't listed in the artifacts, by The Scrum Guide. But it is a secondary artifact, as are things like velocity (if used by the team), and a roster of team members who participated in a given sprint, and vacations, and if there were disruptions (power outages, hurricanes, IT upgrades that brought development to a halt, patch Tuesday), or anything else that is a product or byproduct of the development effort.
I wasn't emphasizing the roles, events, and artifacts in my post. I figured those are all mulled over sufficiently in The Scrum Guide. :-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm agree with you :)
If I may, the artifacts are backlog, sprint backlog and increment. Increment is not sprint burn down chart. As I know, scrum guide never mention any chart :)
I added increment to the artifacts. The Scrum Guide does mention the burn down chart, but in passing and not in depth.
I grant you that it isn't listed in the artifacts, by The Scrum Guide. But it is a secondary artifact, as are things like velocity (if used by the team), and a roster of team members who participated in a given sprint, and vacations, and if there were disruptions (power outages, hurricanes, IT upgrades that brought development to a halt, patch Tuesday), or anything else that is a product or byproduct of the development effort.
I wasn't emphasizing the roles, events, and artifacts in my post. I figured those are all mulled over sufficiently in The Scrum Guide. :-)