The powerful Problem Pyramid™ is described as a
systematic disciplined way to accurately identify the business
need and value for any project.without necessitating a separate
Enterprise Analysis that often doesn't happen.
BABOK v2 implies that business needs are identified only
in a separate somewhat lofty pre-project Enterprise Analysis
that in reality seldom occurs as BABOK v2 envisions.
Introduces the author's Proactive Software Quality Assurance™
concepts that are being adopted in the forthcoming IEEE Std.
P730 for Software Quality Assurance and distinguishes quality
assurance from testing and other quality controls.
Identifies salepeople as perhaps the most fruitful requirements
constituency and describes a Value Selling Maturity Model
culminating in Breakthrough Value Maturity Level 5 –
REAL Customer Value Proposition.
Business Analysts (BAs) keep being taught unwise conventional
wisdom requirements models which destine their efforts to
disappointment. There’s a better model shown here.
Why most of what is called Value Selling fits within low-effectiveness
Levels one through four but fail to achieve breakthrough benefits
of Level 5 maturity.
This article was featured in the Dec. 18, 2008 issue of the
IT Metrics and Productivity Journal
http://www.compaid.com/
Dirty little secrets of Return on Investment (ROI) that
make many such determinations questionable and how to responsibly
guide objective decision making.
An expanded description of ways to analyze and improve the
REAL software process as well as some powerful good practices
that are likely to produce improvements without the analysis.
Go Pro's Proactive Testing™ methodology
spots numerous errors that conventional testing ordinarily
overlooks and yet also enables faster, cheaper, and better
software deliver.
Distinctions that make a difference: between software
requirements, that really are high-level design, and the REAL,
business requirements the design must satisfy to provide value.
Six-step disciplined tool for systematically defining
the REAL problem and the REAL, business requirements that
will solve the problem and provide value.
Because Proactive Testing™ identifies big risks
early, test plans dealing with the higher risks can be tested
not only more often, but earlier in the life cycle.
10 pitfalls that commonly affect the suitability of
ROI calculations and their usage, from simpler issues related
to the calculations themselves to the more difficult, and
often more important, issues of how ROI is interpreted and
used.
Go Pro's Proactive Testing™ methodology wins advocates
among users, managers, and developers who traditionally say,
"We don't need no stinkin' testing."
Testers
are challenged to know the requirements; but focusing on requirements
management addresses primarily form, whereas requirements content
provides the value
Development Models
often consider testing an afterthought, but there are models
that focus on testing. This month, we'll examine the V-Model
- but is it flawed, too? Part 1 of 4
The X Model purports
to fill the gaps left open by the V Model. But does it really
handle all the facets of development, such as hand-offs, frequent
builds and so on? Part 2 of 4
What part of
the system do you test first? The Proactive Testing Model helps
you prioritize, manage a project-level plan and steer clear
of risks. Part 4 of 4
Click here to see the correct Proactive
Testing Life Cycle diagram which should have been in the 'Proactive
Testing' article.
