TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: Requirements management systems From:Claire Philpott <cphilpott -at- ppf -dot- com -dot- cy> To:"jennysubs -at- mac -dot- com" <jennysubs -at- mac -dot- com>, techwr-l List <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 21 Apr 2010 05:55:53 +0000
Hi Jenny
The small development team that I work with uses VersionOne which is also free for up to 10 users, and after that 29$ per user with a requirement for an annual license.
They have a 30 day trial available.
Like Rally, VersionOne is SAS and facilitates access from any location. It was also developed to support Agile software development.
I have been using it for 3 months and like it though I still have a lot to learn about how to use all its features.
-----Original Message-----
From: techwr-l-bounces+cphilpott=ppf -dot- com -dot- cy -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+cphilpott=ppf -dot- com -dot- cy -at- lists -dot- techwr-l -dot- com] On Behalf Of jennysubs -at- mac -dot- com
Sent: 21 April 2010 03:42
To: techwr-l List
Subject: Requirements management systems
Hi all,
My current client is a fairly small hardware/software shop with a relatively immature engineering organization.
Right now, we get requirements in the form of screen shots developed by a marketing person. They sometimes come with a written description of how the controls work, but often we don't get even that much.
The engineering manager would like to put in place some sort of requirements management system. It has to be relatively easy to use and free or cheap. (Not asking for much, right?)
We need a tool that gives us a place to store requirements and art work and record the questions (and answers) generated by the screen shots. We've tried using an open wiki for this, but it's not working very well. Nobody is very excited about using Excel and Word.
The development organization uses a SCRUM-like process, but we have no control over the front end use cases, etc. (We don't get any, either.) I expect that at the beginning, at least, we will flesh out requirements and create specs for small chunks of development. Eventually, it would be nice to have the archaeological record around to help new people come up to speed. The tool needs to support use by about 15-20 people, including engineering, QA, and me, the writer.
The hope is that by having a tool and enforcing its use, we can make our lives easier in the engineering organization and eventually train the folks developing the "requirements" to be more precise.
I said that I would appeal to the collective wisdom of the techwr-l list, since you've seen it all.
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
---
You are currently subscribed to TECHWR-L as cphilpott -at- ppf -dot- com -dot- cy -dot-
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
