the impact of switching to a rapid release cycle on integration delay of addressed issues

Post on 15-Apr-2017

84 Views

Category:

Software

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

The Impact of Switching to a Rapid Release cycle on Integration Delay of

Addressed Issues

Daniel A. Costa Shane McIntosh Uirá Kulesza Ahmed E. Hassan

UFRN McGill UFRN Queen’s

Issues can represent bug fixes, enhancements, and new features

Bug fix

New feature

Enhancement

1

Software projects must attract and retain users to survive

2

Slow delivery of fixed issues can drive users away

So, when does this fix will get added? Firefox release 22? 23?

(Issue report #883554)

3

Proponents of rapid release cycles argue that fixed issues can be delivered faster

4

We study the rapid and traditional releases of Mozilla Firefox

Traditional Rapid

VS

5

Traditional Rapid111 releases 73 releases

We study the rapid and traditional releases of Mozilla Firefox

VS

5

Traditional Rapid111 releases 73 releases

34,673 issues 37,443 issues

We study the rapid and traditional releases of Mozilla Firefox

VS

5

Traditional Rapid111 releases 73 releases

34,673 issues 37,443 issues

We study the rapid and traditional releases of Mozilla Firefox

VS

1.0 to 4.0 10 to 275

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

6

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1)Comparing traditional

and rapid release strategies

VS

6

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2)Comparing traditional

and rapid release strategies

Studying minor and major releases

3.6 3.6.1 3.6.2VS

6

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditional

and rapid release strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

6

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditional

and rapid release strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

6

We measure the delivery delay

3.01.0 2.0

7

We measure the delivery delay

3.01.0 2.0

7

We measure the delivery delay

3.0130 days1.0 2.0

7

Issues are addressed more quickly in rapid releases but are delivered more slowly

500

50

5

1

Day

s to

deliv

er fi

xed

issu

es

TraditionalRapid

8

Issues are addressed more quickly in rapid releases but are delivered more slowly

500

50

5

1

Day

s to

deliv

er fi

xed

issu

es

TraditionalRapid

Data density

8

Issues are addressed more quickly in rapid releases but are delivered more slowly

500

50

5

1

Day

s to

deliv

er fi

xed

issu

es

TraditionalRapid

MedianMedian

Data density

8

Issues are addressed more quickly in rapid releases but are delivered more slowly

500

50

5

1

Day

s to

deliv

er fi

xed

issu

es

TraditionalRapid

8

Fixed issues are delivered more consistently in rapid releases

TraditionalRapid

I can be faster!

I have consistent

gains!

9

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditional

and rapid release strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

10

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditional

and rapid release strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

Traditional releases can deliver issues

more quickly

10

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditional

and rapid release strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

Traditional releases can deliver issues

more quickly

10

Minor releases are how traditional releases deliver issues more quickly

500

50

5

1

Major traditional

Minor traditional

Day

s to

deliv

er fi

xed

issu

es

11

Minor releases are how traditional releases deliver issues more quickly

500

50

5

1

Major traditional

Minor traditional

Day

s to

deliv

er fi

xed

issu

es Major traditional

Rapid

11

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditional

and rapid release strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

Traditional releases can deliver issues

more quickly

12

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditional

and rapid release strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

Traditional minor releases lead to faster

delivery of issues

Traditional releases can deliver issues

more quickly

12

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditional

and rapid release strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

Traditional minor releases lead to faster

delivery of issues

Traditional releases can deliver issues

more quickly

12

Factors that can cause delivery delay

Number of Impacted Files

13

Factors that can cause delivery delay

Number of Impacted Files

I Think this bug is due to…

Number of comments

13

Factors that can cause delivery delay

Number of Impacted Files

Number of comments Experience of the resolvers

VSI Think this bug is due to…

13

Factors that can cause delivery delay

Number of Impacted Files

Number of comments Experience of the resolvers

VS

And more

I Think this bug is due to…

13

A fixed issue is delayed if it is not shipped in the next upcoming release

3.01.0 2.0

14

A fixed issue is delayed if it is not shipped in the next upcoming release

3.01.0 2.0Not delayed

14

A fixed issue is delayed if it is not shipped in the next upcoming release

3.01.0 2.0 Delayed

14

We build logistic regression models to study factors associated with delay

Trad.

Rapid

15

We build logistic regression models to study factors associated with delay

Regression models

Trad.Learn from

RapidLearn from

