Is an AS-IS Workflow Diagram a requirement? This question recently came up in an IIBA Business Analysis Body of Knowledge core team meeting. Everyone’s first reaction was no, or of course not. It is an AS IS. I think that most people would say no because an “AS IS” is a currently implemented process or procedure. This brings up an interesting question: are requirements only things that have not been implemented? The definition of a requirement from the BABOK is “. . . a condition or capability needed by a stakeholder to solve a problem or achieve an objective.”
Just because a process or procedure has been successfully implemented (AS IS WORKFLOW), is it no longer a requirement? If the process was broken or was interrupted somehow would it then become a requirement again? And when we talk about requirements management, aren’t we including the ongoing management of requirements after they have been implemented?
To me, all of these issues support the inclusion of AS IS WORKFLOW Diagrams and descriptions in our list of requirements.
- Selecting a Vendor Package (COTS) - June 7, 2010
- When do you learn the business? - April 6, 2010
- Free podcast on Application Modernization - March 15, 2010
- IIBA and Business Rules Community 2010 Conference - January 11, 2010
- BAs NEED management support - December 4, 2009
- WIBADD is really Great!! - October 22, 2009
- Why status reports? - September 25, 2009
- BA Interns - July 20, 2009
- Who performs business analysis work in your organization? - June 26, 2009
- User Stories - April 14, 2009