Agile Terms or Phrases
Developers and testers work together to knowledge transfer
What is pairing or mobbing?
Lasts no longer than 15 minutes
Daily Stand-Up
The meet up happened on this date
September 28, 2022
This is written in Gherkin/BDD language (Given, When, Then).
Acceptance Criteria
After this is written, it must be checked, has unit test coverage of 80% minimum, peer reviewed, tested, and validated.
Code
Developers and testers work together to get work completed
What is Swarming?
Lasts no longer than 90 minutes once in every 2-week Sprint
Sprint Retrospective
This was a major interruption to our flow of meetings that day
Fire Drill
These two groups of team members have estimated the User Story and have committed to getting it 'Done' before a Sprint begins.
Developers & testers
All of these identified early in development through unit testing and peer review must be fixed.
Bugs
Developers hate that this builds up as they expedite code development
Technical debt
Lasts no longer than 90 minutes every week.
Backlog Refinement
The meet up happened in this room
Skype Room
They have identified test scenarios for the User Story i.e., what will be tested
Testers
This team member has executed static analysis rules and there are no static analysis violations.
Developer
Team members do this when they are not 100% dedicated on one team
Task/Context Switching
Lasts no longer than 2 hours once every 2-week Sprint
Sprint Review
These two people were pictured in a photo shared at 0857 hours in the Pod's MS Team's chat that morning
Steven Lecky & Shereeka
These two things are captured in the Description
Risks & assumptions
If these exist within a User Story they must also be closed/completed/resolved/done by the end of each Sprint.
Sub-Tasks
Developer or tester or other team member has deep expertise in one area of specialty, then some abilities in another area of specialty
T-Shaped Person
Lasts no longer than 4 hours once every 2-week Sprint
Sprint Planning
Food court got this many votes to be the team's choice for source of lunch
Seven (7) votes
If this is complex or confidence is low that it won't become a threat, the User Story should not be accepted into the upcoming Sprint as a User Story.
Dependency
This must be complete in Jira, Confluence, etc.
Required documentation