Difference between revisions of "DREPD"

Latest revision as of 13:08, 8 April 2020

DREPD (alternatively known as Discover-Research-Envision-Plan-Do Cycle and DREPD cycle; also historically known as DRMP, Discover-Research-Model-Plan Cycle, DRMP loop, and DRMP method; hereinafter, the Method) is the iterative four-step method used to manage any enterprise effort that that enterprise effort in four consecutive batches: Discovery (D), Research (R), Envisioning (M), and Planning (P). The name of the Method is the abbreviation of four verbs: Discover, Research, Envision, Plan.

The Method is used in any development in two ways:

Being complex, the Method can serve as a canvas for the development cycle as a whole. In this case, one bigger complex Method may consist of a number of smaller Patterns, which are called basic; and
Being basic, the Method can serve as a layout for simple actions in new product development, problem solving, competitive strategy, business analysis, systems engineering, project management, etc. A combination of those basic Patterns can be presented as a complex Pattern.

In education, Bracka School also deploys the Method while building the curricula on multiple sets of four quarters, each of which represents one batch of the Method.

Components

Discovery

Main wikipage: Enterprise discovery

The first batch of the Method is Enterprise discovery. It includes all activities resulted in discovery of any data relevant to the further enterprise development. These data include some statement of the business need that is sought to be satisfied as the key outcome from that enterprise as a whole.

Research

Main wikipage: Enterprise research

The second batch of the Method is enterprise research. It includes all activities needed to process the data discovered in enterprise discovery in order to provide enterprise envisioning with detailed requirements for the future outcome from the Method.

Envisioning

Main wikipage: Enterprise envisioning

The third batch of the Method is enterprise envisioning. It includes all activities needed to conceptualize, design, scratch, model, map, plan, project, and/or detail the Method's outcome and/or finalize the architecture or layout for this outcome.

Planning

Main wikipage: Enterprise planning

The fourth batch of the Method is enterprise planning. It includes all activities needed to create and deliver the Method's outcome based on its architecture or layout made in enterprise envisioning.

Classifications

Classifications of the Patterns are tentative. Every Method has some agility and no Method can fully fall in one exact category. Thus, the taxonomies below serve to demonstrate various directions of various Patterns rather than precise classifications.

Basic vs complex

Ideally, a basic Method is any development pattern that doesn't include other Patterns. For example, a generic reply like "Oh, really?" in a common conversation can be considered as basic. The listener (a) listens (or discovers) to its conversational partner, (b) researches what he or she has said, (c) decides what to reply (or models the reply), and (d) delivers (or plans) it;
Ideally, a complex Method is any development pattern that includes other Patterns. For example, development of a new space ship requires millions should be considered as complex because it includes millions and millions basic Patterns.

Complete vs partial

Ideally, a complete Method is any development pattern that includes all four batches from enterprise discovery to planning. For example, a generic reply like "Oh, really?" in a common conversation can be considered as complete because the entry data for this reply was collected, researched, the reply was designed and delivered;
Ideally, a partial Method is any development pattern that doesn't include enterprise planning. This Method may or may not include enterprise envisioning if the Method includes enterprise research. This Method may or may not include enterprise research, but always include enterprise discovery. For example, development of a new space ship was ordered, but the project was stopped in the middle because of the lack of funding.

Transitional vs terminal

Ideally, a transitional Method is undertaken in order to get some deliverable, which will be used in some Method in the future. For instance, a traveler takes a taxi in hopes that his or her driver would give more information on what to visit in a city, which hasn't been known to him or her yet. The traveler's airplane is unexpectedly delayed for one day;
Ideally, a terminal Method is undertaken in order to get with some deliverable, which will not be used in the future by the undertaker. For instance, someone delivers a pack of generic Vitamin C to its buyer.

Predefined-deliverable vs unexplored-deliverable

Ideally, a predefined-deliverable Method is undertaken in order to get with some deliverable, which features are defined before the Method starts. For instance, someone needs to buy a pack of generic Vitamin C;
Ideally, an unexplored-deliverable Method is undertaken in order to get some deliverable, which features cannot be exactly defined before the Method starts. For instance, a traveler takes a taxicab in order to get to a city, which hasn't been known to him or her yet, because the traveler's airplane is unexpectedly delayed for one day and he or she is looking for ideas how to spend that "extra" day.

Deductive vs inductive

Ideally, a deductive Method is undertaken in order to create a concept out of other concepts and experiments. For instance, the Patern is created out of similar concepts such as PDCA and experiences;
Ideally, an inductive Method is undertaken in order to conduct an experiment. For instance, the Patern can be tested in any enterprise effort.

