Having the best powerpoint presentation (thanks to Presentation Zen and Beyond Bullets, this is possible) is not sufficient to persuade. We have to craft personal messages. We have to be interactive, and adapt our presentations as we present - maybe even discard them entirely, and craft the key points of our messages into a conversation lead by the people to whom we are presenting.

I put together a candidate logo tonight - any feedback is welcome.

SteelTrace is targeted as a likely takeover candidate in this post from the Computer Business Review online. Borland (CaliberRM) and Teleologic (DOORS) are the most likely suitors identified in the article.

This post isn’t about composition of requirements. It is about using the object-oriented concept of composition when expressing requirements.
Composition is the notion that one object or entity is made up of multiple smaller objects. Grady Booch’s Object Oriented Analysis and Design with Applications (2nd Edition), is the de facto standard for learning about OO. [...]

When you launch a new software product, or start a new blog, or a website, one way to get the word out is by viral marketing.
Thanks to this post on the Presentation Zen website, I found a great presentation by Seth Godin here. Lots of good examples, from Google to the Macarena to the [...]

One of the key points that enables James’ approach is “tight collaboration” between the program manager and the developers. He talks about the miracles that can happen when you have this, as conversations can cause time to miraculously appear in the schedule. And his use of the toaster analogy is spot on.

I was reading ok-cancel today, and saw an article about getting UI designs ‘through the gauntlet’ of different groups of people at the client. Kevin and Tom consistently provide great insights on how to thrive in the HCI world, providing insights both in how to navigate customer-politics and processes, and in how to approach designing [...]

Btw, here’s a link to the article in CIO magazine, that I mentioned indirectly in my previous post about the requirements mess.  This really is a great article - it includes 3 case studies of how different CIOs dealt with the problems on their teams.

People who elicit and manage requirements – product managers, business analysts, program managers, and others – also orchestrate and communicate with their clients. In an enterprise software project, the requirements manager (RM from here on out) has to communicate with people across the client organization. To pass along information, gain support, and gather understanding. Plus [...]

An application lives or dies by its ability to allow users to achieve the goals that drive the creation of (or purchase of) the software.