Requirements Management Tools - GoFuckYourself.com

Validus · 11-12-2014, 05:30 PM

Hey, any of you magical programmers or development people in general, have any recommendations of good requirements management tools? Need to manage lots of software requirements, prioritize them... you know, the stuff that Excel could but isn't ideal for

AdultKing · 11-12-2014, 06:35 PM

I use Merlin.

http://www.projectwizards.net/en/merlin/

edgeprod · 11-12-2014, 07:01 PM

Requirements management has a number of stages that may be vastly overkill for anything less than enterprise-level software. Do you really need to go through the traditional path of investigation, feasibility, design, construction, test, change management, and then release? Likely, you just need to build a minimum viable product from a strong spec sheet, and protect against feature creep.

For that, I'd recommend you consider a kan-ban type of system, which will provide visibility to management as well as keep your programmers on task. It allows for sprints and feature-set prioritization, while maintaining the transparency that lets you keep management in the loop.

Tekkno · 11-12-2014, 11:36 PM

I use youtrack.. it can be modified easily to suit every need..

11-12-2014, 05:30 PM	#1
Validus Confirmed User Industry Role: Join Date: Jul 2001 Location: Calgary, Canada Posts: 4,012	Requirements Management Tools Hey, any of you magical programmers or development people in general, have any recommendations of good requirements management tools? Need to manage lots of software requirements, prioritize them... you know, the stuff that Excel could but isn't ideal for

11-12-2014, 06:35 PM	#2
AdultKing Raise Your Weapon Industry Role: Join Date: Jun 2003 Location: Outback Australia Posts: 15,601	I use Merlin. http://www.projectwizards.net/en/merlin/

11-12-2014, 07:01 PM	#3
edgeprod Permanently Gone Industry Role: Join Date: Mar 2004 Posts: 10,019	Requirements management has a number of stages that may be vastly overkill for anything less than enterprise-level software. Do you really need to go through the traditional path of investigation, feasibility, design, construction, test, change management, and then release? Likely, you just need to build a minimum viable product from a strong spec sheet, and protect against feature creep. For that, I'd recommend you consider a kan-ban type of system, which will provide visibility to management as well as keep your programmers on task. It allows for sprints and feature-set prioritization, while maintaining the transparency that lets you keep management in the loop.

11-12-2014, 11:36 PM	#4
Tekkno Registered User Industry Role: Join Date: Nov 2014 Location: http://youtu.be/liD0w2mkyzw Posts: 72	I use youtrack.. it can be modified easily to suit every need..