Eric Brechner
Author of I. M. Wright's "Hard Code": A Decade of Hard-Won Lessons from Microsoft
Works by Eric Brechner
Tagged
Common Knowledge
There is no Common Knowledge data for this author yet. You can help.
Members
Reviews
I. M. Wright's Hard Code (Best Practices) by Eric Brechner
I appreciated his insight into Microsoft's development organization. It added some soul and flesh to the behemoth that is usually depicted as soul-less. I especially appreciated the chapters dealing with management (both up and down) as this gave me further action items (and best practices) to deal with in my own organization.
Short, sweet, and to the point.
I've read other books on Kanban. This is, I think, the most practical of them. It doesn't spend a lot of time talking about theory. It doesn't spend a lot of time on case studies. Instead, it's a practical guide to using Kanban. As such, if you want to deeply understand why Kanban is so effective, or if you want to see how others are using it, it's not the right choice. But if you want something to point people at when they ask "How do I do this?", it's a great choice.
A slight detour into detail: One thing that this book emphasizes, which other presentations of Kanban don't, is that each column of your board needs to have its own done column. Done should not be indicated by moving something into the "in progress" column of the next section unless ready to be worked on. Without a separate done column for each section, it's harder to tell where the backlogs are.… (more)
I've read other books on Kanban. This is, I think, the most practical of them. It doesn't spend a lot of time talking about theory. It doesn't spend a lot of time on case studies. Instead, it's a practical guide to using Kanban. As such, if you want to deeply understand why Kanban is so effective, or if you want to see how others are using it, it's not the right choice. But if you want something to point people at when they ask "How do I do this?", it's a great choice.
A slight detour into detail: One thing that this book emphasizes, which other presentations of Kanban don't, is that each column of your board needs to have its own done column. Done should not be indicated by moving something into the "in progress" column of the next section unless ready to be worked on. Without a separate done column for each section, it's harder to tell where the backlogs are.… (more)
One of the best books I've read on software development. Practical advice on all manner of things from career development. code reviews, feedback skills. Leaves me hungry for in-depth case studies of Microsoft projects and processes.
Even though it is targeted at software managers, many of the chapters should be read by all managers regardless of domain.
Even though it is targeted at software managers, many of the chapters should be read by all managers regardless of domain.
Statistics
- Works
- 2
- Members
- 122
- Popularity
- #163,289
- Rating
- 4.0
- Reviews
- 4
- ISBNs
- 10