Ygthkb

Explicit Riemann Hilbert correspondence

Can I travel from country A to country B to country C without going back to country A?

Taking an academic pseudonym?

Why is it that Bernie Sanders is always called a "socialist"?

Critique vs nitpicking

Do we still track damage on indestructible creatures?

Is the percentage symbol a constant?

Given a total recursive function, can you always compute its fixed-point?

Minimum Viable Product for RTS game?

Can you say "leftside right"?

Players preemptively rolling, even though their rolls are useless or are checking the wrong skills

Identical projects by students at two different colleges: still plagiarism?

What species should be used for storage of human minds?

Renting a 2CV in France

How bad is a Computer Science course that doesn't teach Design Patterns?

What's the reason that we have a different number of days each month?

In the Lost in Space intro why was Dr. Smith actor listed as a special guest star?

Coworker asking me to not bring cakes due to self control issue. What should I do?

Buying a "Used" Router

Performance and power usage for Raspberry Pi in the Stratosphere

Is it recommended to be 100% delegated for a baker?

Does Plato's "Ring of Gyges" have a corrupting influence on its wearer?

Boss asked me to sign a resignation paper without a date on it along with my new contract

smartctl reports overall health test as passed but the tests failed?

what is the required document in Agile

What are some agile (scrum) metrics?Analysis document in ScrumSatisfying an external auditor when using AgileWhat are alternative agile applications?Is there any place for the Prince 2 Mandate Document 'Quality Expectations' in an agile development?What are some Agile Testing Estimation Techniques?what should I do to overcome the agile process related issues in my organization?Organizing testing in a Scrum(ish) development projectIs the “definition of done” required in Scrum?What is an Agile “Reflection?”

1

Good day dears, i am confused about documentation in Agile as below

we try to implement Scrum in our company, the problem we faced is our traditional thinking which always requires physical document, My manager always asking me about Business Requirements Specification (BRS) and Software Requirements Specification(SRS)

is it a valid habit to writing user stories and their acceptance criteria as an alternative of (BRS and SRS) in a single document?

if it is yes, can you supply me with any template? what is the ISO standard related to Agile documentation? we use TFS project management, any suggestion about the problem

thanks.

scrum

share|improve this question

asked 1 hour ago

user35136user35136

61

New contributor

user35136 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If your company has an existing workflow that uses BRS and SRS then you should find out how those documents are used. What purposes are they serving? Who reads them and what do they do with them? Talk to the consumers of these documents about what they would need and if they feel your user stories would satisfy these needs.
  
  – Pace
  33 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Good i will,based on your experience, as a development team, can we implement the code based on user story bounded with acceptance criteria.In our current model the SRS feed into development team and testing team use the same document to verify the developed feature
  
  – user35136
  4 mins ago
  
  
  

  
  
  
  

add a comment | 

1

Good day dears, i am confused about documentation in Agile as below

we try to implement Scrum in our company, the problem we faced is our traditional thinking which always requires physical document, My manager always asking me about Business Requirements Specification (BRS) and Software Requirements Specification(SRS)

is it a valid habit to writing user stories and their acceptance criteria as an alternative of (BRS and SRS) in a single document?

if it is yes, can you supply me with any template? what is the ISO standard related to Agile documentation? we use TFS project management, any suggestion about the problem

thanks.

scrum

share|improve this question

asked 1 hour ago

user35136user35136

61

New contributor

user35136 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If your company has an existing workflow that uses BRS and SRS then you should find out how those documents are used. What purposes are they serving? Who reads them and what do they do with them? Talk to the consumers of these documents about what they would need and if they feel your user stories would satisfy these needs.
  
  – Pace
  33 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Good i will,based on your experience, as a development team, can we implement the code based on user story bounded with acceptance criteria.In our current model the SRS feed into development team and testing team use the same document to verify the developed feature
  
  – user35136
  4 mins ago
  
  
  

  
  
  
  

add a comment | 

