Just as there is no one right programming language for every application, there is no one right way to develop the more detailed specifications. Different environments call for different techniques, and the requirements managers and requirements writers will probably need to develop a mix of skills suited to various circumstances.
The team’s development process defines who is doing what, when, and how. In the waterfall model, software activities proceed through a sequence of steps, with each step based on the activities of the previous step. The spiral model begins with a series of risk-driven prototypes, followed by a structured waterfall-like process. The iterative approach, a […]
Why can we not allow for a process that creates detailed requirements and design information for each feature so that we can create more meaningful estimates? Isn’t that the professional way to approach the problem? If the schedule provides time for more detailed estimating at this time, by all means do it! However, we believe […]
In many projects, in order to provide a reasonable probability of success, it will be necessary to reduce the scope by as much as a factor of two.
One of the most frustrating, pervasive, and seemingly downright sinister problems in all of application development is the “Yes, But” syndrome, being the observation of the users’ reaction to every piece of software I have ever developed. For whatever reason, I always observe two immediate, distinct, and separate reactions when the users see the system […]
As Boehm points out in the COCOMO cost estimation model, the capability of the team has the greatest impact on software production. Davis supports this conclusion in his discussion of team productivity: “optimizing the productivity of all individuals does not necessarily result in optimizing the productivity of the team”. So, it seems logical to invest […]
Problems and opportunities are just flip sides of the same coin; In the IT industry your problem is my opportunity. It’s just a matter of perspective.