Planning and Control Flashcards

1
Q

3 Planning Concepts

A

Outcome-Based Planning
Plan to sensible horizons at right level of detail
Plan and re-plan, based on available estimates

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

Two types of horizons for ‘plan to sensible horizons at right level of detail’

A

Horizon of delivery plan

Horizon of timebox plan

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

6 Testing Concepts

A
Testing integrated throughout
Collaborative testing
Repeatable testing
Prioritised testing
Independent testing
Test-driven development
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

4 Tracking and Control Concepts

A

Timeboxing and Outcome-Based Measurement
Transparency of Process and Progress
Responding to Change
Management by Exception

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

6 key points for quality activities

A
High-level risk analysis
Planning and high-level analysis
Detail analysis and planning
Prepare and run
Assess quality and impact
Final end-to-end testing and assuring implementation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Horizon of the delivery plan

A

High-level. Likely 6 weeks - 6 months.

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

Horizon of the timebox plan

A

More detailed. 2-4 weeks

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

Two established estimating techniques

A

Use more than one technique

Estimate in groups

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

Testing takes place within the same timebox as the development of any deliverable

Defects are detected early and the impact to the project in terms of time and cost is lower

A

Testing integrated throughout

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

Stakeholders should collaborate closely in respect to testing

Collaborators should come from a broad matrix, including business and solution interested personnel from development and testing circles

A

Collaborative testing

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

Include retesting of the existing features as new features are added in the respective iterations

A

Repeatable testing

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

May not always be sufficient time to carry out all the possible tests required

Based on the risk associated with a potential defect, using Moscow.

A

Prioritised testing

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

Testing of any deliverable should never be done by the same person who was responsible for its creation.

A

Independent testing

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

Which two roles always independent testers?

A

Business Ambassador and Business Advisor

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

The design and build of a test actually precedes the development of the solution and helps to define the requirement

A

Test-driven development

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

Provides the structure whereby a set of timeboxes together, with a deployment, fit within a single increment

A

Timeboxing and Outcome-Based Measurement

17
Q

Create visibility of the necessary elements of control and drive accountability

A

Transparency of Process and Progress

18
Q

Change needs to be embraced (but still controlled/constrained by business need and quality!)

A

Responding to Change

19
Q

Describes the limit of decision-making authority of a particular level of management. Day to day largely left to solution delivery team.

Team empowered to de-scope any ‘could have’ requirement without referring up to project level roles to ensure that must have and should have requirements are delivered.

A

Management by Exception