Yet another Open Development in the Enterprise remix. More synthetic, aimed more at managers than developers.

1. open
development
in the enterprise
Bertrand Delacrétaz
@bdelacretaz, grep.codeconsult.ch
Senior R&D Developer, Adobe Basel
Apache Software Foundation Member and Director
October 2013
slides revision 2013-10-29

2. can
distributed
teams
work?

3. what's a
successful
software
project?

4. good software is
simple
reliable
right features
and has the
more brain cells are good.

5. Corporate teams are too often isolated
in their own watertight boxes...
Bertrand Delacretaz, Octobermorguefile.com
picture: krosseel on 2013

6. Open Development
in the enterprise
A common, shared flow of information
makes all the difference
Bertrand Delacretaz, Septembermorguefile.com
picture: taysm on 2013

7. it’s about
feedback
pictures: taliesin, kevinrosseel xfoto on morguefile,
ck
ba
ed
e
t fs!
fas p
loo
Bertrand Delacretaz, October 2013

8. can
distributed
teams
work?

9. Different cultures,
timezones,
mother tongues,
habits.
Recipe for failure?
smiley: dhester on morguefile.com

10. Open source success stories!
Semi-chaotic, multicultural,
multi-timezone distributed
teams that work.

11. what
is open development?
(it’s like open source)

12. open
everybody gets the same information
picture: taysm on morguefile.com

13. meritocratic
nobody knows you’re a dog
picture: xandert on morguefile.com

14. sustainable
conflict resolution rules
self-service archives
exposure promotes quality
picture: ostephy on morguefile.com

15. key
elements

16. Shared vision
4 drivers
Real-time status updates
Broadcast help requests
Searchable archives
pictures from morguefile.com
http://morguefile.com/license/morguefile/
Bertrand Delacretaz, October 2013

17. “centralized open collaboration bus”
discussions,
decisions,
votes:
mailing lists
& archives
tasks:
issue tracker
code: shared
code repository
smiley: dhester on morguefile.com

18. the
rules

19. talk to
the project!
(no 1-1 email)

20. speak
in URLs!
(precise references to persistent information)
email is where information goes to die...

21. plan in
the tracker!
(issue tracker tickets for everything)

22. code in
the repository!
(there's no "it's on my hard disk")

23. “centralized open collaboration bus”
discussions,
decisions,
votes:
mailing lists
& archives
tasks:
issue tracker
code: shared
code repository
smiley: dhester on morguefile.com

24. does it work?

25. and many others...
piggy: mconnors on
morguefile.com
yes.
Bertrand Delacretaz, October 2013

26. obstacles

27. we're in the
same office
photo by allclasswork on morguefile.com

28. my code
is not finished
photo by beglib on morguefile.com

29. mistakes
in public...
photo by xenia on morguefile.com

30. Shared vision
benefits
Real-time status updates
Broadcast help requests
Searchable archives
pictures from morguefile.com
http://morguefile.com/license/morguefile/
Bertrand Delacretaz, October 2013

31. In summary...
this works!
reading list:
https://delicious.com/bdelacretaz/opendevelopment