This article has been born from a trend that I have seen gain traction over the past few years. People are building requirements matrices of sorts, and they are coming with MoCSoW associations. I think there is a disconnect, and I want to address it.
A requirement is something that is required. The term ‘requirements‘ has [...]
There are a million flavors of Issue and Task Logs. There are also a lot of nice software products out there to help you track bugs, manage work packages, and keep a tight grip on your project. However, some organizations have young PM/BA efforts and cannot afford or do not quite yet have the need [...]
Thoughts on 7 Good Practices for Modeling Software Requirements:
From http://www.stsc.hill.af.mil/crosstalk/2008/03/ - these are 7 “Good Practices for Modeling Software Requirements”:
I like the spirit of this. But for those who are in an Agile or XP environment, or for those who follow MSF, AUP, or other iterative frameworks, there are some things to consider. I [...]
I think they are great, as a guideline, but lay out a project plan in a Gantt chart over a 6 month period and then compare what you planned against what happened…
I like them in small timeboxes, as guidelines, generalizations without fine levels of detail. Nothing beats a whiteboard when you are in the trenches.
Otherwise, [...]
Okay, if you have read my other blog posts, particularly my post about developing a custom PM methodology, you know I am all about inputs and outputs.
This is, obviously, for traceability. When you are running your status meetings, leave with a list of Action Items. Disseminate the list so people are accountable and understand what [...]