Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

agile framework scrum document models

Last post 03:41 pm March 15, 2021 by Daniel Wilhite
3 replies
01:53 am March 14, 2021

What are the document models used in the agile scrum framework?


02:44 am March 14, 2021

Documentation may be negotiated on the Product Backlog or otherwise committed to in the Definition of Done, then planned and actioned in a timeboxed manner on the Sprint Backlog.


04:11 am March 15, 2021

I agree with Ian.

The document model is embedded in three artefacts:

Product Backlog

Sprint Backlog

Iteration (/aggregated iterations)

The nuance in Scrum is to get the organisational document model/taxonemy integrated coherently into the definition of done. On successful product teams I have worked on that meant getting the documents to a place where document impact maps are as easy to understand as feature impact maps are. If you know what features/functions you're touching in your product, you then know what documents have a mandatory/highly recommended/optional update. 


03:41 pm March 15, 2021

The Product Backlog is the primary source of documentation as it is a living body of information about what work needs to be done to the Product. 

The key is that any documentation being created and maintained needs to have value to the team and the organization.  It needs to provide insights into the work being done and not be created for the sake of checking a box on a checklist.  Also it needs to actually reflect the work as it happens.  The Product Backlog is the only documentation that drives the work that is being done. No other documentation should impact the work being done or the way that work is done.  

There could be some documentation that is required by the organization.  For example, some companies require "Run Manuals" which the IT Operations teams will use to keep the application running in a production environment.  As such, the Scrum Team will need to provide and update that documentation.


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.