Categories
Document Management Rapid JAD

Getting It Right

Facebooktwittergoogle_plusredditpinterestlinkedinmail

by Erik Jul

When specifying requirements for a new system, large or small, how much do we have to get right?

Isn’t “All of it” the right answer?

Not always, and maybe never.

Concepts such as “minimally viable product” (which carries the moniker MVP as if it were some sort of champion), “iterative solution scoping,” and “progressive elaboration” decry the notion of completeness and possibly even that of correctness.

Of course, no one wants to deliver, or attempt to use, a system that does not work or is ill-suited to the task. So “getting it right” must matter to some degree: the system must work as specified.

But how much of what the user needs or wants has been identified and correctly specified in functional and other requirements? And of that, how much was correctly implemented?

Relying upon a Six Sigma approach (a methodology driving toward six standard deviations between the mean and the nearest specification limit) may reduce defects, but may still fall short of identifying a customer’s true problem and its best solution.

Lean, Lean Six Sigma, Agile, and the Three Amigos Scrum Alliance. These, plus approaches already forgotten or yet to be proposed, try to help us “get it right.”

In successive waves of innovation and reinvention, practitioners attempt to narrow the gap between what’s needed, what’s specified, what’s delivered, and what solves the customer’s problem.

Along that path, from problem to solution (scope, time, and cost notwithstanding), the professional solutions team—sponsor, business owner, project manager, business analyst, QA /tester, solution architect, developer, trainer, change management lead—all focus on “getting it right.”

Common software development and project management practices such as change requests, expectation management, phased releases, bug fixes, cumulative updates, and new versions testify that “getting it right” remains a noble goal seldom reached and maybe never reasonably expected.  For now, these are our best tools for getting it right, eventually.

To increase the likelihood of getting more right now rather than eventually, try these Rapid JAD principles: Capture Now, Document Once, Visible to All, and Revise Quickly.

Simple. Proven. Effective.

How much do you want to get right?

 

Facebooktwittergoogle_plusredditpinterestlinkedinmail