Chapter 3 Flashcards

1
Q

List

4 stages of a Scrum sprint

A

Plan
Build
Test
Review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

List and Define

3 roles in Scrum

A

Product owner- creates and prioritizes backlog

Scrum Master- facilitates, removes obstacles, runs meetings, coaches

Team members

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

List and Define

3 artifacts of Scrum

A

Product backlog- prioritized list of product requirements or features
Sprint backlog- subset of above to be completed during sprint
Code Increment- result of a sprint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Define

Sprint Planning Meeting

A

Determine what items from product backlog can be delivered in time-box, move to sprint backlog. Decide team roles

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Define

Daily Scrum Meeting

A

15 minutes
What did you accomplish?
What obstacles did you find?
What do you plan to accomplish before next meeting?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Define

What is Agility

A

Effective response to change
Effective communication among all stakeholders
Drawing customer into team
Rapid, incremental delivrey of software

Like making a meal and giving tastes along the way

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

List

Pros of Scrum

A

Product owner sets priorities
Team owns decision making
Documentation is lightweight
Supports frequent updating

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

List

Cons of Scrum

A

Difficult to control cost of changes
May not be suitable for large teams
Requires expert team members

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

List

Extreme Programming (XP) process

A

Planning
Design
Coding
Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Define

XP Planning

A

Begins with user stories, cost estimate (length of time), stories chosen for increment, delivery date set, project velocty estimated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Define

XP Design

A

KIS, encourages use of CRC cards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Define

XP Coding

A

Construct unit tests before coding, program in pairs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Define

XP Testing

A

Unit tests executed daily, acceptance tests defined by customer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

List

Pros of XP

A

Emphasizes customer involvement
Establishes rational plans and schedules
High developer commitment to the projects
Reduced likelihood of project rejection

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

List

XP Cons

A

Temptation to ‘ship’ a prototype
Requires frequent meetingd about increasing costs
Allows for excessive changes
Depends on highly skilled team members

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Describe

Kanban Framework

A

Visual presentation
Limits amount of work in progress at any time
Managing workflow to reduce waste
Making policies explicit, define ‘done’
Continuous improvement with feedback loops
Process changes made collaboratively

17
Q

List

Pros of Kanban

A

Lower budget and time requirements
Allows early product delivery
Process policies written down
Continuous improvement

18
Q

List

Cons of Kanban

A

Team collab skills determine success
Poor business analysis can doom
Flexibility can cause to lose focus
Development reluctant to use measurement

19
Q

List and Define

DevOps

A

Continuous development in multiple sprints
Continuous testing with automatic tools used prior to integration
Continuous integration with new code added to existing
Continuous deployment
Continuous Monitoring of the production environment

20
Q

List

Pros of DevOps

A

Reduced time to Deploy
Team has development and operations staff
Team has end-to-end ownership
Proactive monitoring

21
Q

List

Cons of DevOps

A

Pressure to work on old and new code
Heavy reliance on auto tools to be affective
Deployment may affect the product environment