Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

How to demo in Scrum /agile  RSS feed

 
ambi ambii
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

We demo our completed stories after end of every sprint. I've heard few members in my team saying that we need documentation as a pre-requisite for demoing our work.Just wondering if documentation is required at all before demoing our work. Also, even if a document is made .. whose will refer it and what for???

I believe we should brief the Product owner and our scrum master/rest of the team about the story rather than creating a document. Please suggest me about what do you think is the right approach of giving Demos at end of sprint.

Thanks
Ambi
 
luri ron
Ranch Hand
Posts: 87
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
in my previous experience, we don't provide a documentation. when you demo, you show the user a working software which itself is much better than a document. however, one document to describe the features that are demoed, and the non-functional features should be handy for the discussion. in term of formalities of the document, it should ahere to a consistent format.
 
ambi ambii
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for your message. So this document should be provided by Tester or product Owner should make it?
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!