I really like a simple risk matrix as a visual aid, because it makes it much easier for me to explain of how severity and probability combine to make a risk more or less serious than if I tried to explain it with words alone.
“If we perceive our role aright, we then see more clearly the proper criterion for success: a toolmaker succeeds as, and only as, the users of his tools succeed with his aid. However shining the blade, however jeweled the hilt, however perfect the heft, a sword is tested only by cutting.”
– Fred Brooks
This is a particularly interesting quote when we consider our deliverables as analysts as tools to be used by designers, developers and QA analysts. The measure for our success is, in truth, inseparable from the success of those that use our work to accomplish theirs.
Sure, there are lots of benchmarks and checklists for the forms and aesthetics of good requirements documentation, but what is the benefit of meeting those criteria if we don’t put our delivery team members in a position to succeed?
With that in mind, how successful a toolmaker are you? In what ways could you improve so as to help those who will use what you produce be more successful?
What does IBM’s acquisition of Telelogic (Doors) mean to the future of both products? What does it mean for their users? I thought I’d share a recent article I came across that shows that IBM has made some progress in determining how they’ll leverage both products.
We don’t use SCRUM or XP in my shop, but I am always interested in learning more about other methods and tools, and I know some of my readers use these methodologies, so I thought I’d share some information on Sprintometer, a free SCRUM & XP project tracking tool.