Comments on: Collective Ownership A research from Microsoft about code ownership: [...] #AltDevBlogADay — Collective Ownership by Julien Hamaide “When you share something, aren’t you more careful about it? Wouldn’t you be ashamed of damaging a share good? If you would, you are ready for collective code ownership. Let’s put some context : Fishing Cactus is a small studio that not only makes games, but also advergames and medical serious games. With a small team of no more than 10 programmers and 3 projects running at the same time, there’s no places for an engine team, a tool team,… The flexibility of the team is really essential for managing day-to-day needs in projects. Collective ownership can be defined as : Nobody owns a piece of code, no one is responsible alone of a piece of code. In other words, code I wrote yesterday could be changed by anyone today.” [...] [...] #AltDevBlogADay — Collective Ownership by Julien Hamaide “When you share something, aren’t you more careful about it? Wouldn’t you be ashamed of damaging a share good? If you would, you are ready for collective code ownership. Let’s put some context : Fishing Cactus is a small studio that not only makes games, but also advergames and medical serious games. With a small team of no more than 10 programmers and 3 projects running at the same time, there’s no places for an engine team, a tool team,… The flexibility of the team is really essential for managing day-to-day needs in projects. Collective ownership can be defined as : Nobody owns a piece of code, no one is responsible alone of a piece of code. In other words, code I wrote yesterday could be changed by anyone today.” [...]

]]>
By: Tweets that mention Collective Ownership » #AltDevBlogADay -- Topsy.com/2011/02/17/collective-ownership/#comment-844 Tweets that mention Collective Ownership » #AltDevBlogADay -- Topsy.com Thu, 17 Feb 2011 11:12:29 +0000 #altdevblogaday [...]

]]>