incremental development
implementing the most important features first, then pushing updates to improve them or add other features later on
extreme programming
rapid incremental software development;
test-frirst development, refactoring, small releases, simple design
Kent Beck
coined Extreme Programming in 1998
test-driven development
writing tests first, then code;
clarifies what the code will actually do / return;
an automated unit test framework is used to run the tests after every change, and new code should not break old code
refactoring
improving the structure, readability, efficienty and security of a program;
reorganizing code to be more readable, cleaner, perform better;
optimization of code after a first/early version
scrum
a daily team meeting where progress is reviewed and goals for the day are discussed and agreed upon
potentially shippable product increment
output of a sprint which should be of high enough quality to be deployed for customer use
velocity
estimate of the amount of worok a team can do in a single sprint
backlog
a to-do list of items to be implemented
refinement
existing PBIs are analysed and refined to create more detailed PBIs
estimation
the team estimate the amount of work required to implement a PBI and add this assessment to each analysed PBI
creation
new items are added to the backlog; may be suggested by product manager,required feature changes…
prioritization
implement most important items first; product backlog items are reordered to take circumstances into account
agile software development
scrums/standups, sprints, small self-organized team (3-5 members), test-driven dev, feedback + refactoring
waterfall software development
gather requirements and slowly implement; no feedback or communication; long periods of developing the entire platform
scrum
meeting where priorities are discussed, progress is discussed and tasks are delegated to others
sprint
2-week period of implementing a backlog into a program
backlog
to-do list of items to be implemented, including bug fixes; if an item takes longer than a sprint, it is added to the backlog again for the next sprint
epic
a backlog item that is broken into smaller pieces for implementation, as a result of taking longer than a sprint to implement
technical debt
inefficient code that needs to be optimized
iron triangle
budgets/scope/time; project is made up of three things that all impact one another; in the same way a triangle’s angles always add up to 180º, changing budgets, scope or time will affect everything proportionally in return
unit testing
simple, fast tests to test individual pieces ocode
refactoring
cleaning up code, optimizing it
extreme programming
coined by Kent Beck in 1998; rapid incremental test-driven development with small releases
