Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Agile Foundation > Practices > Flashcards

Practices Flashcards

1
Q

6 Practices

A 
Moscow Prioritisation
Timeboxing
Daily Stand-Ups
Facilitated Workshops
Modelling
Iterative Development
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Types of Timeboxes

A

Structured

Free format

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

Unique phases of structured timebox

A

Investigation
Refinement
Consolidation

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

Types of Testing

A

Positive tests
Negative tests
Unhappy path

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

Testing: Ensures that product does what it needs to do.

A

Positive

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

Testing: Show that product does not do what it is not supposed to do.

A

Negative

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

Testing: Check behavior of product when something undefined happens.

A

Unhappy path

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

Provide a minimum usable subset of the requirements. If not delivered, would mean that the project has failed to deliver a viable solution.

A

Must Have

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

Must Have % of effort

A

Should not exceed 60%

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

Leaving these requirements out will cause some pain but then delivered solution is still viable. Solution may require some kind of workaround to be fully functional.

A

Should Have

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

Wanted or desirable but less important. If left out, there would be less impact on the functionality of the solution.

Any need to reduce the requirements, will be the first to go

A

Could Have

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

Could Have % of effort

A

Should not exceed 20% of what is available

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

Will not be delivered and are strictly speaking out-of-scope.

Helps manage the expectations of the business users

Helps to nip scope creep in the bud before it even begins

A

Won’t Have

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

Defined period of time during which an objective is met

Objective relates to the completion of one or more deliverables which make up the solution increment

A

Timeboxing

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

Typical length of timebox

A

2-4 weeks

Important thing is that it’s an appropriate length of time for team to remain focused but long enough so that something meaningful can be achieved.

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

Structured and free format timebox both start with and end with what

A

Kick-Off and Close-Out

17
Q

Short session around 1-3 hours for an average 2-3 week timebox

Solution delivery team will understand the timebox objectives and priorities and agree them as realistic

A

Kickoff

18
Q

Typically 1-3 hours long for a 2-3 week timebox

Formal acceptance of the deliverables is obtained from the business visionary and the technical coordinator

A

Close-out

19
Q

Structured Timebox step

Gain understanding and agreement on the deliverables to be created
The acceptance criteria of the deliverables
Determining the measures of success for the timebox
Ends with a review, which informs next step

A

Investigation

20
Q

Investigation % effort

A

10-20

21
Q

Structured Timebox step

Creation and testing of the products taken place in line with agreed priorities
Ends with a review, which informs next step

A

Refinement

22
Q

Refinement % of effort

A

60-80%

23
Q

Structured Timebox step

Any loose ends related to evolutionary development are tied up
Cross checks are performed
Ends with a review, which informs the close-out. Concludes development part of timebox. May be useful point/governance juncture.

A

Consolidation

24
Q

Consolidation % of effort

A

10-20%

25
Q

Meetings held on a daily basis. Quick and concise information to be shared across the whole team in a relatively short period of time.

A

Daily Stand-Ups

26
Q

Typical length/formula for daily stand-ups

A

15 minutes. 2 minutes per participant + 2 minutes.

27
Q

A specialised type of meeting with clear objective deliverables. An independent facilitator appointed to enable achievement of the outcome.

A

Facilitated Workshops

28
Q

Benefit of Facilitated Workshops

A 
Rapid high-quality decision-making
Increased buy-in from all stakeholders
Team building 
Building consensus
Enhanced clarification of issues
29
Q

Factors critical to workshop success

A

effective and well-trained facilitator.

Flexibility of format but always with clear objectives

Thorough preparation ahead of the workshop by the workshop facilitator and the participants

Making sure that mechanisms for ensuring the outcomes of previous workshops are built in

30
Q

A visual representation of a problem is presented. A description or analogy used to help visualise something that cannot be observed.

A

Modelling

31
Q

Practice used to evolve a solution from a concept to something of value.

Collaborative always involving at least two members of the Solution Development Team.

A

Iterative Development

32
Q

Each iterative development cycle starts and ends with

A

Conversation

33
Q

responsible for integrity of solution and that quality requirements are reasonable and are met

A

Technical coordinator

34
Q

will carry out the tests to ensure criteria have been met

A

Tester

35
Q

esponsible for business acceptance testing

A

Ambassador and Advisor

Agile Foundation (7 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions