The (.....) is responsible for quality in Agile projects.
XP teams use (.....) time to pay down (.....) by refactoring code or do research.
A cross-functional team in XP releases (.....) frequently.
Agile projects have short iterations; thus, project team receives (.....) and (.....) feedback on product quality throughout SDLC.
The general objective of (.....) is to visualize and optimize the flow of work within a value- added chain.
One programmer plays (.....) role and focuses on clean code, and compiles and runs. Second one plays role of (.....) and focuses on the big picture and reviews code for improvement or refactoring.
There are 2 levels of plans in XP: (.....) and (.....) In both levels, there are 3 steps: (.....)
User stories must address (.....) and (.....) characteristics. Each story includes (.....) for these characteristics used to decide when a task is (.....)
All team members, testers and non-testers, can (.....) on both testing and non-testing activities.
(whole team)
(slack time - technical debats)
(Minimum Viable Product (MVP))
(early - continuous)
(kanban)
(pilot - navigator)
(release planning - iteration planning - exploration, commitment, and steering)
the team and stakeholders collaboratively decide what are the requirements and features that can be delivered into production and when.
the team will pick up the most valuable items from the list and break them down into tasks then estimates and a commitment to delivering at the end of the iteration.
a naming conversion practice used in design and code to have a shared understanding between teams.
management approach used in situations where work arrives in an unpredictable fashion.
The value chain to be managed is visualized by a Kanban board. Each column shows a station. The items to be produced or tasks to be processed are symbolized by tickets.
The amount of parallel active tasks is strictly limited. This is controlled by the maximum number of tickets allowed for a station and/or globally for the board.
is the time between a request being made and a task being released.
is calculating the actual work-in-progress time.
is the agile form of requirements specifications explain how the system should behave with respect to a single, coherent feature or function.
Larger collections of related features, or a collection of sub-features that make up a single complex feature.
Collaborative authorship of the user story can use techniques such as brainstorming and mind mapping.
is a meeting held at the end of each iteration to discuss what was successful, what could be improved, and how to incorporate the improvements and retain the successes in future iterations.
XP teams conduct a small test or proof of concept workout
