by Stewart Mednick President Emeritus IIBA Minneapolis St Paul Chapter Functional Decomposition Feature User Story Acceptance Criteria Process Flow User Story User Story Acceptance Criteria ID: 776018
Download Presentation The PPT/PDF document " The Requirement Continuum" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Slide2The Requirement Continuum
by
Stewart
Mednick
President Emeritus
IIBA Minneapolis St. Paul Chapter
Slide3Functional Decomposition
Feature
User Story
Acceptance Criteria
Process Flow
User Story
User Story
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Requirement Continuum
An iterative requirement lifecycle
Slide4The Hedgehog Concept
Are you a
hedgehog
or a
fox
?
In his famous essay “The Hedgehog and the Fox,”
Isaiah Berlin
divided the world into hedgehogs and foxes, based upon an ancient Greek parable:
“The fox knows many things, but the hedgehog knows one big thing.”
The Hedgehog Concept is developed in the Jim Collins’ book “Good to Great.” A simple, crystalline concept that flows from deep understanding about the intersection of three circles:
what you are deeply passionate about,
what you can be the best in the world at, and
what best drives your economic or resource engine.
Slide6Transformations from good to great come about by a series of good decisions made consistently; supremely well executed, accumulating one upon another over a long period of time.
with a Hedgehog
Concept:
Slide7Collins defines the Hedgehog Concept as such:
“All good-to-great leaders, it turns out, are hedgehogs.
They know how to simplify a complex world into a single, organizing idea — the kind of basic principle that unifies, organizes, and guides all decisions….
Slide8Collins defines the Hedgehog Concept as such:
…That’s
not to say hedgehogs are simplistic. Like great thinkers, who take complexities and boil them down into
simple, yet
profound
ideas
(Adam Smith and the invisible hand, Darwin and evolution), leaders of (in) good-to-great companies develop a Hedgehog Concept that is simple but that reflects penetrating insight and deep understanding.”
Slide9What you can be the best in the world at: Product Development (Macro Level)
What are you deeply passionate about:
BA Education and
Knowledge
What drives your economic engine:
Process Rigor
BA Hedgehog
Slide10What are you deeply passionate about:
BA Education and knowledge
What drives your economic engine:
Process Rigor
What you can be
the best in the world at: Requirement Development (Micro Level)
BA Hedgehog
Slide11BA Education, Knowledge and execution
Process Development, Rigor and execution
Product
Development, testing and implementation
Good Process
Good Product
Repeatability
Success
BA Hedgehog
Slide12BA Education, Knowledge and execution
Process Development, Rigor and execution
Requirement
Development, testing and implementation
Good Process
Good Product
Repeatability
Success
BA Hedgehog
Slide13Transformations from good to great come about by a series of good decisions made consistently with a Hedgehog Concept, supremely well executed, accumulating one upon another, over a long period of time.
The
Requirement Continuum
is a tool to be used to help execute supremely well.
Slide14Syllogism:
To make good decisions, good (relevant) questions need to be asked. To determine what questions are relevant, the purpose of why a question needs to be asked is known. The reason a purpose exists, is because a business need has to be fulfilled. What is that business need?
Slide15Functional Decomposition
Feature
User Story
Acceptance Criteria
Process Flow
User Story
User Story
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Requirement Continuum
An iterative requirement lifecycle
Slide16Insert Solution ArchitectInsert System AnalystInsert Implementation TeamInsert Waterfall jargon
Functional Decomposition
Feature
User Story
Acceptance Criteria
Process Flow
User Story
User Story
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Requirement Continuum
An iterative requirement lifecycle
Slide17Insert Solution ArchitectInsert System AnalystInsert Implementation TeamInsert Waterfall jargon
Functional Decomposition
Feature
User Story
Acceptance Criteria
Process Flow
User Story
User Story
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Will define the feature on the lowest level of the Functional Decomposition; business domain
Requirement Continuum
An iterative requirement lifecycle
Slide18Functional Decomposition
Slide19Insert Solution ArchitectInsert System AnalystInsert Implementation TeamInsert Waterfall jargon
Functional Decomposition
Feature
User Story
Acceptance Criteria
Process Flow
User Story
User Story
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Functional Review or Exploratory Testing to find errors or impact issues
Requirement Continuum
An iterative requirement lifecycle
Slide20Insert Solution ArchitectInsert System AnalystInsert Implementation TeamInsert Waterfall jargon
Functional Decomposition
Feature
User Story
Acceptance Criteria
Process Flow
User Story
User Story
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Delivery Team Develops the process; QA validates (verify process) and tests.
Requirement Continuum
An iterative requirement lifecycle
Slide21Insert Solution ArchitectInsert System AnalystInsert Implementation TeamInsert Waterfall jargon
Functional Decomposition
Feature
User Story
Acceptance Criteria
Process Flow
User Story
User Story
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Check and balance for structural design; traceability
Requirement Continuum
An iterative requirement lifecycle
Slide22Insert Solution ArchitectInsert System AnalystInsert Implementation TeamInsert Waterfall jargon
Functional Decomposition
Feature
User Story
Acceptance Criteria
Process Flow
User Story
User Story
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Acceptance Criteria
Check and balance for structural design; traceability
Delivery Team Develops the process; QA validates (verify process) and tests.
Will define the feature on the lowest level of the Functional Decomposition; business domain
Functional Review or Exploratory Testing to find errors or impact issues
Requirement Continuum
An iterative requirement lifecycle
Slide23The Requirement Continuum will present a Requirement Development Life Cycle that can be used in an Agile or Waterfall environment.Starting initially with a Functional Decomposition of the system (or capability) being analyzed or developed, taking the decomposition to the Feature level.These features will then be further developed by user stories that will provide acceptance criteria for the guardrails of what is considered complete and successful.
Requirement Continuum Key Points:
Slide24QA will validate and test the process in a prototype environment, and when validated, the delivery team can develop.The development time frame represents the end of sprint. Each sprint is defined by the user stories developed. Now more features can be created, more user stories will define the features, and the cycle continues until the project is complete; Thus, a requirement continuum.Implementing this process will provide consistency every time a requirement set is needed to be created.
Requirement Continuum Key Points:
Slide25Business Analysis is not absolute. There are no laws or legal precedence for what is considered proper business analysis. There is only a ‘suggested’ guideline; the BABOK. This is shaped and molded by the minds that contributed to its development. However, we can influence as well by creating a
transcendent idea
that frames a
meaningful design
, and establishes a
compelling force in Business Analysis
.
Slide26The End
Questions?
Or:
Comments, Philosophical observations,
Theoretical perspectives, Contentious objections,
thought provoking contributions,
or simply applauds of approval!