Agility Features

Use Agility to track all aspects of the entire software development life cycle. From gathering requirements at the start of the project to tracking bugs at the tail end and aspects in between.

Agility is based on what we call a Case. By default a Case may be a Requirements, Tasks, Issues, Bugs. But the true power of Agility comes in when you want to extend this list and add a Test Case for example.

All you tracking needs are centralized into one powerful dashboard. From the Agility dashboard you can view statistics, view search results and even update and manage Cases. Additionally, you can view and edit your Cases directly from the dashboard.

Gone are the days of navigating back and forth to and from an edit screen to make changes. With Agility you can make you changes directly from your search results.

With Agility, changes to your Cases get instantly reflected in your results windows using an advanced technology called AJAX.

The design of Agility pays careful attention to ensuring that its intuitive to all users. This is accomplished by having a simple and constant look and feel.

Cases within Agility can be defined in a parent-child hierarchy. This allows you to assign a Bug to a particular Requirement, or perhaps an Issue to a Requirement. Then at the end of the day, you can see what bugs or issues are effecting what end user Requirements.

Hierarchical grouping also allows you to break down complex tasks or bugs into smaller more manageable pieces.

Since agility is web based anybody with access to the Internet can access Agility. Additionally the Email Notification component notifies team members when items are assigned to them or items they are interested in get changed. Of course like all Agility features the Email Notification is completely customizable to your needs.

Agility keeps a history log of all changes to items. This allows you to track what changed and when. Additionally you can generate Change Reports to show a list of items that have changed within a given period of time. This is useful for tracking and managing scope creep.

Agility can support all the needs of your Enterprise no matter how many users or Cases are involved. Agility is built with the Enterprise in mind based on Open Standards and J2EE technology. This allows Agility to grow with the needs of your business.

Cases can be linked to each other in any number of ways. You can link a Case as a 'Duplicate' of another Case. Once a link is created you can jump between the two Cases quickly.

Having a database of all your software items does you no good if you can not search on it. Agility supports searching by attribute as well as full text searching. This allows you to search on Open items that have the word 'Excel Worksheet' in the title for example.

Once you have defined your search, you can save it as either private to you, or global to all members of your team.

Any item in Agility can have files attached to it. This allows you quickly attach relevant documents (such as screenshots, architecture documents) to an item.

Cases can be linked to each other to identify duplicates. This helps to clarify and simplify your tracking. If for example, you have a complex UI design created in Visio, you can upload the Visio as an attachment to a Case.

Agility is designed to support multiple Projects in a single installation. You can leverage you investment by tracking many Projects in one instance. This helps keep you long term cost down.

Your project administrator can choose who belongs on your Agility team and what resources these team members have access to. Additionally since the security model is role based, it is quick an easy to make changes. For example, you might want to give read only access to all your end-users.

The administrator can extend the list of knows Case Types. The administrator can for example create a new Case Type called Test Case that the QA team would use to define what a specific testing scenario looks like. The admin can then go in and add specific custom attributes to this new Case Type. For example, the admin might choose to add a custom field to the Test Case called Steps. This field would be a text field where the tester could enter the steps required to produce the Test Case.

The type of the fields that can be added: drop down, text, and number. There is no limit to the number of new fields a Case Type can have.