Test Automation
The practice of using software to automate the testing process. Testing automation requires up-front planning and configuration of the testing software to ensure that the execution of the test meets...
View ArticleTest-driven Development (TDD)
More a technique than an actual development methodology, TDD is a practice that is commonly utilized in agile methods. TDD advocates the discipline of building working code by first designing and...
View ArticleUnit Test
A unit test is a test performed by the developer to verify and validate the code that the developer completed is fit for use. The unit test is often the first level of testing that is completed as a...
View ArticleUse Case
A use case is a document that attempts to describe system behavior from an end-user’s perspective. It outlines the flow of data, system behavioral interchanges and corresponding end-user interactions...
View ArticleUser Acceptance Tests
User acceptance tests describe the tests that must be successfully executed in order to validate that a specific piece of functionality meets the needs of the user as outlined in the customer...
View ArticleUser Roles
User roles are used to describe the unique perspectives of the different consumers that will interact with the working software. Much like actors in a use case, user roles should not just be limited to...
View ArticleUser Stories
User stories are simple, brief and concise statements that are used to describe customer software requirements from a particular user’s perspective. User stories are often used in agile methods for...
View ArticleVelocity
Used in combination with relative (story point) estimation, static teams and fixed time-boxed iterations, velocity is a predictive metric that is useful for long- and mid-term planning and estimation....
View ArticleVision
Vision is the first and highest level in the agile planning process. Activities often associated with this level of planning include the creation of project charters, feasibility studies, funding...
View ArticleWorking Software
Working software is used to describe the level of completeness that features developed during an iteration should achieve by its conclusion. Working software implies that the features demonstrated to...
View ArticleSprint Goals
Sprint goals are a high level summary of the business and technical goals that the team and product owner agree to accomplish in a sprint. In SAFe, Sprint goals are integral to the effective...
View ArticleStories
Stories are the Agile replacement for traditional forms of requirement specifications. Stories are small, independent behaviors that can be implemented incrementally, each of which provides value to...
View ArticleStrategic Themes
Strategic Themes are specific, itemized business objectives, new business differentiators that connect the portfolio vision to the evolving enterprise business strategy. They provide business context...
View ArticleSystem Architect
The System Architect has the responsibility for maintaining a high level understanding of the user’s needs, system requirements and business benefits for a Release Train. System Architects provide...
View ArticleSystem Demo
The System Demo occurs every two weeks and provides an aggregate _ and integrated _ view of a system increment, all the new software that has been delivered by all the teams in the program to that...
View ArticleSystem Team
A System Team is often responsible for providing assistance in building and utilizing the development environment infrastructure and evaluating the system increments. This can include development and...
View ArticleTeam Backlog
The Team Backlog represents the collection of all the things a team needs to do to advance their portion of the program solution. It can contain user and technical Stories, future Features, technical...
View ArticleTeam Demo
The Team Demo is the traditional, Scrum-prescribed ceremony where the team demonstrates the results of the work done in the iteration. The purpose of the Team Demo is to measure the team’s progress by...
View ArticleTeam PI Objectives
Team PI Objectives are a summarized description of the specific business and technical goals that a team intends to achieve in the upcoming PI. During release planning, each team reviews the vision and...
View ArticleUser Experience (UX)
While Agile Teams have the full responsibility for implementing the code, including the user interface (UI) elements, the User Experience designer works at the Program Level to provide cross-component...
View Article
