Lecture 3 Flashcards

1
Q

What is the extreme programming release cycle?

A
Select user stories for release
Break down stories into tasks
Plan release
Develop/integrate/test
Release software
Evaluate system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the extreme programming practices (specific)?

A
Incremental planning
Small releases
Simple design
Test-driven development
Refactoring
Pair programming
Collective ownership
Continuous integration
Sustainable pace
On-site customer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are Kent Beck’s four XP themes?

A
  1. Fine scale feedback
  2. Continuous process
  3. Shared understanding
  4. Programmer well-being
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What does ‘fine scale feedback’ involves?

A

Pair programming
TDD
“Whole team” all stakeholders, user representatives
Planning game

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

What does ‘continuous process’ involves?

A
Continuous integration
Design improvement (refactoring)
Small releases
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What does ‘shared understanding’ involves?

A

Coding standards
Collective code ownership
Simple design
System metaphor

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

What is the meaning of a system metaphor?

A

The system metaphor is a story that everyone – customers, programmers, and managers - can tell about how the system works. - Kent Beck

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

Programmer well-being involves what?

A

Avoiding crunches
Facilitated by frequent releases
Velocity, rate at which tasks are completed

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

Risk management is done are which stages of the project?

A

Start
Beginning of major project phases
When there are significant changes

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

What are the four steps of risk management?

A
  1. Risk identification
  2. Risk analysis
  3. Risk management planning
  4. Risk review
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are three things to consider for risk identification?

A
  • Weak areas
  • Aspects that are critical to project success
  • Problems that have plagued past projects
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the columns of the ris priority table?

A

Risk/Likelihood/Impact/Priority

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

Risk management table columns?

A
  • Risk
  • Actions to reduce likelihood
  • Actions to reduce impact
  • Who should work on actions
  • When should actions be complete
  • Status of actions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the three tips of the ‘Iron triangle’

A
  • Scope
  • Resources
  • Schedule
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What did the Chaos Report revealed?

A

51% of projects are challenged (severely over budget and/or late)

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

What four elements define the software process?

A
  • Specification
  • Design and implementation
  • Validation
  • Evolution
17
Q

What is the biggest difference between agile and waterfall?

A

• Waterfall is defined by inflexible partitioning of the project into distinct stages. This makes it difficult to respond to changing customer requirement needs.