Practices

Question 1

6 Practices

Answer 1

Moscow Prioritisation
Timeboxing
Daily Stand-Ups
Facilitated Workshops
Modelling
Iterative Development

Question 2

Types of Timeboxes

Answer 2

Structured

Free format

Question 3

Unique phases of structured timebox

Answer 3

Investigation
Refinement
Consolidation

Question 4

Types of Testing

Answer 4

Positive tests
Negative tests
Unhappy path

Question 5

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

Answer 5

Positive

Question 6

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

Answer 6

Negative

Question 7

Testing: Check behavior of product when something undefined happens.

Answer 7

Unhappy path

Question 8

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

Answer 8

Must Have

Question 9

Must Have % of effort

Answer 9

Should not exceed 60%

Question 10

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.

Answer 10

Should Have

Question 11

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

Answer 11

Could Have

Question 12

Could Have % of effort

Answer 12

Should not exceed 20% of what is available

Question 13

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

Answer 13

Won’t Have

Question 14

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

Answer 14

Timeboxing

Question 15

Typical length of timebox

Answer 15

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.

Question 16

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

Answer 16

Kick-Off and Close-Out

Question 17

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

Answer 17

Kickoff

Question 18

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

Answer 18

Close-out

Question 19

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

Answer 19

Investigation

Question 20

Investigation % effort

Answer 20

10-20

Question 21

Structured Timebox step

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

Answer 21

Refinement

Question 22

Refinement % of effort

Answer 22

60-80%

Question 23

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.

Answer 23

Consolidation

Question 24

Consolidation % of effort

Answer 24

10-20%

Question 25

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

Answer 25

Daily Stand-Ups

Question 26

Typical length/formula for daily stand-ups

Answer 26

15 minutes. 2 minutes per participant + 2 minutes.

Question 27

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

Answer 27

Facilitated Workshops

Question 28

Benefit of Facilitated Workshops

Answer 28

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

Question 29

Factors critical to workshop success

Answer 29

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

Question 30

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

Answer 30

Modelling

Question 31

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.

Answer 31

Iterative Development

Question 32

Each iterative development cycle starts and ends with

Answer 32

Conversation

Question 33

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

Answer 33

Technical coordinator

Question 34

will carry out the tests to ensure criteria have been met

Answer 34

Tester

Question 35

esponsible for business acceptance testing

Answer 35

Ambassador and Advisor