Good day dears, i am confused about documentation in Agile as below

we try to implement Scrum in our company, the problem we faced is our traditional thinking which always requires physical document, My manager always asking me about Business Requirements Specification (BRS) and Software Requirements Specification(SRS)

is it a valid habit to writing user stories and their acceptance criteria as an alternative of (BRS and SRS) in a single document?

if it is yes, can you supply me with any template? what is the ISO standard related to Agile documentation? we use TFS project management, any suggestion about the problem

thanks.

scrum

share|improve this question

asked 1 hour ago

user35136user35136

61

New contributor

user35136 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 1 hour ago

user35136user35136

61

New contributor

user35136 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 1 hour ago

user35136user35136

61

New contributor

user35136 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 1 hour ago

user35136user35136

61

New contributor

user35136 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 1 hour ago

user35136user35136

61

2 Answers
2

active

oldest

votes

2

In the manifesto for Agile software development one can read:

Working software over comprehensive documentation

This doesn't mean documentation is a bad thing. Instead, working code is better so you can document what you are going to code.

That being said, user stories and acceptance criteria might be all you need to understand the requirements, considering you're not responsible for the Vision and Scope Document.

share|improve this answer

answered 1 hour ago

Tiago Martins PeresTiago Martins Peres

4911418

add a comment | 

2

