Towards Continuous Software Release Planning

8
Towards Continuous Software Release Planning David Ameller, Carles Farré, Xavier Franch, Danilo Valerio, and Antonino Cassarino

Transcript of Towards Continuous Software Release Planning

Page 1: Towards Continuous Software Release Planning

Towards Continuous Software Release Planning

David Ameller, Carles Farré, Xavier Franch, Danilo Valerio, and Antonino

Cassarino

Page 2: Towards Continuous Software Release Planning

2

Towards continuous SRP

Outline• Continuous SRP• Our approach• Research agenda• Questions for the audience

Page 3: Towards Continuous Software Release Planning

3

What is continuous SRP?

Project requirements Release plan

Software Release Planning

Strategic planning

Operational planning

Towards continuous SRP

R1: effort 2R2: effort 2R3: effort 3

R4: effort 2, dep R1 & R2R5: effort 2, dep R3R6: effort 2, dep R4

Job1

Job2 Job4

Job5

Job3

Bob

Tom

John Job6

Week1 Week2 Week3 Week4 Week5 Week6

Release deadline

Page 4: Towards Continuous Software Release Planning

4

What is continuous SRP?Towards continuous SRP

Continuous SRP is a specialization of the traditional SRPwith the added capability of adapting the release plan in

response to events that occur in the daily development activity

DevelopmentRequirement elicitation

Software Release Planning

Deployment Continuousintegration

ContinuousSRP1

2

3

4

Page 5: Towards Continuous Software Release Planning

5

What is our approach?Towards continuous SRP

Automatic tool Project leader

Software release re-planning

Proposedrelease plan(s)

Release planselection

Release planadaptation and

approval

Updatedrelease plan

Event detector and notifications

Detected risks or issues

Analysis of risk and issues

Trigger

Events:• Changes in the dependencies• Changes in the effort• Changes in the availability• Changes in the skills• Changes in the cost

Risks and issues:• Risk of overrun

• Time• Cost

• Unfeasible solution

Page 6: Towards Continuous Software Release Planning

6

What is our research agenda?• Determine the needs of the industry for

continuous SRP (empirical study)• Improvement of the approach

Additional events, risks, issues• Proof of concept (tool implementation)

Integration with development tools (e.g., Trello)• Validation in industry

Some contacts already made!• SIEMENS, SEnerCon, Agilogy, and Getupcode

Towards continuous SRP

Page 7: Towards Continuous Software Release Planning

7

Questions for the audience• To practitioners:

Would you use it? Why?• All:

What other events would you consider? What other risks or issues should be handled?

• To researchers: What do you miss in the research agenda?

Towards continuous SRP

Page 8: Towards Continuous Software Release Planning

Comments and questions

David Ameller<[email protected]>