Articles Blogs Humor TemplatesInterview Questions
If someone said you could only perform a single quality practice on a software project, what would you choose? I’d pick peer reviews of requirements, which I believe are the highest-leverage quality practice we have available today. In a peer review, someone other than the author of a work product examines the product for quality problems and improvement opportunities. Reviewing requirements is a powerful technique. Use them to identify ambiguous or unverifiable requirements, find requirements that aren’t sufficiently detailed yet, spot conflicts between requirements, and reveal numerous other problems.
The fact that software projects and tasks are reported to be “90 percent done” for a long time has become something of an industry joke. (A related joke states that the first half of a software project consumes the first 90 percent of the resources, and the second half consumes the other 90 percent of the resources.) This well-intentioned but misleading status tracking makes it difficult to judge when a body of work will truly be completed so you can ship the next product release to your customers. Here are several typical causes of “90 percent done” syndrome and a few possible cures.
Many professionals approach us after being unsuccessful in CBAP so we thought of doing some analysis to come up with the most common reasons of failure in CBAP.
There are many articles and blogs giving tips on how to pass the CBAP exam but on a first search, I didn't find any article explaining why people fail in CBAP. This will definitely help the CBAP aspirants to make sure that they don't repeat the mistakes.
brought to you by enabling practitioners & organizations to achieve their goals using: