0
Two modes of Product Development Head-oriented vs. Release-oriented Masayuki Hatta Faculty of Economics, Surugadai Univers...
Observations <ul><li>Sometimes (software development) projects succeed </li><ul><li>Gaining more users, popularity, develo...
What's the difference? <ul><li>Not promising? </li><ul><li>Initial design flawed? </li></ul><li>Developers not competent e...
No demands? </li></ul>
How about the Linux kernel? <ul><li>Not so promising at first </li><ul><li>Tanenbaum vs. Torvalds dispute (1992)
Not promising == not attracting developers/users </li></ul><li>There are (better?) competitors in the F/OSS world </li><ul...
*BSD(looser licensing) </li></ul></ul>
Linx is not rare case <ul><li>e.g. KDE vs. GNOME
Some projects suddenly gain momentum
Some projects suddenly lose momentum </li></ul>
Hypothesis <ul><li>Mismatches between user/developer expectation? </li><ul><li>User preference might be changed as time go...
Hypothesis <ul><li>There seems to be two different “modes” of Software development </li><ul><li>I call them “Release-orien...
Release-oriented
Release-oriented <ul><li>With QA(Quality Assuarance) </li><ul><li>QA works don't add new features
QA is boring, believe me </li></ul><li>Stable(not so buggy, secure, etc), but not cutting-edge
Good for stable environment
Basically for users who appreciate “usable” projects
Most products go this way </li></ul>
Head-oriented
Upcoming SlideShare
Loading in...5
×

Mhatta hitotsubashi-20120221

233

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
233
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Mhatta hitotsubashi-20120221"

  1. 1. Two modes of Product Development Head-oriented vs. Release-oriented Masayuki Hatta Faculty of Economics, Surugadai University [email_address] [email_address] @Tokyo OSS Workshop, hit-u Feb. 21, 2012
  2. 2. Observations <ul><li>Sometimes (software development) projects succeed </li><ul><li>Gaining more users, popularity, developers </li></ul><li>Sometimes projects fail </li><ul><li>Losing more users, popularity, developers </li></ul></ul>
  3. 3. What's the difference? <ul><li>Not promising? </li><ul><li>Initial design flawed? </li></ul><li>Developers not competent enough?
  4. 4. No demands? </li></ul>
  5. 5. How about the Linux kernel? <ul><li>Not so promising at first </li><ul><li>Tanenbaum vs. Torvalds dispute (1992)
  6. 6. Not promising == not attracting developers/users </li></ul><li>There are (better?) competitors in the F/OSS world </li><ul><li>GNU/Hurd(promising architecture)
  7. 7. *BSD(looser licensing) </li></ul></ul>
  8. 8. Linx is not rare case <ul><li>e.g. KDE vs. GNOME
  9. 9. Some projects suddenly gain momentum
  10. 10. Some projects suddenly lose momentum </li></ul>
  11. 11. Hypothesis <ul><li>Mismatches between user/developer expectation? </li><ul><li>User preference might be changed as time goes by </li></ul></ul>
  12. 12. Hypothesis <ul><li>There seems to be two different “modes” of Software development </li><ul><li>I call them “Release-oriented” and “Head-oriented” </li></ul><li>Made it possible by technological advances (== lowering communication costs) </li></ul>
  13. 13. Release-oriented
  14. 14. Release-oriented <ul><li>With QA(Quality Assuarance) </li><ul><li>QA works don't add new features
  15. 15. QA is boring, believe me </li></ul><li>Stable(not so buggy, secure, etc), but not cutting-edge
  16. 16. Good for stable environment
  17. 17. Basically for users who appreciate “usable” projects
  18. 18. Most products go this way </li></ul>
  19. 19. Head-oriented
  20. 20. Head-oriented <ul><li>Continuously developed </li><ul><li>No release, just “snapshots”
  21. 21. “always beta” (O'Reilley 2008) </li></ul><li>e.g. Wikipedia
  22. 22. Users & developers share the same codebase </li><ul><li>Version Control System </li></ul><li>Good for rapidly changing environment
  23. 23. For developers(and advanced users) </li></ul>
  24. 24. Release vs. Head <ul><li>Surely there are hybrid release pattern </li></ul>
  25. 25. F/OSS development dilemma <ul><li>Gaining momentum
  26. 26. Gaining new users
  27. 27. New users(e.g. Corporate users) appreciate stable releases
  28. 28. Developers appreciate cutting-edge snapshots
  29. 29. Conflict! </li></ul>
  30. 30. KDE4 case (2008) <ul><li>KDE4 was released in 2008
  31. 31. Developers love it </li><ul><li>A lots of new ambitious features </li></ul><li>Users don't love it </li><ul><li>Unstable, buggy
  32. 32. However, KDE3 was also buggy </li></ul><li>Release manager in trouble </li></ul>
  33. 33. Other possible cases <ul><li>Dead-line based release (Michlmayr 2009)
  34. 34. Linux kernel? </li><ul><li>Changed release pattern </li></ul><li>Debian </li><ul><li>vs. Ubuntu </li></ul><li>Mozilla? </li><ul><li>vs. Gnome Chrome
  35. 35. Is there still “community” development? </li><ul><li>Limited N of developers employed by limited N of corporations </li></ul></ul></ul>
  36. 36. Further research <ul><li>Is this only a change in software development? </li><ul><li>e.g. Democratized innovation (von Hippel 2005)
  37. 37. e.g. Open Hardware
  38. 38. e.g. 3D printing </li></ul></ul>
  39. 39. Extra...
  40. 40. FLOSS Survey 2012(or 2013)? <ul><li>Almost 10 years since FLOSS Survey (2003)
  41. 41. It would be nice if we could do it again this year (or next) </li><ul><li>Comparision should be very interesting </li></ul><li>I'm trying to convince FSF hosts it
  42. 42. I'll talk at LibrePlanet 2012 </li></ul>
  43. 43. Thanks for listening [email_address] http://about.me/mhatta Twitter: @mhatta (in Japanese) Twitter: @masayukihatta (in English)
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×