1. Scrum uses artifacts to ensure transparency and accountability in the work and value delivered.
2. The three artifacts of Scrum are the Product Backlog, the Sprint Backlog, and the Increment.
3. The Product Goal should be clear and definite, while the Sprint Goal should be a short-term mission that gets closer to fulfilling the Product Goal.
The article is generally reliable as it provides an overview of how Scrum can be applied in non-software teams, with a focus on its three core artifacts - Product Backlog, Sprint Backlog, and Increment. It also provides guidance on how these artifacts can be used to remain focused on what is important and measure progress against a shared standard.
However, there are some potential biases in the article that could affect its trustworthiness. For example, it does not explore any counterarguments or present both sides equally when discussing Scrum's application in non-software teams. Additionally, there is no evidence provided for some of the claims made about Scrum's effectiveness in this context. Furthermore, there is no mention of possible risks associated with using Scrum in non-software teams which could lead readers to believe that it is risk-free when this may not necessarily be true.
In conclusion, while this article provides useful information about applying Scrum in non-software teams, it should be read with caution due to potential biases and unsupported claims which could affect its trustworthiness and reliability.