Scrum methodology documentation template

Question

I am well versed in documenting application requirements using case studies and modeling systems using the Rational Unified Process.

But now, I would like to know if there is a template or model for documenting system requirements when using an Agile methodology such as Scrum.

thanks

Answer 1

Check it out: http://www.scrumbasics.com/scrum-documentation/

(PS: Scrum is a wireframe)

Answer 2

But now, I would like to know if there is a template or model for documenting system requirements when using an Agile methodology such as Scrum.

There is no template for Scrum, because Scrum does not prescribe a way to capture requirements and allows you to use anything that suits your context. Many (web teams) use User Stories , and this works well for them, but there is no general agreement. Just in case, the recommended template for user stories:

"As <user type>, I want <some goals> to <some reason>."

But nothing forces you to use stories, and they are not suitable for all projects (for example, Jeff Sutherland said that he will never use stories again for PDA projects, the user interface and navigation rules are too complicated for stories).

With Scrum, I would say that the general principle is to create specifications enough (and just in time) (which differs from a model with an exhaustive use of RUP in this approach), you decide which format is suitable for your context.

Answer 3

You can continue to describe your requirements as use cases. Or like user stories. Or like poetry. Regardless of what you (the team, you include the Product Owner, the team and ScrumMaster - and potentially even interested parties) are known and understanding. However, there are two implicit requirements emanating from Scrum.

Requirements should be described in such a way that: a) their separation to the point where one requirement is what can be done in one sprint, b) and that this requirement when choosing for a sprint can be fully and clearly implemented ("done" )

This is why user stories are so popular. They are easy to understand, and they can be easily demonstrated - just grab and try with the increment obtained during the sprint to check if this is really done.