There are a number of requirements management tools on the market that can help Business Analysts and project teams more efficiently document, communicate, and manage requirements. Most have integration points with modeling, development, and testing tools allowing teams to trace requirements through the project lifecycle.
I want to stress that these tools will help you increase your efficiency. This implies that you have already implemented a requirements management process/methodology that teams are effectively using. Requirements management tools will make you more efficient only if you have a methodology that everyone understands. Here are some steps to take before you start looking to purchase a tool.
- Create and document a requirements management methodology. Know what your needs are before finding a technical solution. The methodology should include what your requirements package looks like, how you categorize requirements, what attributes you track, how you trace requirements, and who does what and at what point in the project.
- Implement this methodology using tools like Microsoft Word which mostly everyone has access to and knows how to use.
- Use this methodology on pilot projects, identify lessons learned, and make the necessary adjustments.
- Establish a support structure where project teams can get assistance with using the methodology and provide feedback. The support team should be responsible for making adjustments to the methodology and communicating the changes.
- Roll out the methodology to all teams in your organization.
- When the methodology (process) is in place and the people using the methodology are effectively implementing it, you can begin looking for a tool to increase your efficiency.
- Use your requirements management methodology as your requirements for the tool.
If you do the above successfully you have a great chance for a successful tool implementation. The good news is that some of the tool vendors don’t shy away from the fact that you should have a methodology in place.
I would love to hear from others that have implemented or are planning to implement a requirements management tool. Please share your thoughts and experiences.
October 25th, 2006 at 12:28 pm
I think you make a good point here. Tools are often looked at as the silver bullet to fix a broken process.
I’ve seen teams seek tools that simplify the requirements elicitation process - or document requirements auto-magically. In my experience, this isn’t the time to use a tool. Use the tool for documentation, change management, communication, traceability etc.
For the nitty gritty task of figuring out what someone really needs, I don’t know if I’d want to automate that process. In my opinion the goal is to determine what is really needed - not what someone thinks they need. For that task and reaching agreement across multiple personalities, organizations, languages, backgrounds etc, my money’s on a skilled analyst. Someone that can interview, facilitate, manage, problem solve and document. White-boards, paper, audio-recorders, video-recorders and other tools that capture without restricting thought are about all the tools you need.
Tools do a great job of supporting a well functioning team. As you say, they can make everyone more efficient. They also allow teams to do what would be time-prohibitive, such as managing traceability on large projects, or keeping everyone updated when an artifact changes.
October 29th, 2006 at 3:37 am
I agree to your opinion, i worked on various IT Projects as BA and we did managed requirements gathering phase by using simple word document templates.
business analysis framework must be established first and thoroughly understood by BA, analysis framework applicability for the project is eased by use of software tools and selection of right software tool for your analysis framework is very tedious task.