What is knowledge acquisition in product backlog
Hi All,
I am very new in Scrum, and I read some topics from internet,
I am confused with the term "knowledge acquisition in product backlog".
I am not able to understand what it mean and what is the advantages of having it.
I got some examples (mentioned below) related to this but still I did understand
"An example of knowledge acquisition could be a scrum backlog item about researching WordPress plugin libraries and making a selection."
"Create a prototype or proof of concept of two architectures and run three tests to determine which would be a better approach for our product."
Please help me to understand this!!!!
My understanding is that these are planning tasks which are required to make a future technical decision and precise scheduling.
For example, we might have a future user story: Implement an auto-upgrade service for our endpoint client. To do that, we need to have a design and technology choice in place, thus we might have a knowledge acquisition task called: Prepare high-level architecture for auto-upgrade.
If we do not have existing auto-upgrade experience in the team, we might have even an earlier task called Research and summarise existing auto-upgrade techniques.
The idea is that each task in the path allows us to have proper and reliable estimates for the next one.
