I have recently read Software Creativity 2.0 by Robert L. Glass. It's a great book dealing with being creative in the development process.
- Are discipline and formality at odds with flexibility and agility?
- When are control-driven vs. experimentation-driven approaches most effective?
- Can we "make creativity happen" in a software organization?
- Which is more important, process or product?
- How do theory and practice interact in the software field? Can practitioners and academe complement each other more effectively?
- Is there a missing link between creativity and software design?
- What is the balance of "intellectual" and "clerical" tasks in software work?
- Can we still find a place for plain old fun?
Can you recommend any other good books dealing with the same issues?