This post originated from an RSS feed registered with Java Buzz by Michael Cote. Original Post: Some Items from Org Patterns Feed Title: Cote's Weblog: Coding, Austin, etc. Feed URL: https://cote.io/feed/ Feed Description: Using Java to get to the ideal state. Latest Java Buzz Posts Latest Java Buzz Posts by Michael Cote Latest Posts From Cote's Weblog: Coding, Austin, etc.

I've finally gotten around to read through the org patterns stuff. It's been around a long, long time (you know, "long" for the coding world. It's being released in book-form as Organizational Patterns of Agile Software Development.

I'm not so sure that it's exclusively Agile -- it seems like that's in every project management book title now-a-days. But, anyhow, here's some patterns I've come across so far that are good readin':

• Build Prototypes - everyone knows building prototypes is good. What's nice about this writeup is that is draws clear boundaries for what a prototype should do, and when you should do them.
• Take No Small Slips - it's better, psychologically, to take one large schedule slip than many small ones:

  A single large slip is important for the morale of the team. If you continually take small slips, nobody believes the schedule any more. This hurts morale, the sense of urgency fades, and people stop caring. On the other hand, a single large slip preserves at least some of the believability of the schedule, and people are more willing to work toward the revised schedule.

• Private World - I don't quite have this one figured out beyond the basic way you use CVS, or any revision control system. Even if it is that, though, it's a good explicit writeup of that major part of day-to-day development that's implicit.