Six Stages in the Evolution of a Business Requirement
Six Stages in the Evolution of a Business Requirement
Business requirements exist in the wilds of organizations around the world. At least, that is our theory. They roam through the hallways and offices, hiding in the minds of business managers and subject matter experts, waiting to spring on the unsuspecting developers or analysts when they can do the most harm. There were times when they were thought to be extinct, in particular just before the "Y2K" scare where they were reduced to the single concept, "Thou shall know thy century". There are also many people who are trying purposely to eradicate the entire concept of business requirements. Yet they survive, often waging war on their close relatives, system requirements (often called by their pseudonym, "Technical Specifications"). It appears to be very difficult for these two entities to coexist. Perhaps they need a mediator to initiate peace talks aimed at allowing both sides to exist in their own separate, albeit connected, little universes. We propose that the role most qualified for this task is the role we refer to as "Business Analyst".
Requirements Captured
Remember that this is just a theory. We do not really know whether business requirements exist at all until we capture them. Only then can we recognize them for what they are. Only then can we work with them, tame them, make them work for us, which is only right and just. It is their purpose in life. Only when they have been tamed can they truly fulfill their destiny, to define the business need of those business managers and subject matter experts in words that the information technology professionals can understand and use to develop a technology solution that meets those needs. But how can we, those responsible for defining business needs, tame these wild beasts? The answer: one step at a time. For starters, you have to capture them. The key to capturing the business requirement is not to worry about what it looks like (looks can be deceptive) or whether it is a legitimate requirement or not. The process of taming it, when followed rigorously, will ultimately reveal its true nature. The technical name for this stage in the life of the business requirement is "Captured".
Stage: Sentenced!
Once the business requirement has been captured, we can begin to nurse it along, trying to help it achieve its full potential. To that end, we have to state it in a simple, complete, well-structured sentence that:
- states one thing and states it well;
- does not contain conjunctions (and, or, …);
- contains subject, verb, object and appropriate modifiers;
- does not depend on other sources of information; and
- defines a feature, function, fact, or behavior that the future business solution has to enable, execute, enforce, or exhibit.
Only when the business requirement meets these 5 criteria can we definitively state that it has advanced to the stage in its evolution technically referred to as "Sentenced".
Stage: Whatified!
The next stage in the process of taming the business requirement requires that we establish whether it is a legitimate business requirement or a technical specification in disguise. To do this, we need to ensure that it states "what" should be done, not "how" to do it by:
- avoiding preconceived solutions;
- describing business logic (rules) independent of the technology; and
- expressing the what (destination), not the how (journey).
At this time, we can maintain that the young requirement has reached a state in its development that experts refer to as "Whatified".
Stage: Scoped!
Once a requirement is "Whatified", we need to weed out those business requirements that do not really "fit in". During the hunt, we were being careful not to scare off any potential "real" business requirements. As a result, we now have captured some business requirements that we do not actually need. To test the validity of each business requirement in our herd (official statement: requirements come in herds), we now need to evaluate whether it targets components that are in scope for your project in that:
- it focuses on a desired behavior or feature of one or more components of the business system; and
- you have the authority to implement it without impacting out-of-scope components.
If the business requirement survives this critical step, we maintain that it is now "Scoped".
Stage: Clarified!
Now that our timid, frightened, little business requirement is starting to evolve, we have to make sure that it can survive the threats that the development community poses. Remember, that is not the requirement’s natural habitat, so we have to give it the resources it needs to be able to move into that which is often perceived as hostile terrain. The best protection we can provide the business requirement is to ensure that it is understandable, unambiguous, and clear by proving that:
- it is understandable to "knowledge peers";
- all terms have been revised, defined, and/or clarified; and
- it has a single meaning in the context of the subject area.
To indicate the strengthened state of the business requirement at this stage in its life, we can now claim that it has reached the state of being "Clarified".
Stage: Quantified!
An additional defense mechanism that we can protect the business requirement with to help it survive the development process is to test whether or not it is objectively measurable by:
- clearly stating functional and informational dimensions;
- referring to business rules for specific values; and
- defining performance in measurable terms.
If the business requirement can pass these tests, we can now confer upon it the title of "Quantified".
Stage: Confirmed!
Now that we have trained the young business requirement and given it all of the skills it needs to survive, we are ready to allow it to rejoin others of its kind. A single business requirement does not exist in isolation, it has no value alone. To provide true value, to achieve their full potential, we need to allow – nay, we need to encourage business requirements to form groups within their herd. Only in the herd can the individual bloom. To fit into the society of business requirements that define a coherent business solution that can be supported by technology, the individual business requirement now needs to become one of a consistent, non-redundant, complete set of prioritized statements that:
- neither repeats nor contradicts any other requirements;
- is prioritized to ensure that the most important requirements are delivered first; and
- defines what you need or want and what you don’t need or don’t want.
Then, and only then, can we confer upon the business requirement that we captured, sentenced, - whatified, clarified, and quantified the hallowed state of "Confirmed".
Future Stages
We do not want to mislead you, dear reader, there are further stages in the evolution of this thing we call a business requirement. Notably, it will ultimately need to be tracked, probably modified, implemented, verified, and maintained before its effective life span ends. The term voted most-likely-to-define the well-behaved business requirement throughout these final transitions is the exalted state we call "Managed". But the journey from "Confirmed" to "Managed" is an arduous trip that exceeds the scope of today’s tirade. It might, however, just prove to be important enough to be described another day.
Six Stages in the Evolution of a Business Requirement - To learn more about this author, visit Tom Hathaway's Website.
Like this article? Share it with your friends
Requirements in the Wild
Business requirements exist in the wilds of organizations around the world. At least, that is our theory. They roam through the hallways and offices, hiding in the minds of business managers and subject matter experts, waiting to spring on the unsuspecting developers or analysts when they can do the most harm. There were times when they were thought to be extinct, in particular just before the "Y2K" scare where they were reduced to the single concept, "Thou shall know thy century". There are also many people who are trying purposely to eradicate the entire concept of business requirements. Yet they survive, often waging war on their close relatives, system requirements (often called by their pseudonym, "Technical Specifications"). It appears to be very difficult for these two entities to coexist. Perhaps they need a mediator to initiate peace talks aimed at allowing both sides to exist in their own separate, albeit connected, little universes. We propose that the role most qualified for this task is the role we refer to as "Business Analyst".
Requirements Captured
Remember that this is just a theory. We do not really know whether business requirements exist at all until we capture them. Only then can we recognize them for what they are. Only then can we work with them, tame them, make them work for us, which is only right and just. It is their purpose in life. Only when they have been tamed can they truly fulfill their destiny, to define the business need of those business managers and subject matter experts in words that the information technology professionals can understand and use to develop a technology solution that meets those needs. But how can we, those responsible for defining business needs, tame these wild beasts? The answer: one step at a time. For starters, you have to capture them. The key to capturing the business requirement is not to worry about what it looks like (looks can be deceptive) or whether it is a legitimate requirement or not. The process of taming it, when followed rigorously, will ultimately reveal its true nature. The technical name for this stage in the life of the business requirement is "Captured".
Stage: Sentenced!
Once the business requirement has been captured, we can begin to nurse it along, trying to help it achieve its full potential. To that end, we have to state it in a simple, complete, well-structured sentence that:
- states one thing and states it well;
- does not contain conjunctions (and, or, …);
- contains subject, verb, object and appropriate modifiers;
- does not depend on other sources of information; and
- defines a feature, function, fact, or behavior that the future business solution has to enable, execute, enforce, or exhibit.
Only when the business requirement meets these 5 criteria can we definitively state that it has advanced to the stage in its evolution technically referred to as "Sentenced".
Stage: Whatified!
The next stage in the process of taming the business requirement requires that we establish whether it is a legitimate business requirement or a technical specification in disguise. To do this, we need to ensure that it states "what" should be done, not "how" to do it by:
- avoiding preconceived solutions;
- describing business logic (rules) independent of the technology; and
- expressing the what (destination), not the how (journey).
At this time, we can maintain that the young requirement has reached a state in its development that experts refer to as "Whatified".
Stage: Scoped!
Once a requirement is "Whatified", we need to weed out those business requirements that do not really "fit in". During the hunt, we were being careful not to scare off any potential "real" business requirements. As a result, we now have captured some business requirements that we do not actually need. To test the validity of each business requirement in our herd (official statement: requirements come in herds), we now need to evaluate whether it targets components that are in scope for your project in that:
- it focuses on a desired behavior or feature of one or more components of the business system; and
- you have the authority to implement it without impacting out-of-scope components.
If the business requirement survives this critical step, we maintain that it is now "Scoped".
Stage: Clarified!
Now that our timid, frightened, little business requirement is starting to evolve, we have to make sure that it can survive the threats that the development community poses. Remember, that is not the requirement’s natural habitat, so we have to give it the resources it needs to be able to move into that which is often perceived as hostile terrain. The best protection we can provide the business requirement is to ensure that it is understandable, unambiguous, and clear by proving that:
- it is understandable to "knowledge peers";
- all terms have been revised, defined, and/or clarified; and
- it has a single meaning in the context of the subject area.
To indicate the strengthened state of the business requirement at this stage in its life, we can now claim that it has reached the state of being "Clarified".
Stage: Quantified!
An additional defense mechanism that we can protect the business requirement with to help it survive the development process is to test whether or not it is objectively measurable by:
- clearly stating functional and informational dimensions;
- referring to business rules for specific values; and
- defining performance in measurable terms.
If the business requirement can pass these tests, we can now confer upon it the title of "Quantified".
Stage: Confirmed!
Now that we have trained the young business requirement and given it all of the skills it needs to survive, we are ready to allow it to rejoin others of its kind. A single business requirement does not exist in isolation, it has no value alone. To provide true value, to achieve their full potential, we need to allow – nay, we need to encourage business requirements to form groups within their herd. Only in the herd can the individual bloom. To fit into the society of business requirements that define a coherent business solution that can be supported by technology, the individual business requirement now needs to become one of a consistent, non-redundant, complete set of prioritized statements that:
- neither repeats nor contradicts any other requirements;
- is prioritized to ensure that the most important requirements are delivered first; and
- defines what you need or want and what you don’t need or don’t want.
Then, and only then, can we confer upon the business requirement that we captured, sentenced, - whatified, clarified, and quantified the hallowed state of "Confirmed".
Future Stages
We do not want to mislead you, dear reader, there are further stages in the evolution of this thing we call a business requirement. Notably, it will ultimately need to be tracked, probably modified, implemented, verified, and maintained before its effective life span ends. The term voted most-likely-to-define the well-behaved business requirement throughout these final transitions is the exalted state we call "Managed". But the journey from "Confirmed" to "Managed" is an arduous trip that exceeds the scope of today’s tirade. It might, however, just prove to be important enough to be described another day.
Six Stages in the Evolution of a Business Requirement - To learn more about this author, visit Tom Hathaway's Website.
Like this article? Share it with your friends
| |||
 |
