Welcome to the Simplilearn Community

Want to join the rest of our members? Sign up right away!

Sign Up

Question on Documentation of requirements in Agile setup

Rajan Sood

Rajan
Alumni
Hello Friends,

As we know that in Scrum setup, the focus on documentation of requirements is very less. Requirements are discussed in the daily meetings and most of the time there isn't any detailed documentation done.

Isn't that create an issue later on? What we have learned so far in software development (or in Project Management in general) is that "Work not documented is work not done".

How Agile/Scrum deals with this issue?

Thanks,
Rajan
 

_3223

New Member
Hi Rajan!

As far as Agile/Scrum process is concerned we do minimum documents using Product Backlog, Release Backlog, Sprint Backlog and through EPIC, User Stories.

We don't have concept of Project manager rather we have Product Owner [ Who works closely with stake holders and provide requirements to the team], Scrum Master[Servant Leader, who facilitates the conversation between Product Owner and Team and Remove impediments] and Team [Based on Product backlog it will have Developer, Tester, Architects, self driven team].

Product Owner is the one who gives requirement to the team which will be classified in to EPIC, User Stores, Tasks which is nothing but feature by feature written down. Normally written requirements are light weight and Visual.

It doesn't mean we don't have any of these in place.

Various ceremonies being conducted part of Agile/scrum which includes Sprint Planning[Preparing the Product Backlog, Release Backlog, Sprint Backlog], Daily Scrum[Whats done yesterday, whats to be done today, Any Impediments] , Sprint Review[Demo of working software, Feedback] Sprint Retrospective[Identify Top 2 or 3 learning where in improvements can be brought in coming sprint cycles].

So in a short we do have lot of information captured and shared across.

I hope this gives some inside.
 

KRISHNA MURTHY

Active Member
Alumni
Hello Friends,

As we know that in Scrum setup, the focus on documentation of requirements is very less. Requirements are discussed in the daily meetings and most of the time there isn't any detailed documentation done.

Isn't that create an issue later on? What we have learned so far in software development (or in Project Management in general) is that "Work not documented is work not done".

How Agile/Scrum deals with this issue?

Thanks,
Rajan
Hi Rajan,

As per my knowledge,Agile will be giving less importance to the documentation.But its not avoiding fully.
Documentation is needed as and when its mandatory.Instead of Documentation in Agile ,we will be concentration on working software deliverable to the customer.

Regards
Krishna
 
Top