Applications

New product development, problem solving, competitive strategy, portfolio administration, business analysis, systems engineering, project management and many other concepts are built on the basic Patterns. Complete complex terminal Patterns seem to have strong correlations with other concepts as well.

In project management

With one exception of discovering a business need, which project deliverables shall satisfy, the complex Method can serve as a project management canvas itself. One or more the basic Patterns can be used in order to create or modify any output of any project management process such as a project charter, stakeholder register, acceptance criteria, etc.

Complex Patterns vs other development concepts

Although the table below is not intended to be complete, it addresses some tendencies and correlations between the complete complex terminal Patterns, on the one hand, and some other other development concepts, on the other hand:

Discovery		Research	Envisioning	Planning
Business need	Requirements data
Portfolio administration
Usually, c-level executives define the needs at the organizational level, as well as frontline managers at the lower levels and middle managers in between those levels	New product development
	Project management
	Systems engineering			Usually, project teams or functional departments execute implementations
	Business analysis		Solution architects or others can model the solution
Competitive strategy
Business need	Requirements data	Research	Envisioning	Planning
Discovery

In education

Bracka School has built its Septem Artes Administrativi curriculum on seven sets of four quarters. Each set is called quadrivium and designed around the Method.

Related concepts

Deductive DREPD.
Inductive DREPD.
Viable DREPD
Viable DREPD. A pattern that consists of both Deductive DREPD and Inductive DREPD.

Related lectures

Concept Management Quarter.

