Agile development: Issues and avenues requiring a substantial enhancement of the business perspective in large projects

Oualid Ktata, Ghislain Lévesque

University of Québec at Montréal 201,

avenue du Président-Kennedy Montréal, Québec, Canada

報告人：吳牧哲

Outline …………....………………

• INTRODUCTION• Potential issues in today’s large-scale development• Agile software development response• Areas of improvements• Potential benefits behind the use of goals• A goal and value oriented approach as a potential avenue• Conclusions and future work

INTRODUCTION ……………………. 1

• Large-scale developments

• Traditional approachs

• Agile methods

1. misunderstanding 2. custormer decisions

• Goals

Potential issues in today’s large-scale development .. 1

• Volatility of the business context

[1] Uncertainty and rapid change

[2] Obsolescence

[3] The wicked nature of software valuation

Potential issues in today’s large-scale development .. 2

• Limitations

on traditional software development

[1] SE basic assumptions

[2] Business cases limitations

[3] Contract negotiations

Agile software development response . 1

• Agile develop : principles, values and practices

• Agile business perspective

• Agile limitations in large-scale projects

Agile software development response . 2

Areas of improvements ……………… 1

• B-Scrum

Potential benefitsbehind the use of goals…………….… 1

• Goals generally describe objectives which a system should achieve through cooperation of actors in the intended software and in the environment .

• SMART (Specific, Measurable, Achievable, Relevant, and Time-Specific)

• SMARTER ( E=Extendable, R=Recorded )

Potential benefitsbehind the use of goals…………….… 2

• GORE ( Goal-oriented Requirement Engineering )

[1] Achieve requirements completeness:

[2] Avoid irrelevant requirements:

[3] Explain requirements to stakeholders:

[4] Increase readability of complex requirements documents

through goal refinement

[5] Explore alternatives:

[6] Manage conflicting situations:

[7] Distinguish between stable and volatile information:

[8] Identify system requirements:

[9] Relate requirements to organizational and business context:

[10] Derive design:

Potential benefitsbehind the use of goals…………….… 3

• IT Project governance

[1] Establish the basis …

[2] Evaluate project …

[3] Define the ‘desired business outcomes’ …

[4] Control the scope, contingency funds, overall project value …

[5] Monitor the project …

[6] Measure the outputs, outcomes, benefits and value …

[7] Steering the project …

[8] Develop the organization’s project delivery capability …

A goal and value oriented approach as a potential avenue ……………...….. 1

• Large-scale problem

• Goals

• How to use goals to achieve [1] Stakeholders can express their expectations in terms of goals.

[2] Hierarchical product backlog

[3] From working software to achieving business goals

[4] Prioritizing goals

[5] Business valued-goals

Conclusions and future work ………. 1

• Misunderstanding stakeholders’ needs

• Product owner

• Goal-value oriented approach

• Future work