Friday, December 18, 2009
Your Own Experience
Your Own Experience
Your best bet is to collect some data on how much
of your own project effort is spent on requirements development and to
judge how well that has worked for you in the past. (See Chapter 22, "Measuring Requirements.")
Use this historical data when estimating the requirements effort needed
for future projects. Adjust your initial estimate by using the
considerations in Figure 4-1 to compensate for differences between your next project and the benchmark
projects. Consider any additional factors that would influence your own
project. You might weight each of the factors shown in Figure 4-1
on a scale of 0 (no effect) to 5 (major impact). This analysis can help
you spot risk factors that could prolong your requirements development
work.
Another factor to consider is the development life
cycle that the project is following. Not all the requirements effort
should be allocated to the beginning of the project, as is the case in
the sequential or waterfall life cycle. Don't think in terms of a
discrete "requirements phase," but rather about a set of
requirements-related activities that span the project's life cycle. In
particular, requirements management will be performed on an ongoing
basis once a set of requirements is baselined and change requests begin
to appear.
No comments:
Post a Comment