Requirements vs. Design – Which is Which and Why
A classic debate. It comes up often. Unfortunately, it’s a source of confusion that causes many teams to shy away from staffing, creating, or managing any formal requirements processes. There’s a discussion on Seilevel’s forum where this has been brought up again, and it’s shaping up to be a fine grudge match here in Austin. Thanks to Cauvin for calling it to our attention. We can’t let the other folks have all the fun, so we’ll chime in too.
Software Requirements – Process and Roles
Our previous post, Requirements vs design – which is which and why, describes our position on which parts of the software development process are requirements-activities, and which parts are design activities. The debate among professionals about these distinctions is ongoing, and continues in the comments on that post. The length of the debate, combined with the skills of those debating demonstrates that it isn’t a black and white issue.
In this post, we will try and explore the reasons why this debate is ongoing. We will do that by exploring the symbolism of the terms involved, as well as the roles of different members of the software development team.
Top Ten Tips For Giving A Better Presentation
Guy Kawasaki wrote a great article last month about how to give a great presentation. You should be reading his stuff!
He goes into details about each of his ten eleven tips from his perspective. Here’s a quick summary of those tips with our thoughts.
I work for Guy Kawasaki, and I would like to thank you for your comments about Guy and his blog posting on presentations!
Mary-Louise
Online Assistant
http://blog.guykawasaki.com/
Mary-Louise@garage.com
How cool is that? Both Mary-Louise and Guy reached out to say thanks (in email too). That’s why he’s still on the A-list. He got there because of his reputation in the valley, but he’s stayed there because he deserves it.
Check out Guy’s blog. Great Stuff! (linked in Mary-Louise’s comment)