Back to Forum

What is knowledge acquisition in product backlog

Last post 03:01 pm February 9, 2016 by Andrzej Zińczuk
2 replies
Prashant Pathak
07:25 am February 23, 2015

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!!!!

Roman Kleiner
12:01 pm February 23, 2015

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.

Andrzej Zińczuk
03:01 pm February 9, 2016

Some PBI to get implemented need additional decisions and steps made before. During sprints it is easy to focus only on incoming sprint, which may be to short horizon for proper planning and decision making.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.