No article feedback found. | ||
|
Leave Your Feedback | ||
|
|||
 Six Stages in the Evolution of a Business Requirement
| |||
| Business requirements exist in the wilds of organizations around the world. We do not really know whether business requirements exist at all until we capture them. To ensure the safety of the business community and... |
|||
|
Why Transformation Efforts Fail
| |||
| Why change initiatives, whether they were intended to boost quality, efficiency, sales or profitability, or reverse business spiral usually only generate lukewarm results or fail. |
|||
|
Website Evolution – Which Stage is Right for You?
| |||
| Lately I’ve been talking a lot about websites. Large, small and in-between. And it has become very clear to me that for all businesses there are a number of stages – or ‘evolutions’ - you can progress through when d... |
|||
|
The 7 Stages of a Referral Generation
| |||
 Referrals happen, thank goodness, but for too many, they happen randomly, almost accidentally. |
|||
|
A SHARPER MIND/BRAIN --(To Reduce Stress Level)
| |||
| Many studies have underlined the importance of exercise in reducing stress level. Studies also show that aerobic exercise is an excellent way of keeping our brains young and healthy. |
|||
| |||
David BarrDavid Barr is the President of Venture Opportunities, Inc. David has been a professional business broker/intermediary since 1980 focusing on General Business Brokerage and Mergers and Acquisitions representing client transaction value from $400,000 to $20,000,000. Mr. Barr has handled the sale of over four hundred and fifty companies. David earned a university degree from the State University of New York majoring in economics and business. David holds the Mergers and Acquisition Master Intermediary and the Certified Business Intermediary designations from the International Business Brokers Association. He is also a Senior Business Analyst and a Texas licensed Real Estate Agent. For more information about David and Venture Opportunities, visit www.bizdealmaker.com. - Visit David Barr's Website |
|||
Jeff FosterWebBizIdeas.com is a Minneapolis website design company founded to help people start an internet business by providing them with website, business, and internet resources that help foster the growth of successful online businesses and develop innovative Internet business ideas. - Visit Jeff Foster's Website |
|||
Anne BarrAnne Barr has over 26 years experience in sales and marketing, six years as a franchisee. She has assisted over 367 business owners and purchasers to achieve their goals in career change, transition and exit strategy. She holds the designation of Certified Franchise Executive from the International Franchise Association, Certified Business Intermediary from the International Business Brokers Association and Board Certified Broker from the Texas Association of Business Brokers. Anne is active in professional organizations, networking groups and volunteers for non-profit entities. As owner/operator of four successful businesses, Anne has proven people skills and enjoys helping clients find the right "fit" in business ownership. Visit www.FranchiseOpportunitySpecialist.com for more information about me and my company. - Visit Anne Barr's Website |
|||
Casey GollanCasey Gollan, Business Coaching & Mentoring Programs. Add $1 Million to $10 Million in the next 1 to 3 years. Since 1996 Casey has to added hundreds of millions of dollars to businesses. Watch a free video see client results Business Coaching website. - Visit Casey Gollan's Website |
|||
Kim CastleWith nearly two decades in the advertising and design business, with clients like Domino's Pizza, General Motors, Direct TV, Pedigree, Wolfgang Puck, Higher Octave Music, Hollywood Celebrity Products, Disney, and Paramount, as well as thousands of entrepreneurs around the world define, structure, communicate, and position their business for greater profits, BrandU(R) co-creators Kim Castle and W. Vito Montone discovered that entrepreneurs could experience the same power that big brands command for a fraction of the cost with the world's only process-based results-drive Integral approach to business creation. BrandU(R) is helping entrepreneurs grow with the power of extreme clarity from idea...to brand...to market(TM) and helping one million entrepreneurs become successful and whole so that they can make a difference in the world. Are you one of them? If you want to experience clarity all the way to the bank(TM), get started now at http://www.brandu.com. - Visit Kim Castle's Website |
|||
Bernard ReberBack in late 1992, MS Access hit the streets. About that time the company I managed needed new software to handle their growing client base and I decided to try this new product. I had little difficulty writing and adapting a database to suit us and discovered a hidden talent for programming. A business was born. With business studies and 25 years of management experience in three different countries under my belt, I could offer a unique combination of skills and my customers agreed. From these humble beginnings my software 'invoiceit' emerged in 1999 and has since been taken to 49 states (hello Wyoming, won't you join us?), all across Canada and more than 70 other countries. From the very beginning the program included cashbook accounting, the simplest form of keeping financial business records. The Dictionary.com defines 'cashbook' as "A 'book' in which to record money received and paid out". For 'book' substitute 'simple software' and that's what I'm about. Now I have published Simple Accounting, an inexpensive spreadsheet solution which even you can master. For just $14.95 it costs less than a takeout meal! More at http://www.scrambled-card.com/simple_accounting_main.htm - Visit Bernard Reber's Website |
|||
Dr. John OdaJohn Oda Ph.D NLP is a business peak performance expert, an author, and speaker frequently called upon to provide corporate training, workshops and seminars for many companies in the United States. He is an expert in coaching sales and business professionals in overcoming the behaviors and obstacles that may impede their sales results and affect their bottom line. Since 1995, John has created a speaking bureau such topics, which include: time management, sales training, human diversity, leadership programs and etc. He provides companies with a strategic plan to increase their bottom line by over 25 percent yearly. - Visit Dr. John Oda's Website |
|||
Leanne Hoagland-SmithAre your sales where you want them to be? Will you be one of the few who achieves sales or business success or one of the many who have failed to change? Are you tired of being told you are like everyone else? Then you may find my first book on sales of interest. Be the Red Jacket in the Sea of Gray Suits, The Keys to Unlocking Sales available at Amazon or at http://www.processspecialist.com/red-jacket.htm. This book is a reflection of my no-nonsense approach to improving sales to overall business results. If you are truly committed to making sustainable changes, then I can help you secure a positive return on your investment because I focus on executable solutions not telling you the problems you already know you have. From training to corporate (group) coaching to executive one on one coaching, my approach is to assess, create awareness, build a goal driven action plan and then execute. The bottom line question is "Not do you or your employees know it, but do you or they want to do it?" Please call for a free strategy session at 219.759.5601. - Visit Leanne Hoagland-Smith's Website |
|||
|
To learn more about the Evan Elite Author Program please contact us. | |||
 | |
 Tom Hathaway (Visit Tom's Website) Mr. Hathaway has over 30 years experience as a practitioner and instructor in business information systems. He has successfully facilitated over 300 accelerated JAD (Joint Application Development) sessions dealing with mainframe, client/server and web-based applications in the US, Canada and Europe. In the early 1990’s, Tom pioneered the use of interactive CASE technology in JAD sessions (iJAD) to create in-session documentation of business requirements (InstaDoc™). As an instructor, he has developed and presented hundreds of seminars to thousands of participants on Business System Analysis, SDLC, Testing, and JAD Facilitation. Tom co-founded and co-manages the Requirements Solutions Group, a Tampa-based organization that provides training and consulting in business analysis and requirements definition. Throughout his career, Tom's major focus has been developing, using and teaching tools and techniques for increasing the quality and accelerating the delivery of information technology solutions that meet the needs of the business community. His talent for analyzing and synthesizing has resulted in original contributions to the industry’s body of knowledge.
|  |
 |
|
|
 |
|
|
|
 |
| Modeling the Masters: Learn the true secrets behind Walt Disney's business success factors & grow your company! Video produced by Phanta Media |
|
|
 |
| Have you written articles that would be of value to entrepreneurs? Become an expert on our site by publishing them! Expose yourself to a wide audience, drive more traffic to your website and get more sales! Click Here for details. |
 |
 | ||
|
||
|
||
|
||
|
| ||
|
|
|
Get advice & tips from famous business owners, new articles by entrepreneur experts, my latest website updates, & special sneak peaks at what's to come!
|
|
|
 |
 3 Networking Skills Disappearing Leader How To Get Media Attention Power of Concentration 100 Success Tips |
|
 | ||
 |
Choose A PR Topic
Press Release Builder | |
 |
Top 50 Business Plans
Top Business Plan Blogs | |
| ||
 |
|
|
|
|
|||||||||||||||||||||||||||
 |
|
|
||||||||||
