Agile - Alvin Vocabulary Flashcards
Agile
Iterative approach to deliver a project, which focuses on delivering in INCREMENTAL steps.
Agile Release Planning
Gives a high level overview and timeline of the software’s release schedule, based upon the established Product Roadmap.
BurnDOWN Chart
A visual chart which tracks the REMAINING WORK throughout the number of story points completed in an iteration, and is used ot analyze the team’s velocity and completion date for remaining work.
BurnUP Chart
Visual graph that shows the work that has already been completed to release the product.
Caves and Commons
A team’s workspace and common area that facilitates collaboration, colocation, and a quiet environment for th eteam to work in.
Continuous Integration
Frequently incorporating the work in to the entire whole and retesting the product to confirm that the product still functions as intended.
Cumulative Flow Diagram
A stacked area graph used to track your team’s work which is being completed on the project, and helps identify bottlenecks.
Daily Standup / Daily Scrum
Daily meeting facilitated by the scrum master to discuss
1. What did I do since the last standup
2. What is the plan fo rworkign on today
3. What impediments am I experiencing?
Flow Based Agile
Team pulls features from a backlog, based upon the team’s available capacity. Features become available as soon as they are ready instead of from a timebox schedule.
Iteration Based Agile
Team works in iterations to deliver completed features. Iterations are of equal durations.
Minimum Viable Product (MVP)
A product which has MINIMAL FEATURES, which allows the team to iterate quickly and obtain customer feedback as early as possible.
Mobbing
The team members work together and contribute towards completing a specific task. Drives increased focus and completing the work. Prevents hand offs and waste. Next level version of ‘swarming’
Pair Programming
One programmer writes the code, while another inspects the code (while it’s being written). Allows for any issues to be detected while code is being created.
Planning Poker
Estimation technique used during spring planning to estimate effort for a User Story. Uses playing cards with numbers written on them, based on the Fibonacci sequence (1, 2, 3, 5, 8…)
Product Backlog
List of all the work which needs to be completed to finish creating the product.
Product Backlog vs Sprint Backlog
Product Owner
Scrum team
Represents the Voice of the Customer on a project and is the one who understands the customer’s needs and requirements. Key responsibility is prioritizing the backlog.
Scrum Master
Person responsible for leading the team to implement the Scrum process. He or she should be fluent and knowledgable in what’s entailed with using Scrum. Acts as a servant leader to remove any roadblocks the team experiences.
Spike
Short time-boxed window to ‘experiment’ with technical options and gain more knowledge. For example, risk-based spikes (to investigate & remove an issue) or archtectural spikes (team writes enough code to explore the use of a new technology)
Sprint
Time-boxed period of 1-4 weeks in which the team finishes the work found within the Sprint Backlog.
Sprint Backlog
Scrum artifact that lists features to develop for the upcoming sprint. Consists of prioritized items pulled from the Product Backlog.
Sprint Planning Meeting
Scrum
Planning meeting used to determine which features will be performed in the upcoming sprint. This results in the development of a Sprint Backlog.
Sprint Retrospective
Meeting used to review the team’s performance and determine what went right, what went wrong, and to conduct a ‘lessons learned’. This is typically held at the end of every sprint.
*not use to provide customer or product owner feedback about the product increment - focused on improving the scrum process and team performance for future sprints.
** vs sprint review
Sprint Review
At the end of each sprint, the customer performs an inspection to review the product demo (also know as the product increment) which was developed during the sprint. Customer and Product Owner review to determine if it meets the user needs.
Story Point
Metric used to establish the level of effort and difficulty to fully develop a User Story. What is the amount of effort and difficulty with completing a task.
