Capturing Information/Requirements Formally

Moderator: kwalford

New Member
New Member
Posts: 1
Joined: Tue 05 Jul 2016 3:21 pm

Capturing Information/Requirements Formally

Postby ps124 » Wed 06 Jul 2016 6:14 pm

Hi, new to this forum...this is my first post.

I've just kicked off a new project, which is in the 'storming' phase. Loads of questions to and from the customer and from me. Comments/suggestions/requirements/information is passed all over the place and at present it's all just via emails. I've taken minutes and sent these out whenever we've had a meeting, but what I want to know is whether to capture all of these items in some sort of formal document or log. At present, I'm just logging these onto a simple customer made spreadsheet, which I can send to the customer and will do the trick, but is there a formal way of doing this? I'm not aware of anything.

Thanks, all.

Expert Member
Expert Member
Posts: 53
Joined: Thu 28 Apr 2016 12:03 pm
Location: Bangalore

Re: Capturing Information/Requirements Formally

Postby jayashree » Mon 12 Sep 2016 7:48 am

Maintaining it in a spreadsheet is really good as you should keep on updating it. Maintain an online document if you need one.

Who is online

Users browsing this forum: No registered users and 1 guest