Documentation for Product Owner or Product Manager

Last post 06:36 pm July 26, 2024 by Ian Mitchell

1 reply

04:41 pm July 26, 2024

Hi, I have a confusion. In scrum there are very few documentations as per need. But I need to lock scope with the customer what should I do in that case. Then there are PRDs, BRDs and FRDs being frequently used Product Owners/Managers or organizations. What is your take on this? Please advice

Ian Mitchell

06:36 pm July 26, 2024

If scope can truthfully be locked at all, then you don't need Scrum. You know what to build.

Scrum is about innovation, and learning to build the right thing at the right time. Far from being locked, scope is held to be emergent. There's no requirements document, but there is a Product Backlog which is continually refined and curated.

In agile practice, requirements change is expected and welcomed, even late in development.

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.