An activity whereby the product owner or customer accepts the validity of a feature based on its adherence to the defined acceptance criteria.
The criteria which defines the functionality, behavior, and performance required by the feature for it to be accepted by the product owner or customer.
A method of test-driven development (TDD) that involves writing an executable test before the solution code. These tests are typically developed in conjunction with the product owner or customer and are conducted to determine whether a feature satisfies its acceptance criteria.
Formal tests developed by the customer, product manager, or their testing proxy that are conducted to determine whether a system satisfies its acceptance criteria.
The release that has a state value of Active and whose release date is the earliest date.
Someone or something that interacts with the system.
The actual completion date of a portfolio item when all user stories linked to the portfolio item have reached the Accepted schedule state.
A calendar date that reports when development teams actually started work on a portfolio item (when the first user story linked to the portfolio item has reached the In-Progress schedule state).
The origin of agile development methodologies. Crafted in 2001 by several software developers, the manifesto stresses the importance of individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan.
The collaborative team comprised of the product owner, the scrum master, and the delivery team.
An app allows for the combination of data from more than one source into a single integrated page within CA Agile Central. CA Agile Central allows you to use your own custom app code and provides a catalog of managed apps.
Associations are relationships that assist in managing software development work items. For example, a technical problem found while developing new code can be documented as a defect associated to a user story.
Synonymous with field. An attribute represents a named property of a work item. An attribute has a type that defines the entry of its instances, such as drop-down lists, text fields, and boolean.
Information assigned to an attribute. For example, the State attribute could be assigned a value of Committed, Completed, Approved, and so on.
The process of verifying a person's identity. Your username and password are authenticated when logging in.
A collection of prioritized requests for work to be done.
An ongoing process whereby the product owner or customer manages the product backlog based on information gathered in the feedback cycles inherent to agile practices. The activities of backlog refinement can include: adjusting rank; breaking down stories that are going to be worked on in the next few iterations; creating new stories; updating existing stories; deleting obsolete stories; elaborating acceptance criteria.
The practice of testing new software features manually to uncover defects that automated testing may not find. CA Agile Central development, quality, and support teams hold collaborative bug bashes prior to each release.
An operational version of a system or part of a system that identifies a subset of the capabilities to be provided in the final product.
A type of chart that shows work remaining over time. Burndown is a compound word, the correct spelling, and industry standard. Burn down refers to arson.
Amount of work a team can complete in a given time period.
Matches business demand with available supply, so you can optimize your agile teams’ capacity towards the highest business value within their capacity. Facilitates the events leading up to big room planning.
A card is an object on a board, such as the Kanban Board app. Cards can represent work items such as user stories, portfolio items, tasks, and defects.
Textual information that specifies the justification or reasoning behind the changes associated with a given revision of a work item.
A term to describe a member of a scrum team or daily standup meeting that does not have an active stake in the work. Taken from the fable of the chicken and pig, a chicken is only involved, but a pig is committed. See skin-in-the-game.
A user story that represents the breakdown of a large feature or initiative into a smaller segment. Only the lowest-level child story in a user story hierarchy can be scheduled into an iteration or release.
A systematic examination of computer source code intended to find and fix mistakes overlooked in the initial development phase, improving both the overall quality of software and the developers' skills.
A type of software methodology that allows new code to be released as soon as it is finished, instead of holding to a defined release schedule. See also Lean.
A software development practice where members of a team integrate their work frequently. Typically, developers integrate their code into the code base at least daily.
A team composed of people with varied levels of skills and experience brought together to achieve a shared goal. Agile teams should be cross-functional.
The iteration that contains today's date, the earliest start date, and the earliest end date.
A user-defined work item field. Custom fields may be created on most CA Agile Central work items.
A user-generated page that displays in CA Agile Central. Custom pages may contain a CA Agile Central catalog app, a custom app built by a user, a dashboard page, or the contents of another webpage. Custom pages may be installed by a single user or shared with all users of a workspace.
A person or organization, internal or external to the producing organization, who takes financial responsibility for the system. In a large system this may not be the end user. The customer is the ultimate recipient of the developed product and its work items. See also stakeholder.
A tool used to prioritize backlogs, determine teams, and see capacity for releases.
A brief meeting held between the delivery team, product owner, and scrum master. While everyone stands (to keep the meeting from running long) each team member reports on what work they did yesterday, what they plan to do today, and alerts the scrum master of any issues that may be blocking them.
A CA Agile Central page located under the My Home page. Panels on the dashboard display various information and charts. Users can control what panels display and how they appear. You can create multiple dashboards as custom pages.
A defect (also called bug or software bug) is an error, flaw, mistake, failure, or fault in a computer program that prevents it from behaving as intended (such as producing an incorrect result).
A grouping mechanism that allows you to compile and schedule a collection of defects as a single unit for resolution in an assigned iteration or release.
A living definition created and managed by the delivery team, defining their current standards for technical excellence. The definition typically includes the requirements the team has to meet in order to declare any work item worked on in an iteration done. These differ from acceptance criteria in that they are typically technical in nature and generalized to be valid for most work items (such as unit tests complete, online help updated), as opposed to value-driven criteria specific to a feature (such as website users should only be able to create one account per email address).
A relationship between two modeling element work items, in which a change to one work item will affect the other work item.
A method for ranking work items when you click the work item and drag it to a desired prioritized position on the page.
Synonymous with parent story.
An improvement or capability of value to a stakeholder that can be developed in a PSI or release timebox (usually 10-12 weeks).
A description of a feature or function that does not currently exist in the software, requested by a customer or other stakeholder. Feature requests may be captured using CA Agile Central Idea Manager and converted into user stories when ready for prioritization and development.
Synonymous with attribute. Fields represent a named property of a work item. A field has a type that defines the entry of its instances, such as drop-down lists, text fields, and boolean.
A process by which you can change the amount of information displayed in a view. You can filter by specifying certain distinct criteria for any or all attributes. For example, instead of displaying all work items, you might apply a filter to display only work items having a high priority.
A description of how to work with a particular work item, including how to create and revise the work item. Guidance (guidelines) may include techniques, procedures, standards, tips, templates of work items, examples of work items, definitions, and so on.
An event in a scrum team where individual members are allowed to create their own code, features, or other materials of their choosing. Hackathon work should be fun, but also relate to the system in some way. A hackathon generally lasts an entire iteration, and is built into a release schedule.
A collection of related work items. CA Agile Central provides several hierarchies: a project hierarchy, a user story hierarchy, and a portfolio item hierarchy (when using CA Agile Central Portfolio Manager). The project hierarchy is intended to model your organizational structure (how product teams and delivery teams are organized in your company). The user story hierarchy helps agile teams organize their work in smaller batches of work. The portfolio item hierarchy helps product teams organize their strategic plans into large initiatives, and smaller features. The portfolio item hierarchy is linked to the user story hierarchy to provide a full strategy-to-execution view.
An object in CA Agile Central Idea Manager used to represent a feature or function requested by a customer or stakeholder.
An estimation unit that considers the time it would take to complete a task without interruptions.
The changing condition of the software product as it is developed, and is expressed in terms of repeated iterations or milestones with specific start and end points.
A type of iterative development strategy in which more and more functionality is added to an iteration of the system being built.
See loop, infinite.
The largest portfolio item in a project hierarchy. Initiatives are split into large blocks of work that will be spread out over multiple teams.
A report used to benchmark data and get detailed, diagnostic analytics to help understand and improve software development performance.
A budget or investment area that a portfolio item supports. Define a list of investment categories possible for a portfolio item. Each portfolio item can be associated with one investment category.
A theme-driven timebox of requests to be worked on and accepted within a release of a product; it is defined in an iteration planning meeting and is completed with an iteration demo and review meeting. The terms iteration and sprint are used synonymously.
An app that displays work delivered so far in an iteration to proactively anticipate whether the iteration scope will be delivered.
A plan to achieve a specified level of functionality and meet additional specific criteria with a particular iteration of a system.
Provides your team with a view of all work items within an iteration organized by scheduled state.
The estimated amount of resources for an iteration.
A system of tracking work across various stages of development. Work is represented by cards, and stages are represented by columns on a board. A card is moved to the next column when it enters the next stage.
Refers to any user story that has no children.
Software development practices adapted from the Lean Manufacturing principles developed by Toyota. The focus of Lean methodology is to eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible, build integrity, empower the team, and see the whole. You may practice Lean in CA Agile Central by using the Kanban Board and Portfolio Kanban Board apps.
See infinite loop.
The target dates for events that are important to the business. Setting these dates is beneficial to program, product, project, and development managers, as well as product owners and engineering directors to track critical dates.
Modules are sets of advanced features included with the Unlimited Edition of CA Agile Central. Specific modules may be purchased for Enterprise Edition subscriptions. Time tracking, product, and portfolio management, advanced test management, and advanced security are some of the features provided by modules.
An acronym used to prioritize work, or aspects of a particular feature. Stands for must have, should have, can have, and won't have. May be used to define the acceptance criteria of a user story.
The user responsible for accepting a work item.
A general purpose mechanism for collecting and organizing work products into groups. Package is an available field in CA Agile Central, but it is recommended that tags be used instead.
A location in CA Agile Central under any of the main navigation pages, that provides summary views of work item data. You can also create custom pages under CA Agile Central tabs. Custom pages are used to host one or many apps and can be copied, shared, and customized.
A rank order based on the page position of a work item on a particular summary view.
A user story that represents a large feature or set of work, which is further defined by related child stories. Parent stories cannot be scheduled into an iteration or release, as they are considered too large. Synonymous with epic story.
Acronym used by IT professionals to describe a common source of errors. It stands for Problem Exists Between Chair and Keyboard.
Specific user rights for workspaces and projects. Controls abilities to administer, create, edit, and delete CA Agile Central subscription data and settings.
A term to describe a member of a scrum team or daily standup meeting that does have an active stake in the work. Taken from the fable of the chicken and pig, a pig is committed, but a chicken is only involved. See skin-in-the-game.
The amount of effort estimated to complete a single user story. Plan estimates are represented by points, t-shirt sizes, or other systems. They do not correspond to task or man hours.
An estimating technique that uses an agreed-upon unit (typically story points or ideal days) to estimate the relative size of a feature. This estimating is typically done to assist with release planning and to allow the team to determine its velocity.
A calendar date to express the intended date when a portfolio item will be completed.
A calendar date to express the intended start date of a portfolio item.
The total number of story points (or other unit type) the team estimates they can complete within an iteration or release. This value is also known as available resources. This total can be estimated by averaging the total number of story points successfully completed in past iterations or releases.
An approach to estimating the size of work among a scrum team. Team members are given cards, each with a point value. An example of point values is 0, 2, 5, 10, 20, 40, 100. The potential new work is presented to the team, and each member holds up a card with their estimated point value. The largest and smallest point value holders explain their position, and then the process is repeated until a consensus is reached.
The most common units used by agile teams to estimate relative size of stories or portfolio items such as features and initiatives.
A CA Agile Central work item type used to capture high-level features and initiatives. A top-level portfolio item may consist of several smaller portfolio items, each of which consist of several user stories. Available with the CA Agile Central Portfolio Manager product.
An app that helps you track the status of your portfolio items as they move along in your portfolio process.
An app that allows you to visualize how portfolio items are progressing over varying time intervals.
Any user story that must be completed before another user story can start or finish.
An estimating technique that uses an agreed upon unit (for example, S, M, L) to estimate the relative size of a portfolio item (initiative or feature). This estimating is typically done to provide the product or portfolio manager with a high-level effort estimate for the initial prioritization of strategic items. We recommend you use relative sizes (S, M, L) over numeric values.
A prioritized list of functional and non-functional requirements for a system or product. A product backlog may be created and prioritized on the Backlog page, under the Plan menu in CA Agile Central.
Can be user stories, technical features, defects or any other item that will require the time of the delivery team to deliver the feature. They are typically estimated at the gross or plan level.
A role on an agile delivery team that is responsible for collecting and ranking business requirements on the product backlog. A product owner does not manage a delivery team, but communicates what must be built in the next release or iteration. In exchange for the team's commitment to finish the top-most ranked work in an iteration, the product owner agrees to protect the team from any changes in requirements during the iteration.
A collection of work, usually software projects, performed by a number of teams to deliver marketable value to the company or to external stakeholders.
A container for a set of releases and iterations, and their related user stories and tasks. In CA Agile Central, it is helpful to think of projects as work areas for teams. When using CA Agile Central Portfolio Manager, projects represent either work areas for portfolio and product managers or work areas for teams.
A pull-down menu found in the upper-left corner of any CA Agile Central page. Used to select what project and related child or parent projects data is pulled from for display on the page. See also scope.
Potentially Shippable Increment. A timebox, usually 10 weeks, in which a PSI of features is developed.
An attribute of a work item that describes its importance for a release or iteration.
Any change to software code that improves its readability or simplifies its structure without changing its results.
A timebox where work occurs in support of an internal or external delivery of a working, tested version of the system or software. In scrum, a release consists of multiple iterations to deliver new system code.
A Release Announcement specifies the list of cases whose respective Salesforce contact will be alerted over email when the release announcement notification is sent.
Contains all stories that have been scheduled for a particular release, but not a particular iteration.
A commitment to a plan for delivering an increment of product value. It is a collaborative effort involving scrum masters, product owners, delivery teams, and stakeholders.
The estimated amount of resources for a release.
A generated description of one or several work items, or work item attributes. The report can describe the detail of an individual work item or a summary listing of like work items.
A software capability that must be met or possessed by the system or a system component to satisfy a contract, standard, specification, or other formally imposed documentation that takes the form of a declaration. User stories and portfolio items are types of requirements.
A term used in describing the outcome of a test case.
A change made to a work item, user, or workspace settings. Revision histories are provided on these objects to show a log of changes.
The number identifying a revision. Revision numbers are automatically incremented for each change made to a work item.
The level of impact on the successful outcome of a work item.
A relative number to express the level of risk for a portfolio item.
A high-level or long-range estimation of work to be completed by an organization. Roadmaps may be created for internal planning or external communication to stakeholders. In agile organizations, roadmaps are subject to change with evolving business priorities or needs. CA Agile Central Portfolio Manager provides capabilities for planning feature roadmaps with development cadences of usually 10-12 weeks.
The updating of status and progress from a lower-level work item or project in CA Agile Central up through the hierarchy. For example, release work can be rolled up among several projects in a common hierarchy, when the releases in each project share the same name and dates. Schedule state updates also roll up from tasks to user stories.
RSS (Really Simply Syndication) is a lightweight XML format designed for sharing web content.
An acronym for Scaled Agile Framework. A methodology created by Dean Leffingwell to implement Lean and Agile practices on an enterprise scale.
Also known as SAFe. A methodology created by Dean Leffingwell to implement Lean and Agile practices on an enterprise scale. Use this proven methodology to scale agile from the team level to the enterprise level.
A standard field in CA Agile Central with values of Defined, In-Progress, Completed, and Accepted. User stories, defects, and defect suites use this field to indicate progress and track performance. Not to be confused with State, which can have different values depending on the type of work item.
A time-ordered collection of activities that specify when important project events or milestones are planned to occur.
The primary project that you have designated as your focus within the current workspace, as well as related parent and child projects that you have included in focus. See project picker.
The setup object is used to configure your connection to CA Agile Central, and to specify mapping preferences between Salesforce cases and CA Agile Central defects and stories. It is also where the Salesforce administrator can update all cases with their respective CA Agile Central development status at once.
A pane on the left side of CA Agile Central detail pages that organizes related work items links and makes them easy to access.
A term that represents an individual's commitment to a team or project. For example, if a pig and a chicken decide to open a ham-and-eggs restaurant, the chicken is merely involved while the pig is committed; it has skin-in-the-game.
Synonymous with iteration.
An individual who is materially affected by the outcome of work done in an iteration, release, or user story.
A condition during the life of a work item where it satisfies given criteria. Examples include defined, in-progress, completed, open, closed, released, and so on.
An agreement to give a set of named users access to use the CA Agile Central service.
Has administrator privileges for the subscription and as such can add and set user permissions, create workspaces and projects, and configure default workspace settings.
Any user story that cannot start or finish until another user story is completed.
Describe behavioral and non-behavioral requirements of the system such as functional requirements, non-functional requirements, and design constraints.
Horizontal rows that can be applied to a board for a team to easily visualize work items by category or sub-process.
A main navigation heading in CA Agile Central. Each tab contains several pages, which display various data. CA Agile Central tabs are My Home, Plan, Track, Quality, Portfolio Items, and Reports.
A unique identifier that may be applied to a work item to indicate category or class. You may use tags as a filter to find specific sets of work items on summary pages.
A unit of work that, when performed, contributes to the fulfillment and completion of a scheduled user story within the iteration. Tasks allow decomposition of stories into manageable units of work. Team members can take responsibility and ownership for each task, providing estimates and work left to do for completion.
An app that provides you with a way to view and update tasks during your daily standup meetings.
The amount of effort estimated to complete a single task. Generally recorded in hours, but does not directly correlate to user story estimates.
A set of known behaviors associated with a feature or requirement that define acceptance of work associated with the work item. A test case also captures test results.
A test case field that informs the user of the actions that must be taken to perform the test.
A container for related tests that make up a suite, set, or initiative in your system.
A textual description of what is being tested by the test case.
A page in CA Agile Central that allows you to organize your tests into functional areas representing the structure of your system or other organizations.
An executable display of a single or collection of test cases, including their steps.
A tool for managing regression testing by allowing a collection of test cases to be run together in a single instance. Available with the CA Agile Central Quality Manager product.
Test-Driven Development (TDD) involves writing new test cases covering the desired improvement or new functionality first, then the code necessary to pass the tests is implemented, and finally the software is refactored to accommodate changes.
A fixed period of time in which development is done for a deliverable. In addition to fixing the start and end points of timeboxes, teams typically also fix the resources available within the timebox.
A calendar view of the portfolio schedule, showing planned dates and actual dates. Available as a page under the Track page, or an app.
The amount of remaining effort required to complete a task. Generally recorded in hours.
A description that provides guidance on how to perform activities or steps in using a specific work item.
A method by which the developers write testing code to test their target code at the module (class, object, and interface) level. Developers have access to the internals of the object, method, or interface that is being tested. They use a set of open-source and commercial method frameworks to facilitate development, management, and execution of unit tests.
Represents a login for a person or role within a CA Agile Central subscription that can take on specific access privileges.
A listing of acceptance criteria needed to deliver a new feature or piece of work. Generally written from the perspective of a user of the system. A commonly used format is: As a X, I want to Y, so that Z.
A validation action evaluates the status of the execution of a test case. Typical validation criteria includes pass, fail, build tested, and date tested.
A number that indicates the worth of the portfolio item.
Variations express how the action or task being executed can be done in a different way. Examples are technical or data variations.
A measure of the amount of accepted work delivered within a timebox. Agile teams typically use the sum of story points associated to accepted user stories delivered in an iteration as their velocity calculation.
Test case results yield verdicts. Predefined verdict values may include pass, fail, inconclusive, and error, and can be user-defined.
The ability to follow the status of an individual work item and receive notifications when changes are made. Watches can be used when you have a critical portfolio item, user story, defect, or task and need immediate notification when its details are changed.
A form of software development that agile seeks to change. In waterfall environments, work may not begin on a feature until it meets several requirements first, stalling development. Waterfall projects typically take 2-3 times longer to complete than agile projects.
A mechanism that creates a rule that sends information to an external server when the rule triggers. The destination of the information is defined in the webhook rule where it was created.
Items which help define the project, or team objective. Work items in CA Agile Central are user stories, tasks, portfolio items, test cases, test sets, test case results, defects, and defect suites.
An organizational construct within a CA Agile Central subscription representing independent departments that contains work items, projects, and settings. Data cannot span from one workspace to another. CA Agile Central strongly recommends you limit the number of workspaces you create.
A user in CA Agile Central with permissions to manage a workspace, including adding users, teams, projects, and programs. Workspace administrators are delegated by subscription administrators.
The single time zone used in a subscription, which allows for consistency among distributed teams. Dates display as a fixed point in time, not a calendar date. The workspace time zone is set by the subscription administrator.