• Easy Redmine

Whether it is about capturing requirements, designing test cases, test execution reports, informing other team-members aboutprogress etc. A test management tool is mandatory. Even small error in recording these details may lead to catastrophic effect and failure of the project. So, to manage all these details some test management tools can come very handy and useful.

Let see some of the best test management and QA tools. 1)is the #1 selling test management tool, providing end-to-end solutions for agile teams of all sizes. Get the flexibility, visibility, and insights you need to release better software FASTERFeatures:.

1-click Integration with JIRA, Confluence, Jenkins, Bamboo, and more. Cloud, Server, and Data Center Deployment Options. Advanced Analytics and DevOps Dashboards. No Annual Commitment Required2)is a continuous testing platform for Agile and DevOps teams that enables teams to collaborate on an idea, test code continuously and generate living documentation from real-time insights. Hiptest is used by over 25,000 users in 140 countries.Features:. Native BDD support to align your team and streamline workflows and living documentation of your product.

Automate your tests with a selection of over 20+ frameworks supported including: Cucumber, Specflow, Java/Junit, Selenium, and more!. CI/CD pipeline integrations with tools like Jenkins, Bamboo, TravisCI, Shippable, and more. Scenario editor, reusable steps, and easy test refactoring for painless test creation. Free fast, expert support along with a dedicated customer success team.is an end-to-end test management tool.

I would like to discuss with you a special case of requirements management. I call it “requirements management for mere mortals”.I had worked as a project manager in a small web development company.Significant part of my daily job was talking with our clients totranslate their wishes into the tasks for our developers.The problem I faced is that most of the approaches and tools I usedpreviously simply did not fit.The root cause is that I had to work withcompletely non-techie stakeholders who do not care about requirements.Another issue is a large volume of data. I had to organize info on dozens of small projects each month.While I have adapted to the process in general there is an issue that I did not manageto overcome – software.

Is this an accurate summary of why you need a system? We can't find information we needbecauseThere is no single repository of information to refer tobecauseThere are lots of emails and documents with scattered informationsoWe need a system to centralise information from emails and documentsIf the answer was yes, I understand how you got to the 'I need a system for this' solution.But what if we keep going? We can't find information we needbecauseThere is no single repository of information to refer tobecauseThere are lots of emails and documents with scattered informationbecauseThere are frequent changes in requirementsbecauseCustomers aren't yet sure what they wantsoI need to help my customer develop their wishes into something I can work on.Even then, there is probably another layer (or more) of 'because' that you need to get to. Solving it might mean the problem of constant change and the associated emails and document revisions goes away. No tool is going to solve the issue of stakeholders not understanding what a good requirement is and why it is important.

It is the process you need to work on - if you have bad requirements, no matter how fancy and sophisticated your software is, you will still get bad requirements (rubbish in, rubbish out).Personnally I find that MS Excel works perfectly fine. I like to keep things simple and avoid over-engineering things - I find that unless you are in an organization/industry that demands stringent control over requirements definition/validation there are a lot of features you mention that you can do without (and some of them can be done in MS Excel).Some recommendations:. Educate your stakeholders on requirements definition: organize a workshop and share with them principles and ground rules of effective requirements gathering, using examples of 'good' and 'bad' (and 'ugly'!). Get them to work with sample requirements - don't take their own requirements as examples, try to use requirements from a different project so your stakeholders can look at them and practice in a neutral, objective manner. Use techniques that help your stakeholders define requirements: use imagery, visualisation techniques, process mapping, mind mapping, user case or user stories to help your stakeholders define and articulate their needs. Help them write good requirements by suggesting appropriate wording.

Easy Redmine

Get them to focus on value: when defining requirements, make your stakeholders put a value (business benefit) on each of them: e.g. What will this enable? How will it impact our ability to execute a business process?

How will it help us improve what we do? Focus on tangible benefits rather than loose improvements (eg. 'will reduce time to produce analytics by 80%' vs 'faster reports').

Be clear about roles in the requirements definition process: business requirements should not be defined by the technical team because they are not be technical requirements. The fact that your stakeholders are not technical is actually an advantage because when you have stakeholders who are (or think they are.), you often end up with people thinking about the solution before the need (eg. 'we need a button to click on to do X.' You can however educate them on basic technical terms and concepts. Conversely it is not up to your stakeholders to define tasks for the developers; it is the project team's job to translate business needs into tasks. Prioritize & validate requirements: include a prioritization process as part of requirements gathering and definition, and get stakeholders to sign-off on requirements.

There are tools to support versioning of Excel and Word documents. For example, if you're a Microsoft-dependent shop, are you running SharePoint? It allows you to check in and check out documents for editing, and tracking changes. Otherwise, a simple version control system with locking will prevent people from stomping on each other. Changes to requirements documents should only be made by a few people and viewed by all, so it shouldn't be too much of a hassle. Honestly, I've looked for tools other than Word/Excel and haven't found anything good.–Aug 29 '11 at 12:52.

This is a tough question because I see lots of underlying questions/assumptions.Requirements management is huge and often over complicated. It is one of the main reasons for the huge focus on prioritization and user stories in the Agile methodologies and approaches, so that we keep teams and customers conversations focused. It seems to me you should give Google Docs a real try in this capacity.

It seems to address all your concerns in your first Edit section.With it's new issue-like comment system that integrates with email it can really help track the consensus process.I've actively contributed to documents with over 5 concurrent people editing and commenting and it seemed 'natural'.One thing I wish was better was search and navigation of the revision history but the raw rev tracking is good and hopefully they continue to improve it. I would suggest with the add-on. Easy for non-techies: Confluence has an easy, MS Word-style wysiwyg editor,. Unique number: Yes. If you link to a requirement, you can see an excerpt when you hover over it,.

Versionned: Yes for Confluence pages,. Search: Yes. Links: As you suggested, traceability matrix aren't human-ready, so it's just links,.

Export to ExcelHere's an example of inserting a link to a requirement key and showing an excerpt in view mode:Disclaimer: I'm the author of Requirement Yogi. I recommend taking a deeper look at with the plugin. If you need to document relatively extensive requirements or general documentation in the future, it integrates well with Atlassian's Confluence. When used appropriately with a workflow that everyone understands, this can be a very effective team of tools and it looks like they meet most of your requirements.As an admin user of JIRA, you can customize the interface, permissions, etc. There are a lot of options available on the default interface that could be confusing, but you can customize the interface and simplify it to the point where it's easily understood by your 'non-techies', but still has the robust features that are needed to meet your requirements.This was the system I had in place and it worked well for the context of our organization.

The biggest issue we had was applying a standard; everyone needs to understand the workflow (and actually follow it).