Quick Navigation
AGILE METHODOLOGIES#1
A set of principles for software development emphasizing flexibility, collaboration, and customer feedback.
TEST-DRIVEN DEVELOPMENT (TDD)#2
A software development process where tests are written before code, ensuring better alignment with requirements.
BEHAVIOR-DRIVEN DEVELOPMENT (BDD)#3
An Agile practice that encourages collaboration among stakeholders through shared understanding of requirements.
CONTINUOUS INTEGRATION (CI)#4
A practice that involves regularly integrating code changes into a shared repository to detect issues early.
CONTINUOUS DELIVERY (CD)#5
An extension of CI that ensures code is always in a deployable state, allowing for frequent releases.
USER STORIES#6
Short, simple descriptions of a feature from the perspective of the end user, guiding development and testing.
ACCEPTANCE CRITERIA#7
Conditions that a product must satisfy to be accepted by a stakeholder, guiding testing efforts.
RETROSPECTIVES#8
Regular meetings in Agile teams to reflect on past work and identify improvements for future iterations.
AGILE FRAMEWORKS#9
Structured approaches to implementing Agile methodologies, such as Scrum and Kanban.
SCRUM#10
An Agile framework that uses fixed-length iterations called sprints to deliver incremental improvements.
KANBAN#11
An Agile method focusing on visualizing work, limiting work in progress, and maximizing flow.
COLLABORATION#12
Working together across roles to achieve common goals, crucial in Agile environments.
FEEDBACK LOOPS#13
Processes that allow teams to receive and act on feedback quickly, enhancing product quality.
AGILE VALUES#14
Core beliefs guiding Agile practices, including individuals and interactions over processes and tools.
AGILE TEAMS#15
Cross-functional groups that work collaboratively to deliver value in Agile projects.
CROSS-FUNCTIONAL TEAMS#16
Teams composed of members with different skills and expertise, promoting collaboration and efficiency.
DOCUMENTING PROCESSES#17
Recording steps and outcomes in development practices, crucial for knowledge sharing and improvement.
INCREMENTAL DEVELOPMENT#18
A method where software is developed in small, manageable segments, allowing for gradual improvement.
TEST AUTOMATION#19
Using software tools to run tests automatically, enhancing efficiency and consistency in testing.
AGILE COACH#20
A mentor who guides teams in implementing Agile practices and improving collaboration.
QUALITY ASSURANCE (QA)#21
A systematic process to ensure that software meets specified requirements and standards.
SOFTWARE DEVELOPMENT LIFECYCLE (SDLC)#22
The process of planning, creating, testing, and deploying software.
VERSION CONTROL#23
A system that records changes to files or code, enabling collaboration and tracking of modifications.
SOLUTION ARCHITECTURE#24
The design and structure of a software solution, ensuring it meets technical and business requirements.
AGILE PRINCIPLES#25
Guidelines that underpin Agile methodologies, emphasizing customer collaboration and responsiveness to change.