@@ Line 1: / Line 1: @@
-[[DADI]] (also known as [[DADI pattern]]; hereinafter, the ''Pattern'') is the enterprise development pattern that divides enterprise development activities in four consecutive batches: [[Enterprise discovery|'''D'''iscovery]] (D), [[Enterprise analysis|'''A'''nalysis]] (A), [[Enterprise design|'''D'''esign]] (D), and [[Enterprise implementation|'''I'''mplementation]] (I). The name of the ''Pattern'' is the abbreviation of four verbs: [[Enterprise discovery|'''D'''iscover]], [[Enterprise analysis|'''A'''nalyze]], [[Enterprise design|'''D'''esign]], [[Enterprise implementation|'''I'''mplement]].
+[[File:Dadi.png|400px|thumb|right|[[DREPD]]]][[DREPD]] (alternatively known as [[Discover-Research-Envision-Plan-Do Cycle]] and [[DREPD cycle]]; also historically known as [[DRMP]], [[Discover-Research-Model-Plan Cycle]], [[DRMP loop]], and [[DRMP method]]; hereinafter, the ''Method'') is the iterative four-step method used to manage any [[enterprise effort]] that that [[enterprise effort]] in four consecutive batches: [[Enterprise discovery|'''D'''iscovery]] (D), [[Enterprise research|'''R'''esearch]] (R), [[Enterprise envisioning|'''E'''nvisioning]] (M), and [[Enterprise planning|'''P'''lanning]] (P). The name of the ''Method'' is the abbreviation of four verbs: [[Enterprise discovery|'''D'''iscover]], [[Enterprise research|'''R'''esearch]], [[Enterprise envisioning|'''E'''nvision]], [[Enterprise planning|'''P'''lan]].
-The ''Pattern'' is used in any development in two ways:
+The ''Method'' is used in any development in two ways:
-#Being '''complex''', ''Pattern'' can serve as a canvas for the development cycle as a whole. In this case, one bigger ''complex Pattern'' may consist of a number of smaller ''Patterns'', which are called ''basic''; and
+#Being '''complex''', the ''Method'' can serve as a canvas for the development cycle as a whole. In this case, one bigger ''complex Method'' may consist of a number of smaller ''Patterns'', which are called ''basic''; and
-#Being '''basic''', ''Pattern'' can serve as a layout for simple actions in [[new product development]], [[problem solving]], [[business strategy]], [[business analysis]], [[systems engineering]], [[project management]], etc. A combination of those ''basic Patterns'' can be presented as a ''complex Pattern.''
+#Being '''basic''', the ''Method'' can serve as a layout for simple actions in [[new product development]], [[problem solving]], [[competitive strategy]], [[business analysis]], [[systems engineering]], [[project management]], etc. A combination of those ''basic Patterns'' can be presented as a ''complex Pattern.''
-[[#In education|In education]], [[Bracka School]] also deploys the ''Pattern'' while building the curricula on multiple sets of four quarters, each of which represents one batch of the ''Pattern''.
+[[#In education|In education]], [[Bracka School]] also deploys the ''Method'' while building the curricula on multiple sets of four quarters, each of which represents one batch of the ''Method''.
-==Classifications==
+==Components==
-Classifications of the ''Patterns'' are tentative. Every ''Pattern'' has some agility and no ''Pattern'' can fully fall in one exact category. Thus, the taxonomies below serve to demonstrate various directions of various ''Patterns'' rather than precise classifications.
+===Discovery===
+::''Main wikipage: [[Enterprise discovery]]''
+::The first batch of the ''Method'' is [[Enterprise discovery]]. It includes all activities resulted in discovery of any data relevant to the further enterprise development. These data include some statement of the [[business need]] that is sought to be satisfied as the key outcome from that enterprise as a whole.
-===Basic vs complex===
+===Research===
-::Ideally, a '''basic''' ''Pattern'' is any development pattern that doesn't include other ''Patterns''. For example, a generic reply like "Oh, really?" in a common conversation can be considered as basic. The listener (a) listens (or ''discovers'') to its conversational partner, (b) ''analyzes'' what he or she has said, (c) decides what to reply (or ''designs'' the reply), and (d) delivers (or ''implements'') it;
+::''Main wikipage: [[Enterprise research]]''
-::Ideally, a '''complex''' ''Pattern'' is any development pattern that includes other ''Patterns''. For example, development of a new space ship requires millions should be considered as complex because it includes millions and millions ''basic Patterns''.
-===Complete vs partial===
+::The second batch of the ''Method'' is [[enterprise research]]. It includes all activities needed to process the data discovered in [[enterprise discovery]] in order to provide [[enterprise envisioning]] with detailed requirements for the future outcome from the ''Method''.
-:*Ideally, a '''complete''' ''Pattern'' is any development pattern that includes all four batches from [[Discovery Batch]] to [[Implementation Batch|Implementation one]]. For example, a generic reply like "Oh, really?" in a common conversation can be considered as complete because the entry data for this reply was collected, analyzed, the reply was designed and delivered;
-:*Ideally, a '''partial''' ''Pattern'' is any development pattern that doesn't include [[Implementation Batch]]. This ''Pattern'' may or may not include [[enterprise design]] if the ''Pattern'' includes [[enterprise analysis]]. This ''Pattern'' may or may not include [[enterprise analysis]], but always include [[enterprise discovery]]. For example, development of a new space ship was ordered, but the project was stopped in the middle because of the lack of funding.
-===Transitional vs terminal===
+===Envisioning===
-:*Ideally, a '''transitional''' ''Pattern'' is undertaken in order to get some deliverable, which will be used in some ''Pattern'' in the future. For instance, a traveler takes a taxi in hopes that his or her driver would give more information on what to visit in a city, which hasn't been known to him or her yet. The traveler's airplane is unexpectedly delayed for one day;
+::''Main wikipage: [[Enterprise envisioning]]''
-:*Ideally, a '''terminal''' ''Pattern'' is undertaken in order to get with some deliverable, which will not be used in the future by the undertaker. For instance, someone delivers a pack of generic Vitamin C to its buyer.
-===Predefined-deliverable vs unexplored-deliverable===
+::The third batch of the ''Method'' is [[enterprise envisioning]]. It includes all activities needed to conceptualize, design, scratch, model, map, plan, project, and/or detail the ''Method's'' outcome and/or finalize the architecture or layout for this outcome.
-:*Ideally, a '''predefined-deliverable''' ''Pattern'' is undertaken in order to get with some deliverable, which features are defined before the ''Pattern'' starts. For instance, someone needs to buy a pack of generic Vitamin C;
-:*Ideally, an '''unexplored-deliverable''' ''Pattern'' is undertaken in order to get some deliverable, which features cannot be exactly defined before the ''Pattern'' starts. For instance, a traveler takes a taxicab in order to get to a city, which hasn't been known to him or her yet, because the traveler's airplane is unexpectedly delayed for one day and he or she is looking for ideas how to spend that "extra" day.
-==Components==
+===Planning===
-===Enterprise discovery===
+::''Main wikipage: [[Enterprise planning]]''
-::''Main wikipage: [[Enterprise discovery]]''
-::The first batch of the ''Pattern'' is [[Enterprise discovery]]. It includes all activities resulted in discovery of any data relevant to the further enterprise development. These data include some statement of the [[business need]] that is sought to be satisfied as the key outcome from that enterprise as a whole.
+::The fourth batch of the ''Method'' is [[enterprise planning]]. It includes all activities needed to create and deliver the ''Method's'' outcome based on its architecture or layout made in [[enterprise envisioning]].
-===Enterprise analysis===
+==Classifications==
-::''Main wikipage: [[Enterprise analysis]]''
+Classifications of the ''Patterns'' are tentative. Every ''Method'' has some agility and no ''Method'' can fully fall in one exact category. Thus, the taxonomies below serve to demonstrate various directions of various ''Patterns'' rather than precise classifications.
-::The second batch of the ''Pattern'' is [[enterprise analysis]]. It includes all activities needed to process the data discovered in [[enterprise discovery]] in order to provide [[enterprise design]] with detailed requirements for the future outcome from the ''Pattern''.
+===Basic vs complex===
+:*Ideally, a '''basic''' ''Method'' is any development pattern that doesn't include other ''Patterns''. For example, a generic reply like "Oh, really?" in a common conversation can be considered as basic. The listener (a) listens (or ''discovers'') to its conversational partner, (b) ''researches'' what he or she has said, (c) decides what to reply (or ''models'' the reply), and (d) delivers (or ''[[enterprise planning|plan]]s'') it;
+:*Ideally, a '''complex''' ''Method'' is any development pattern that includes other ''Patterns''. For example, development of a new space ship requires millions should be considered as complex because it includes millions and millions ''basic Patterns''.
-===Enterprise design===
+===Complete vs partial===
-::''Main wikipage: [[Enterprise design]]''
+:*Ideally, a '''complete''' ''Method'' is any development pattern that includes all four batches from [[enterprise discovery]] to [[enterprise planning|planning]]. For example, a generic reply like "Oh, really?" in a common conversation can be considered as complete because the entry data for this reply was collected, researched, the reply was designed and delivered;
+:*Ideally, a '''partial''' ''Method'' is any development pattern that doesn't include [[enterprise planning]]. This ''Method'' may or may not include [[enterprise envisioning]] if the ''Method'' includes [[enterprise research]]. This ''Method'' may or may not include [[enterprise research]], but always include [[enterprise discovery]]. For example, development of a new space ship was ordered, but the project was stopped in the middle because of the lack of funding.
-::The third batch of the ''Pattern'' is [[enterprise design]]. It includes all activities needed to conceptualize, design, scratch, model, map, plan, project, and/or detail the ''Pattern'''s outcome and/or finalize the architecture or layout for this outcome.
+===Transitional vs terminal===
+:*Ideally, a '''transitional''' ''Method'' is undertaken in order to get some deliverable, which will be used in some ''Method'' in the future. For instance, a traveler takes a taxi in hopes that his or her driver would give more information on what to visit in a city, which hasn't been known to him or her yet. The traveler's airplane is unexpectedly delayed for one day;
+:*Ideally, a '''terminal''' ''Method'' is undertaken in order to get with some deliverable, which will not be used in the future by the undertaker. For instance, someone delivers a pack of generic Vitamin C to its buyer.
-===Enterprise implementation===
+===Predefined-deliverable vs unexplored-deliverable===
-::''Main wikipage: [[Enterprise implementation]]''
+:*Ideally, a '''predefined-deliverable''' ''Method'' is undertaken in order to get with some deliverable, which features are defined before the ''Method'' starts. For instance, someone needs to buy a pack of generic Vitamin C;
+:*Ideally, an '''unexplored-deliverable''' ''Method'' is undertaken in order to get some deliverable, which features cannot be exactly defined before the ''Method'' starts. For instance, a traveler takes a taxicab in order to get to a city, which hasn't been known to him or her yet, because the traveler's airplane is unexpectedly delayed for one day and he or she is looking for ideas how to spend that "extra" day.
-::The fourth batch of the ''Pattern'' is [[enterprise implementation]]. It includes all activities needed to create and deliver the ''Pattern'''s outcome based on its architecture or layout made in [[enterprise design]].
+===Deductive vs inductive===
+:*Ideally, a '''deductive''' ''Method'' is undertaken in order to create a [[concept]] out of other [[concept]]s and [[experiment]]s. For instance, the ''Patern'' is created out of similar concepts such as [[PDCA]] and experiences;
+:*Ideally, an '''inductive''' ''Method'' is undertaken in order to conduct an experiment. For instance, the ''Patern'' can be tested in any [[enterprise effort]].
 ==Applications==
-[[New product development]], [[problem solving]], [[business strategy]], [[portfolio management]], [[business analysis]], [[systems engineering]], [[project management]] and many other concepts are built on the ''basic Patterns''. ''Complete complex terminal Patterns'' seem to have strong correlations with other concepts as well.
+[[New product development]], [[problem solving]], [[competitive strategy]], [[portfolio administration]], [[business analysis]], [[systems engineering]], [[project management]] and many other concepts are built on the ''basic Patterns''. ''Complete complex terminal Patterns'' seem to have strong correlations with other concepts as well.
 ===In project management===
-::With one exception of discovering a business need, which project deliverables shall satisfy, the ''complex Pattern'' can serve as a [[project management]] canvas itself. One or more the ''basic Patterns'' can be used in order to create or modify any output of any [[project management process]] such as a [[project charter]], [[stakeholder register]], [[acceptance criteria]], etc.
+::With one exception of discovering a business need, which project deliverables shall satisfy, the ''complex Method'' can serve as a [[project management]] canvas itself. One or more the ''basic Patterns'' can be used in order to create or modify any output of any [[project management process]] such as a [[project charter]], [[stakeholder register]], [[acceptance criteria]], etc.
 ===Complex Patterns vs other development concepts===
 ::Although the table below is not intended to be complete, it addresses some tendencies and correlations between the complete complex terminal ''Patterns'', on the one hand, and some other other development concepts, on the other hand:
 ::{|class="wikitable" width=100% style="text-align:center;"
-|colspan="2" style="background:#fff;"|'''[[Enterprise discovery|Discovery]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise analysis|Analysis]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise design|Design]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise implementation|implementation]]'''
+|colspan="2" style="background:#fff;"|'''[[Enterprise discovery|Discovery]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise research|Research]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise envisioning|Envisioning]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise planning|Planning]]'''
 |-
 |style="background:#fff;"|[[Business need|Business&nbsp;need]]|| style="background:#fff;"|[[Requirements data|Requirements&nbsp;data]]
 |-
-|colspan="5" style="background:#ffe6e6;"|'''[[Portfolio management]]'''
+|colspan="5" style="background:#ffe6e6;"|'''[[Portfolio administration]]'''
 |-
 |rowspan="4" style="background:#f6f6f6;"|Usually, [[c-level executive]]s define the needs at the organizational level, as well as [[frontline manager]]s at the lower levels and [[middle managers]] in between those levels||colspan="4" style="background:#e6ffe6;"|'''[[New product development]]'''
@@ Line 69: / Line 73: @@
 |colspan="3" style="background:#ffe6e6;"|'''[[Systems engineering]]'''||rowspan="3" style="background:#f6f6f6;"|Usually, project teams or functional departments execute implementations
 |-
-|colspan="2" style="background:#e6ffe6;"|'''[[Business analysis]]'''||style="background:#f6f6f6;"|[[Solution architect]]s or others can design the solution
+|colspan="2" style="background:#e6ffe6;"|'''[[Business analysis]]'''||style="background:#f6f6f6;"|[[Solution architect]]s or others can model the solution
 |-
-|colspan="4" style="background:#e6e6ff;"|'''[[Business strategy]]'''
+|colspan="4" style="background:#e6e6ff;"|'''[[Competitive strategy]]'''
 |-
-|style="background:#fff;"|[[Business need|Business&nbsp;need]]|| style="background:#fff;"|[[Requirements data|Requirements&nbsp;data]]||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise analysis|Analysis]]'''||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise design|Design]]'''||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise implementation|implementation]]'''
+|style="background:#fff;"|[[Business need|Business&nbsp;need]]|| style="background:#fff;"|[[Requirements data|Requirements&nbsp;data]]||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise research|Research]]'''||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise envisioning|Envisioning]]'''||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise planning|Planning]]'''
 |-
 |colspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise discovery|Discovery]]'''
@@ Line 80: / Line 84: @@
 ===In education===
-::[[Bracka School]] has built its [[Septem Artes Administrativi]] curriculum on seven sets of four quarters. Each set is called [[quadrivium]] and designed around the ''Pattern''.
+::[[Bracka School]] has built its [[Septem Artes Administrativi]] curriculum on seven sets of four quarters. Each set is called [[quadrivium]] and designed around the ''Method''.
+==Related concepts==
+*[[Deductive DREPD]].
+*[[Inductive DREPD]].
+*[[File:Double-dadi.png|400px|thumb|right|[[Viable DREPD]]]][[Viable DREPD]]. A pattern that consists of both [[Deductive DREPD]] and [[Inductive DREPD]].
+==Related lectures==
+*[[Concept Management Quarter]].
+[[Category: Septem Artes Administrativi]][[Category: Articles]]

Difference between revisions of "DREPD"

Latest revision as of 13:08, 8 April 2020

Contents

Components

Discovery

Research

Envisioning

Planning

Classifications

Basic vs complex

Complete vs partial

Transitional vs terminal

Predefined-deliverable vs unexplored-deliverable

Deductive vs inductive

Applications

In project management

Complex Patterns vs other development concepts

In education

Related concepts

Related lectures

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Tools