Glossary

    A
  • A test defined by the developer or customer to verify that the application as delivered meets the conditions of a user story.
  • In Sprint Closure, a specific activity that is called for at the end of a sprint. Action items can be generated automatically from the sprint retrospective, and can be converted in turn to user stories that are added to the backlog.
  • The total number of hours invested and remaining for all tasks in a backlog item.
  • The ALI Dev Bridge is a simple mini-web application that connects Agile Manager hosted in a SaaS environment to Source Code Management systems and Build Management systems hosted in your local development environment.
  • One of the components being developed in the framework of your project. An application is defined by the features you assign to it.
  • An application or program you develop, and integrate with Agile Manager over the Agile Manager API. Register your application in the configuration area to create client credentials used when authenticating your API over OAuth.
  • Backlog items removed from the product backlog. Adminstrators can archive themes and features, or remove items from the archive. Archiving an item also archives any related child items.
  • B
  • A list of work items planned to be handled during a specific stage of the product development life cycle. Can refer to the product, release, or sprint backlog.
  • A work item that is listed in the product, release, or sprint backlog. A backlog item can be either a user story or defect.
  • A process to produce the key deliverables of software development.
  • A Build Agent is a set of scripts or proprietary applications installed on a Build Server configured for listening on a Build System. When appropriate, changes on the Build Server are pushed to ALI.
  • A build configuration specifies how and with what tools the build is to be built.
  • A computer used to create a build. The server automatically runs the unit tests periodically or even after every commit and reports the results to the developers.
  • C
  • An ID created for a client application that you wish to integrate with Agile Manager via the Agile Manager API. Clients are assigned to specific workspaces and roles, similar to Agile Manager users.
  • A password for a specific client, created for an application you wish to integrate with Agile Manager. Record your client secret securely, because it is like a password, and once generated, cannot be retrieved again. If you need to, generate a new secret to replace your current secret.
  • ALI metric that measures the number of defects closed in a build.
  • Any change made to the code that was committed to the SCM repository. ALI metrics count the number of lines of code changed in a build. Code changes are often grouped by their association with user stories, defects, or neither.
  • ALI metric that measures the percentage of code in a build that is covered by unit tests.
  • A developer who committed code changes.
  • Fields defined by administrators in the configuration area. Custom fields are created at the site and workspace level, and can apply to user stories, defects, all backlog items (user stories and defects), themes, or features.
  • A sub-division of ALM releases. In ALM, requirements and defects can be assigned to cycles within a release. When synchronizing releases, ALM cycles are matched with Agile Manager sprints.
  • Verify whether the updates detected in synchronized records were made in fields specifically mapped for the selected link. If the changes were made in fields that are not mapped, the record is not synchronized.
  • D
  • A fault or bug detected in the application under development. Defects are included in the product backlog as backlog items along with user stories. Defects can be linked to user stories, and can be associated with features.
  • ALI metric that measures the number of defects detected in a build.
  • When synchronizing data between Agile Manager and ALM: The endpoint whose data is used in cases of conflict, where the same entities were modified both on Agile Manager and on ALM.
  • E
  • An instance of ALM or Agile Manager connected that is synchronized with another endpoint using ALM Synchronizer. ALM endpoints can only connect to Agile Manager endpoints, and Agile Manager endpoints can only connect to ALM endpoints.
  • The type of data synchronzied in a Synchronizer link. Entity types include releases, requirements/user stories, and defects.
  • A link between two entities in Agile Manager or ALM, such as a link between a requirement and a defect.
  • F
  • A functional area in an application. Several features can be grouped together under a theme. A feature is fulfilled by the user stories associated with it.
  • Teams created and used only in the scope of a single release.
  • A full comparison and update of the records in each endpoint, including deleted records.
  • G
  • After you break a user story it is converted to a group story. The group story contains the parts that you define when breaking the original story. To view group stories, on the Product Backlog > Backlog page, select the Group Stories View.
  • I
  • Unique IDs that are stored in a mapping table for records in each endpoint. This mapping table records the correspondence between each pair of records.
  • Synchronizes data between two endpoints for records that were created or modified since the last synchronization task.
  • The platform that enables two-way communication between Agile Manager and on-premises applications located behind firewalls, such as ALM.
  • A Windows service or linux daemon that makes sure the Integration Bridge is automatically started when you system starts.
  • K
  • Thousand Lines Of Code. Used to measure the amount of effort used in the item being measured.
  • L
  • The Synchronizer link endpoint to which data is synchronized. Data in the destination endpoint is updated according to the data in the source endpoint and the mapping's settings.
  • The Synchronizer link endpoint from which data is synchronized. Data in the source endpoint for the mapping remains unchanged
  • P
  • The total number of hours estimated for all tasks in a backlog item.
  • R
  • A group of changes to the application that will be available for distribution at the same time. You can assign user stories and defects to the release.
  • Each user in the project is assigned a role. The role defines the user's read/write permissions in different areas of Agile Manager.
  • S
  • Source Code Management is the management of changes to documents, computer programs, large web sites, and other collections of information.
  • An SCM agent is a set of scripts or proprietary applications installed on a SCM server configured for listening on a SCM system. When appropriate, changes on the SCM server are pushed to AGM.
  • A set of files under version control may be branched or forked at a point in time so that, from that time forward, two copies of those files may develop at different speeds or in different ways independently of each other.
  • A database used to enable the collaborative development of large projects by multiple engineers.
  • A time period, measured in days or weeks, in which teams work on a set of backlog items planned to that sprint and team.
  • 1. The number of hours a team member is available to work in a sprint. The sprint capacity is based on the team member's daily work hours multiplied by the number of his/her work days in the sprint. 2. The sum of all team velocities, in story points, of teams participating in a sprint.
  • A method for estimating the size of a user story or defect. Story points compare one story to another to determine a relative size and then assign points denoting that size. A team's estimated sprint velocity is then used to estimate how many story points the team can deliver in a sprint.
  • Connects an ALM endpoint and an Agile Manager endpoint and synchronizes data between them.
  • T
  • One of the work items that should be carried out in order to implement a user story or defect. A user story or defect is considered done when all its tasks are completed.
  • A group of people that work together on a sprint. Teams are defined at the release level. A team can include members from different departments (such as development, QA and technical writers) who work together on the same backlog items. The amount of work a team can deliver in a sprint is estimated in story points.
  • A user that is assigned to a team. A user can be a member on a number teams simultaneously. This can represent a shared resource that contributes to several teams, such as a technical writer.
  • ALI metric that measures the success rate of unit tests run on a build.
  • A top-level objective or a high-level functional area that is fulfilled by the features associated with it. A theme may span several applications.
  • Data available for retrieval from Agile Manager through the API. Time sheet data includes changes made to the Invested (hours) field for each assigned task, for specified users, and within a specific time frame.
  • U
  • A basic action that a user should be able to carry out in the application. User stories are added to the product backlog and estimated in story points. User stories are typically written using the following format: 'As a <role>, I want <goal/desire>'.
  • V
  • The number of story points a team is estimated to complete or has completed in a sprint. The estimated team velocity is used as a basis to calculate the total sprint or release capacity.
  • W
  • A graph or mini application that can be displayed in a dashboard. Widgets are available from the Widget Gallery.
  • ALI metric that measures the number of defects worked on in a build.
  • A top-level layer of data visiblity that enables you to apply scaled agile methodology in an enterprise organization. Users must be assigned to specific workspaces, and can view and access only data within the assigned workspaces.
  • Teams created at the workspace level, and reused in multiple releases.