Open-Source
   Project Tools
        for
Corporate Projects?
     bertrand delacrétaz
        codeconsult.ch
    bdelacret...
Can the corporate
world learn something
from successful Open
   Source projects?
Can we Succeed?




Efficient communication is (obviously)
   the key to successful teamwork...
                           ...
Open Source Projects
 timezones            cultures
                        egos
english?    chaotic
meetings?            ...
Corporate Projects
• structure
• rules
• same office, same language
• meetings!
• the boss!
• bullet points
          ...ma...
why?
The Questions
1. What are we doing?
2. Who knows what?
3. Who usually does what?
4. Who did what, precisely?
5. What happe...
Self-Service




Team members need self-service answers.
The Tools
Mailing Lists
and Archives
           The default
           tool...

           Not much
           structure

          ...
Source Code Repository
                Stores all
                revisions of
                all code

                T...
Issue Tracker
         One page per issue

         History, decisions

         Not only for bugs!

         Powerful sea...
Issue Dependencies




Answer “why is this not done?”
     Show critical paths
Project Wiki
           Collaborative
           editing

           Traceable
           writing

           Centralized
...
Project Blog
        Chronological
        posts, news,
        articles

        Categories, search

        Central sour...
What does
each tool bring?
Mailing Lists
         and Archives




Lists require lots of discipline to be useful.
          Searching is often hard.
Source Code Repository




 Adds a lot of value to simple checkout
         and commit operations.
  Tells the story of th...
Issue Tracker




 Structuring and classification add a lot of value.
           Gives each issue a unique ID.
Very detaile...
Project Wiki




Does not adds much value to the content.
    Needs discipline to stay useful.
        Strong linking feat...
Project Blog




The best way to disseminate news.
      Celebrate milestones.
Leave space for Random Thoughts.
  Does you...
Answers?
Answers
Lists         Bugzilla    Weblog

                              1. What are we doing?
                            ...
Examples
    Apache HTTP Server
      Mozilla, Firefox
           Linux
       Open Office
         etc., etc...
Using publ...
Counter-Examples



 Let’s have a show of hands...
What now?
Start Small...




A source code
repository and issue
tracker bring the most
value.
The Rules

  If you’re working on something,
it must be an issue from our tracker.

  If something’s not in the source
   ...
Coda
Conclusions

        These tools work!
Self-service answers are the key.
       You can start small.
      Don’t forget op...
Links
http://www.bugzilla.org/
http://www.atlassian.com/software/jira/

http://www.nongnu.org/cvs/
http://subversion.tigri...
Open-Source Project Tools for Corporate Projects?
Upcoming SlideShare
Loading in …5
×

Open-Source Project Tools for Corporate Projects?

5,031 views
4,977 views

Published on

Using Open-Source Project Tools for Corporate Projects? Presented at ApacheCon EU 2006, Dublin.

Published in: Technology
2 Comments
15 Likes
Statistics
Notes
  • Very well put together presentation, congratulations!
    http://www.homeimprovementfirm.com
    http://www.homeimprovementfirm.com/category/furniture
    http://www.homeimprovementfirm.com/category/kitchen-furniture
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • This is what enterprise 2.0 can learn from open source. Great presentation.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
5,031
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
319
Comments
2
Likes
15
Embeds 0
No embeds

No notes for slide

Open-Source Project Tools for Corporate Projects?

  1. 1. Open-Source Project Tools for Corporate Projects? bertrand delacrétaz codeconsult.ch bdelacretaz@apache.org
  2. 2. Can the corporate world learn something from successful Open Source projects?
  3. 3. Can we Succeed? Efficient communication is (obviously) the key to successful teamwork... photo: www.imageafter.com
  4. 4. Open Source Projects timezones cultures egos english? chaotic meetings? divas no boss ...many are successful!
  5. 5. Corporate Projects • structure • rules • same office, same language • meetings! • the boss! • bullet points ...many fail!
  6. 6. why?
  7. 7. The Questions 1. What are we doing? 2. Who knows what? 3. Who usually does what? 4. Who did what, precisely? 5. What happened while I was away? 6. How are we doing? 7. When will this be ready? 8. Who said what on that topic? 9. Wasn’t this said before?
  8. 8. Self-Service Team members need self-service answers.
  9. 9. The Tools
  10. 10. Mailing Lists and Archives The default tool... Not much structure Too much information Archives help
  11. 11. Source Code Repository Stores all revisions of all code Traceable code, differences Log messages, what changed
  12. 12. Issue Tracker One page per issue History, decisions Not only for bugs! Powerful search and classification Dependencies, critical paths
  13. 13. Issue Dependencies Answer “why is this not done?” Show critical paths
  14. 14. Project Wiki Collaborative editing Traceable writing Centralized content Potentially chaotic
  15. 15. Project Blog Chronological posts, news, articles Categories, search Central source of news, gossip, stories RSS feeds, broadcasting
  16. 16. What does each tool bring?
  17. 17. Mailing Lists and Archives Lists require lots of discipline to be useful. Searching is often hard.
  18. 18. Source Code Repository Adds a lot of value to simple checkout and commit operations. Tells the story of the code in detail.
  19. 19. Issue Tracker Structuring and classification add a lot of value. Gives each issue a unique ID. Very detailed story of the project, knowledge base.
  20. 20. Project Wiki Does not adds much value to the content. Needs discipline to stay useful. Strong linking features.
  21. 21. Project Blog The best way to disseminate news. Celebrate milestones. Leave space for Random Thoughts. Does your customer subscribe?
  22. 22. Answers?
  23. 23. Answers Lists Bugzilla Weblog 1. What are we doing? 2. Who knows what? 3. Who usually does what? 4. Who did what, precisely? 5. What happened while I was away? 6. How are we doing? 7. When will this be ready? 8. Who said what on that topic? 9. Wasn't this said before? CVS Wiki
  24. 24. Examples Apache HTTP Server Mozilla, Firefox Linux Open Office etc., etc... Using public instances of these tools...
  25. 25. Counter-Examples Let’s have a show of hands...
  26. 26. What now?
  27. 27. Start Small... A source code repository and issue tracker bring the most value.
  28. 28. The Rules If you’re working on something, it must be an issue from our tracker. If something’s not in the source code repository, it doesn’t exist.
  29. 29. Coda
  30. 30. Conclusions These tools work! Self-service answers are the key. You can start small. Don’t forget openness.
  31. 31. Links http://www.bugzilla.org/ http://www.atlassian.com/software/jira/ http://www.nongnu.org/cvs/ http://subversion.tigris.org/ http://www.ezmlm.org/

×