Agile Development Flashcards
1
Q
What is Scrum?
A
- an agile way to manage a project
- details of how things are done on a project are left to teams, because the team knows best how to approach them
- relies on a self-organizing, cross-functional team
- takes a project from concept to completion
- also has a ScrumMaster and Product Owner
2
Q
Cross-Functional
A
- a cross-functional team has all of the necessary disciplines to take a projec from concept to completion
3
Q
Self-Organizing
A
- a self-organizing team has no specific leader
- team members determine roles and responsibilities
- the team determines the best way to accomplish goals
4
Q
Product Owner
A
- the key stakeholder for a project
- creates and maintains the compelling vision for the project
- represents business, customers and users
- prioritizes and updates the backlog to make sure the project stays on course
- guides the team towards building the right product
- DOES NOT tell the team exactly what to work on; the team picks the items they feel they can take on
5
Q
ScrumMaster
A
- coach for the Scrum team
- helps the team perform at the highest level
- does not provide day-to-day direction or assign tasks
- shelters the team from outside distractions, allowing for complete concentration
6
Q
What’s involved in the Scrum model?
A
- timeboxed sprints confined to 2-4 weeks
- the team takes a small set of features from idea to coded and tested functionality
- at the end all features are done: coded, tested, and integrated into the product or system, at potentially shippable quality
- has a daily Scrum meeting on each day of the sprint
- a sprint retrospective at the end of each sprint
7
Q
Timeboxing
A
- setting a specific time frame to complete a specific goal
- example
- paper design: 2 days
- art pass: 3 days
- design tuning: 1 day
- art polish: 1 day
8
Q
Sprint Backlog
A
- a list of tasks to be performed during the sprint
- based on a user story in the product backlog
- created during the sprint planningmeeting on the first day of a sprint
9
Q
Daily Scrum
A
- meeting each day of the sprint
- involves the team, ScrumMaster, and Product Owner
10
Q
Sprint Retrospective
A
- meeting at the end of each sprint involving the team, product owner, and ScrumMaster
- the team reflects on the sprint and identifies areas to improve
11
Q
Scrum Product Backlog
A
- complete list of functionality that remains to be added to the product
- the product owner prioritizes this functionality
- is populated by user stories
- can grow and change over the course of a project
12
Q
User Stories
A
- short descriptions of functionality, described from the perspective of a user or customer
- Ex: “As a shopper, I can review the items in my shopping cart before checking out so that I can see what I’ve already selected.”
13
Q
Sprint Burndown Chart
A
14
Q
Release Burndown Chart
A
15
Q
Scrum Team
A
- self-organizing development team
- each member contributes in whatever way they can towards completing each sprint
- includes developers, ScrumMaster, and product owner
- racecar analogy
- dev team = car
- product owner = driver
- ScrumMaster = chief mechanic
16
Q
What kinds of items are in a Scrum Product Backlog?
A
- Features
- Bugs
- Technical Work
- Knowledge Acquisition
17
Q
Scrum Bugs
A
- essentially the same as a feature, since it describes what a user wants
- these are also put on the Scrum Product Backlog
18
Q
Technical Work and Knowledge Acquisition
A
- also belong on the Scrum Product Backlog
- ex: “Upgrade all developers’ workstations to Windows 10”
- ex: Research various JavaScript libraries and make a selection
19
Q
Sprint Planning Meeting
A
- product pwner presents the prioritized product backlog and describes the top items
- the team determines what can be completed during the coming sprint
- items are moved from the product backlog to the sprint backlog
- the product backlog item becomes one or more sprint backlog tasks so team members can share the work
20
Q
When can product requirements and prioritization be changed?
A
- outside of the sprint
21
Q
Release Burndown Chart
A
