CHAPTER 3 - Agile Development

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/43

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

44 Terms

1
New cards

Processes, tools

Individuals and interactions over _________ and _____

2
New cards

Documentation

Working software over comprehensive _____________

3
New cards

Contract

Customer collaboration over ________ negotiation

4
New cards

Plan

Responding to change over following a ____

5
New cards

Agility

Effective (rapid and adaptive) response to change

6
New cards

Agility

Effective communication among all stakeholders, Drawing the customer onto the team , Organizing a team so that it is in control of the work performed

7
New cards

Agility

Yielding − Rapid, incremental delivery of software

8
New cards

Agile Process

Is driven by customer descriptions of what is required (scenarios), Recognizes that plans are short-lived

9
New cards

Agile Process

Develops software iteratively with a heavy emphasis on construction activities, Delivers multiple 'software increments', Adapts as changes occur

10
New cards

Early, continuous

Our highest priority is to satisfy the customer through _____ and __________ delivery of valuable software.

11
New cards

Change

Welcome changing requirements, even late in development. Agile processes harness ______ for the customer's competitive advantage.

12
New cards

Frequently

Deliver working software __________, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

13
New cards

Business people

________ ______ and developers must work together daily throughout the project.

14
New cards

Motivated

Build projects around _________ individuals. Give them the environment and support they need, and trust them to get the job done.

15
New cards

Face-to-face

The most efficient and effective method of conveying information to and within a development team is ____-__-____ conversation

16
New cards

Software

Working ________ is the primary measure of progress.

17
New cards

Constant pace

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a ________ ____ indefinitely.

18
New cards

Agility

Continuous attention to technical excellence and good design enhances _______

19
New cards

Simplicity

the art of maximizing the amount of work not done - is essential.

20
New cards

Self-organizing

The best architectures, requirements, and designs emerge from ____-__________ teams.

21
New cards

Reflects

At regular intervals, the team ________ on how to become more effective, then tunes and adjusts its behavior accordingly

22
New cards

Human Factors

The process molds to the needs of the people and team, not the other way around

23
New cards

Extreme Programming

The most widely used agile process, originally proposed by Kent Beck.

24
New cards

Kent beck

he proposed extreme programming

25
New cards

XP Planning

− Begins with the creation of "user stories"

− Agile team assesses each story and assigns a cost

− Stories are grouped to for a deliverable increment

− A commitment is made on delivery date

26
New cards

Project velocity

in xp planning, After the first increment, "_______ ________" is used to help define subsequent delivery dates for other increments

27
New cards

XP Design

− Follows the KIS principle

− Encourage the use of CRC cards

− For difficult design problems, suggests the creation of "spike solutions"—a design prototype

− Encourages "refactoring"—an iterative refinement of the internal program design

28
New cards

spike solutions

In xp design, For difficult design problems, suggests the creation of "_____ _________"—a design prototype

Refactoring = in xp design, Encourages "__________"—an iterative refinement of the internal program design

29
New cards

XP Coding

− Recommends the construction of a unit test for a store before coding commences

− Encourages "pair programming"

30
New cards

XP Testing

− All unit tests are executed daily

− "Acceptance tests" are defined by the customer and executed to assess customer visible functionality

31
New cards

Jim Highsmith

he proposed Adaptive Software Development

32
New cards

Adaptive software development

Distinguishing Features:

− Mission-driven planning

− Component-based focus

− Uses "time-boxing"

− Explicit consideration of risks

− Emphasizes collaboration for requirements gathering

− Emphasizes "learning" throughout the process

33
New cards

Dynamic Systems Development Method

Promoted by the DSDM Consortium (www.dsdm.org)

34
New cards

Dynamic Systems Development Method

Distinguishing Features

35
New cards

Dynamic Systems Development Method

− Similar in most respects to XP and/or ASD

− Nine guiding principles

− Active user involvement is imperative.

− DSDM teams must be empowered to make decisions.

− The focus is on frequent delivery of products.

− Fitness for business purpose is the essential criterion for acceptance of deliverables.

− Iterative and incremental development is necessary to converge on an accurate business solution.

− All changes during development are reversible.

− Requirements are baselined at a high level

− Testing is integrated throughout the life-cycle.

36
New cards

Schwaber and Beedle

they Originally proposed Scrum

37
New cards

Scrum

Distinguishing Features:

− Development work is partitioned into "packets"

− Testing and documentation are on-going as the product is constructed

− Work occurs in "sprints" and is derived from a "backlog" of existing requirements

− Meetings are very short and sometimes conducted without chairs

− "demos" are delivered to the customer with the time-box allocated

38
New cards

Cockburn and Highsmith

they proposed Crystal

39
New cards

Crystal

Distinguishing Features:

− Actually a family of process models that allow "maneuverability" based on problem characteristics

− Face-to-face communication is emphasized

− Suggests the use of "reflection workshops" to review the work habits of the team

40
New cards

Peter Coad et al

proposed Feature Driven Development

41
New cards

Feature driven development

Distinguishing Features

− Emphasis is on defining "features"

○ a feature "is a client-valued function that can be implemented in two weeks or less."

− Uses a feature template

the a(n)

− A features list is created and "plan by feature" is conducted

− Design and construction merge in FDD

42
New cards

feature

in feature driven development, it "is a client-valued function that can be implemented in two weeks or less."

43
New cards

Scott Ambler

proposed Agile Modeling

44
New cards

Agile modeling

Suggests a set of Agile Modeling Principles

− Model with a purpose

− Use multiple models

− Travel light

− Content is more important than representation

− Know the models and the tools you use to create them

− Adapt locally