I encourage people not to think of user stories (or backlog items of any kind) as another form of requirements. There is a critical difference in thinking between the use of requirements documents and backlogs that teams and organizations need to understand in order to effectively use the latter. Backlogs are emergent. This means that they not only change over time (there's nothing stopping a BRS from changing) but that later backlog items build on and modify earlier items such that it is possible that the earlier items no longer describe the application's behavior.

This means that the documentation you require will largely be separate from your requirements (think of it as what you walked into development knowing vs what you did in development). Note that things like ISO 9001 is mostly about validating that you follow your processes (whatever those happen to be) and that you record information you will need to audit or maintain the software later. The days where documentation and audit standards were about making sure the result matched the original idea perfectly are largely gone. The only place I see that anymore is places where they have it written into their processes and don't want to change the documented processes, in which case it's a conscious choice, not a constraint.

share|improve this answer

answered 1 hour ago

DanielDaniel

8,61921125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Seconding this. The ISO rules simply say you need a well defined process. If your company decides that process includes SRS and BRS then your company needs to define how, if at all, the agile processes generate those documents. If your company decides that user stories will be the SRS or BRS then simply write that down as your process and follow it to make ISO happy.
  
  – Pace
  37 mins ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "208"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

user35136 is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f25875%2fwhat-is-the-required-document-in-agile%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

2

In the manifesto for Agile software development one can read:

Working software over comprehensive documentation

This doesn't mean documentation is a bad thing. Instead, working code is better so you can document what you are going to code.

That being said, user stories and acceptance criteria might be all you need to understand the requirements, considering you're not responsible for the Vision and Scope Document.

share|improve this answer

answered 1 hour ago

Tiago Martins PeresTiago Martins Peres

4911418

add a comment | 

2

In the manifesto for Agile software development one can read:

Working software over comprehensive documentation

This doesn't mean documentation is a bad thing. Instead, working code is better so you can document what you are going to code.

That being said, user stories and acceptance criteria might be all you need to understand the requirements, considering you're not responsible for the Vision and Scope Document.

share|improve this answer

answered 1 hour ago

Tiago Martins PeresTiago Martins Peres

4911418

add a comment | 

In the manifesto for Agile software development one can read:

Working software over comprehensive documentation

This doesn't mean documentation is a bad thing. Instead, working code is better so you can document what you are going to code.

That being said, user stories and acceptance criteria might be all you need to understand the requirements, considering you're not responsible for the Vision and Scope Document.

share|improve this answer

answered 1 hour ago

Tiago Martins PeresTiago Martins Peres

4911418

share|improve this answer

answered 1 hour ago

Tiago Martins PeresTiago Martins Peres

4911418

answered 1 hour ago

Tiago Martins PeresTiago Martins Peres

4911418

answered 1 hour ago

Tiago Martins PeresTiago Martins Peres

4911418

2

I encourage people not to think of user stories (or backlog items of any kind) as another form of requirements. There is a critical difference in thinking between the use of requirements documents and backlogs that teams and organizations need to understand in order to effectively use the latter. Backlogs are emergent. This means that they not only change over time (there's nothing stopping a BRS from changing) but that later backlog items build on and modify earlier items such that it is possible that the earlier items no longer describe the application's behavior.

This means that the documentation you require will largely be separate from your requirements (think of it as what you walked into development knowing vs what you did in development). Note that things like ISO 9001 is mostly about validating that you follow your processes (whatever those happen to be) and that you record information you will need to audit or maintain the software later. The days where documentation and audit standards were about making sure the result matched the original idea perfectly are largely gone. The only place I see that anymore is places where they have it written into their processes and don't want to change the documented processes, in which case it's a conscious choice, not a constraint.

share|improve this answer

answered 1 hour ago

DanielDaniel

8,61921125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Seconding this. The ISO rules simply say you need a well defined process. If your company decides that process includes SRS and BRS then your company needs to define how, if at all, the agile processes generate those documents. If your company decides that user stories will be the SRS or BRS then simply write that down as your process and follow it to make ISO happy.
  
  – Pace
  37 mins ago
  

  
  
  
  

add a comment | 

2

I encourage people not to think of user stories (or backlog items of any kind) as another form of requirements. There is a critical difference in thinking between the use of requirements documents and backlogs that teams and organizations need to understand in order to effectively use the latter. Backlogs are emergent. This means that they not only change over time (there's nothing stopping a BRS from changing) but that later backlog items build on and modify earlier items such that it is possible that the earlier items no longer describe the application's behavior.

This means that the documentation you require will largely be separate from your requirements (think of it as what you walked into development knowing vs what you did in development). Note that things like ISO 9001 is mostly about validating that you follow your processes (whatever those happen to be) and that you record information you will need to audit or maintain the software later. The days where documentation and audit standards were about making sure the result matched the original idea perfectly are largely gone. The only place I see that anymore is places where they have it written into their processes and don't want to change the documented processes, in which case it's a conscious choice, not a constraint.

share|improve this answer

answered 1 hour ago

DanielDaniel

8,61921125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Seconding this. The ISO rules simply say you need a well defined process. If your company decides that process includes SRS and BRS then your company needs to define how, if at all, the agile processes generate those documents. If your company decides that user stories will be the SRS or BRS then simply write that down as your process and follow it to make ISO happy.
  
  – Pace
  37 mins ago
  

  
  
  
  

add a comment | 

I encourage people not to think of user stories (or backlog items of any kind) as another form of requirements. There is a critical difference in thinking between the use of requirements documents and backlogs that teams and organizations need to understand in order to effectively use the latter. Backlogs are emergent. This means that they not only change over time (there's nothing stopping a BRS from changing) but that later backlog items build on and modify earlier items such that it is possible that the earlier items no longer describe the application's behavior.

This means that the documentation you require will largely be separate from your requirements (think of it as what you walked into development knowing vs what you did in development). Note that things like ISO 9001 is mostly about validating that you follow your processes (whatever those happen to be) and that you record information you will need to audit or maintain the software later. The days where documentation and audit standards were about making sure the result matched the original idea perfectly are largely gone. The only place I see that anymore is places where they have it written into their processes and don't want to change the documented processes, in which case it's a conscious choice, not a constraint.

share|improve this answer

answered 1 hour ago

DanielDaniel

8,61921125

share|improve this answer

answered 1 hour ago

DanielDaniel

8,61921125

answered 1 hour ago

DanielDaniel

8,61921125

answered 1 hour ago

DanielDaniel

8,61921125