The Project Coach

In previous articles we’ve discussed requirements from several viewpoints.  We’ve examined the characteristics and attributes of good requirements and differentiated them from business rules.  We’ve discussed the merits of developing requirements in a cascading fashion from business goals through related objectives to enable prioritization.  We’ve also looked at techniques and templates to aid in remembering categories of requirements to explore.  Requirements are so important a topic I could probably discuss them for weeks, and who knows maybe I just will.  Requirement documents can take on many fashions and styles and this week’s focus will be common formats for their expression and capture. › Continue reading…

In our previous 2 articles, we’ve discussed how business requirements should originate in a cascading manner from goals and objectives, to assist in assigning their relative priorities.  We also reviewed tools that can be leveraged to help us remember the different areas or categories of requirements to capture.  But now let’s step back and consider, just what is a requirement anyway, and what is it not?  › Continue reading…