• 検索結果がありません。

CHAOS MANIFESTO 2011

35 Acceptance tests are run often and the score is published

for Mo・No・Zu・Ku・Ri

科学技術ソフトウェア開発へのアジャイル手法の適用(3/8) 参考

No. Agile Practices

21 All production code is pair programmed 22 Only one pair integrates code at a time 23 Integrate often

24 Set up a dedicated integration computer 25 Use collective ownership*

26 Simplicity in design*

27 Choose a system metaphor

28 Use class-responsibility-collaboration (CRC) cards for design sessions 29 Create spike solutions to reduce risk*

30 No functionality is added early

31 Refactor whenever and wherever possible 32 All code must have unit tests

33 All code must pass all unit tests before it can be released 34 When a bug is found, tests are created

35 Acceptance tests are run often and the score is published

* Denotes Extreme Programming (XP) practices that are also recommended practices in the Scrum

methodology.

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

科学技術ソフトウェア開発へのアジャイル手法の適用(4/8) 参考

No. Projects

1 2 3.1 3.2 3.3 3.4 3.5 3.6 4 5

1 X X

2 X X

3 X

4 X X

5 ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

6 X X

7 X ✔ ✔ ✔ ✔ ✔ ✔ ✔

8 ✔ ✔ ✔ X ✔ ✔ ✔ ✔

9 X ✔ ✔

10 X

11 ✔

12 ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

13 X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

14 ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

15 ✔

16 X ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

17 X ✔ ✔

18 ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

19 ✔ ✔ ✔

20 ✔

21 X X X X X X X ✔

22 ✔

23 ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

X: 未使用 ✔: 使用 (空白): 不明

Mapping chart of agile practices from the literature review

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

科学技術ソフトウェア開発へのアジャイル手法の適用(5/8) 参考



Characteristics feniCS* Dalton olga

Scientific domain Mathematical (automated Chemistry (molecular Physics (flow modeling solution of differential electronic structures) of oil, gas, and natural

equations) water)

Number of >10 40 50

contributors

Duration 10 years 30 years 30 years

Programming C++, Python Fortran 77/90, C, C++ Fortran, C++, C#

languages

Chosen process No specific No specific Scrum

method

Distributed Yes Yes Yes

development

Availability Free, open source Free, licensed Proprietary

* FEniCS stands for Finite Elements in Computational Science.

Characteristics of the case study projects

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

科学技術ソフトウェア開発へのアジャイル手法の適用(6/8) 参考



Practice Projects

number feniCS Dalton olga

1 X X

2 X X

3 X X

4 X X

5 X X

6 X X

7 X X

8

9 X X X

10 X X

11 X X

12 X X X

13 X X

14 X X X

15 X X X

16 X X X

Mapping chart of agile practices from the case study

17 X X

18

19

X

20  X X X

21 X X X

22 X X X

23

X

24 X X X

25 X X

26

X X

27 X X X

28 X X X

29 X X X

30 X

31

X X

32 X X X

33

34 X

X

35

X X

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

科学技術ソフトウェア開発へのアジャイル手法の適用(7/8) 参考

多くのプロジェクトで使用されたプラクティス

5 (time-boxed sprints)

7 (short daily meetings) 8 (self-organizing team) 12 (release planning) 13 (user stories)

14 (dedicated open work space for team) 16 (project velocity is measured)

18 (customer is always available) 23 (integrate often)

25 (collective ownership)

31 (refactor whenever and wherever possible)

ほとんど使われなかったか,不明のプラクティス

21 (all production code is pair programmed) 24 (set up a dedicated integration computer)

28 (use class-responsibility-collaboration, or CRC, cards for design sessions)

29 (create spike solutions to reduce risk)

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

科学技術ソフトウェア開発へのアジャイル手法の適用(8/8) 参考

In all projects where we could identify the presence of one or more test-related agile practices, problems with testing were less

frequently reported than in the other projects.

Contemporary scientific software-development projects embrace the agile spirit in their focus on flexibility and communication, but otherwise are selective in using specific agile practices according to the book.

Some of the more technology-driven practices simply might not be known to scientists who aren’t professional software developers.

Nevertheless, the literature review indicated that agile techniques generally had positive effects in the projects investigated.

The agile approach can be valuable to scientific software

development, especially for smaller-sized teams and projects.

テスト関連のアジャイルプラクティスを使ったプロジェクトでは,テストの問題はあまり報告されなかった.

柔軟性とコミュニケーションに焦点を当ててアジャイルの精神を取り入れている.

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

H23年度版報告書の公開中

http://www.ipa.go.jp/about/press/20120328.html

http://sec.ipa.go.jp/reports/20120326.html

http://sec.ipa.go.jp/reports/20120611.html

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

●ご質問、ご意見は、SECホームページからお願い致します。

ご質問・意見の宛先

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

IPA/SECホームページ:

http://sec.ipa.go.jp/index.html

ご清聴,ありがとう

ございました

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

参考. 各種調査データ(追加分)

SEC

Software Engineering for Mo・No・Zu・Ku・Ri

2012年秋

刊行予定

日本ではまだアジャイル手法の利用は少ない(1)

N=2957