I've recently managed to find time to read technical books again. In an attempt to "fix" the broken process at my job, I just finished reading a book on a process known as Feature Driven Development.
I really liked the information presented. Yet Another Process, but this one seems to be within the realm of practicality. There are good tips for where to focus and why, and how to effortlessly keep metrics and status etc.
The biggest problem I had (if you can call it a problem) is the focus on Domain Modeling. I'm all for it, and buy into what the book recommends, but I am having a hard time visualizing how to get that implemented in our organization.
Not that the organization would be against it, but just how to get the buy-in and support needed to properly complete the procedure.
To supplement the area of knowledge in Domain Modeling, I've now started reading Domain Driven Design. I really am enjoying this book as well.
Armed with the knowledge presented in these two books, I'm hoping to introduce some of these processes and methodologies into our organization.
Who knows... we could improve!
All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the Poster. The Rest © 1997-2008 SourceForge, Inc.