Business:Concepts:Principle [Notes]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
# Business:Concepts:Principle #

<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}
* See also:
  * [[Business/Concepts/Behaviour/]]
  * [[Business/Concepts/Pattern/]]


</callout>


<panel title="Summary">

TODO: "Don't automate what still needs human oversight (TCO)"

A [[../Principle/|Principle]] is a objective abstract [[Business/Concepts/Norm/]] that an [[IT/AD/Organisation/|Organisation]] abides by in order to operate (or a person runs their life) and deliver [[Business/Concepts/Value/|Values]], expressed as [[Business/Concepts/Quality/|Qualities]]. 


<uml>
!includeurl http://skysigal.com/_media/resources/configuration/plantuml/minimalist.txt

package Qualities {
}

note right of Qualities
A Quality that has Value
to a Stakeholder
eg: 'Honesty'
eg: 'Reliability'
end note

class Principle

Qualities <|.DOWN. Principle 


note right of Principle
An approach on how
to deliver it
eg: 'Honesty is the best policy'
end note



</uml>


<callout icon="true" type="tip">
A [[Business/Concepts/Principle/]] differs from a [[Business/Concepts/Pattern/]] in that the [[Business/Concepts/Principle/]] is abstract (*"Be Transparent"*) whereas a [[Business/Concepts/Pattern/]] provides a means of accomplishing common tasks (which may satisfy a [[Business/Concepts/Principle/]]).
</callout>


</panel>


### Categorisation


[[IT/AD/TOGAF/]] recommends that [[IT/AD/TOGAF/HowTo/Terms/Principle/|Principles]] be separated into the following Domains:

* Business
* ITC:
  * Data
  * Technology
  * Development

That said, valuable Principles can -- maybe should -- be within *one or more categories*.


<uml>
!includeurl http://skysigal.com/_media/resources/configuration/plantuml/minimalist.txt

      package "Business Principles" as BP {
      }
      package "ITC Principles" as ITCP  {
        package "Information Principles" as IP  {
        }
        package "Technology Principles" as TP {
        }
        package "Development Principles" as DP {
        }
        IP -[HIDDEN]RIGHT- TP
        TP -[HIDDEN]RIGHT- DP
      }
</uml>

## Characteristics of Principles

* Of lasting organisation value
* Developed and Managed for iterative delivery and subsequent change
* Solve by Bridged Federation before Monolithic solutions.
* Plan to reach Targets via Transition
* Succinctness removes Ambiguity.
* Aim for Actions Achieved.








### Primary Principles

If I had to focus on getting only some of the above right, I would focus on the following first:

* [[./Act with Integrity/]]
* [[./Be User Focused/]]
* [[./Deliver Results/]]




## Resources ##

* https://www.quora.com/What-is-the-difference-between-a-value-and-a-principle
* https://medium.com/@jobv/how-to-work-remotely-with-150-people-89741118418c#.kvpgi722k 
* https://principles.com