15

We build logistic regression models to study factors associated with delay

Regression models

not delayedTrad.Learn from Answer

delayed

not delayedRapidLearn from Answer

delayed

15

We build logistic regression models to study factors associated with delay

Regression models

not delayedTrad.Learn from Answer

delayed

not delayedRapidLearn from Answer

delayed

VS

15

3.02.0

Traditional

Prioritization is different along strategies

16

3.02.0

Traditional

Prioritization is different along strategies

Backlog of issues

16

3.02.0

Traditional

Prioritization is different along strategies

16

3.02.0Position 4 in the backlog

Traditional

Prioritization is different along strategies

16

3.02.0Position 4 in the backlog

Traditional

Prioritization is different along strategies

0.950.900.850.80

0 5,000 10,000Position in the backlog

Prob

abili

ty o

f del

ay16

3.02.0Position 4 in the backlog

Traditional

2.0

Rapid

3.0

Prioritization is different along strategies

0.950.900.850.80

0 5,000 10,000Position in the backlog

Prob

abili

ty o

f del

ay16

3.02.0Position 4 in the backlog

Traditional

2.0

Rapid

3.0

Prioritization is different along strategies

0.950.900.850.80

0 5,000 10,000Position in the backlog

Prob

abili

ty o

f del

ay

Release cycle backlog

16

3.02.0Position 4 in the backlog

Traditional

2.0

Rapid

3.0

Prioritization is different along strategies

0.950.900.850.80

0 5,000 10,000Position in the backlog

Prob

abili

ty o

f del

ay16

3.02.0Position 4 in the backlog

Traditional

2.0

Rapid

3.0

Prioritization is different along strategies

0.950.900.850.80

0 5,000 10,000Position in the backlog

Prob

abili

ty o

f del

ay

Position 2 in the cycle backlog

16

3.02.0Position 4 in the backlog

Traditional

2.0

Rapid

3.0

Prioritization is different along strategies

0.950.900.850.80

0 5,000 10,000Position in the backlog

Prob

abili

ty o

f del

ayPr

obab

ility

of d

elay

0.95

0.900.850.80

Position in the cycle backlog0 1,000 3,000

Position 2 in the cycle backlog

16

Traditional releases behave as a queue while rapid releases behave as a stack

VS

17

1.0 2.0 3.0VS

Traditional releases behave as a queue while rapid releases behave as a stack

17

Released Completed

1.0 2.0 3.0VS

Traditional releases behave as a queue while rapid releases behave as a stack

17

Released Completed

1.0 2.0 3.0

3.0

2.0

1.0

VS

Traditional releases behave as a queue while rapid releases behave as a stack

17

Released Completed

1.0 2.0 3.0

3.0

2.0

1.0

VS

Traditional releases behave as a queue while rapid releases behave as a stack

CompletedReleased

17

Are addressed issues delivered more quickly in rapid releases?

Case study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditionaland rapid releasing

strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

Traditional minor releases lead to faster

delivery of issues

Traditional releases can deliver issues

more quickly

1

Are addressed issues delivered more quickly in rapid releases?

Case study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditionaland rapid releasing

strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

Traditional minor releases lead to faster

delivery of issues

Traditional releases can deliver issues

more quickly

Traditional and rapid releases prioritize issues differently

1

In Summary

Are addressed issues delivered more quickly in rapid releases?

Empirical study structure

(RQ.1) (RQ.2) (RQ.3)Comparing traditionaland rapid releasing

strategies

Studying minor and major releases

Studying delay factors of each release

strategy

3.6 3.6.1 3.6.2VS

Traditional minor releases lead to faster

delivery of issues

Traditional releases can deliver issues

more quickly

Traditional and rapid releases prioritize issues differently

Fixed issues are delivered more consistently in rapid releases

TraditionalRapid

I can be faster!

I have consistent

gains!

Minor releases are how traditional releases deliver issues more quickly

500

50

5

1

Major traditional

Minor traditional

Day

s to

deliv

er fi

xed

issu

es Major traditional

Rapid

3.02.0Position 4 in the backlog

Traditional

2.0

Rapid

3.0

Prioritization is different along strategies

0.950.900.850.80

0 5,000 10,000Position in the backlog

Prob

abili

ty o

f del

ayPr

obab

ility

of d

elay

0.95

0.900.850.80

Position in the cycle backlog0 1,000 3,000

Position 2 in the cycle backlog

top related