Getting ahead of themselves, this episode was recorded at the end of July for the August release due to holidays etc. Before looking at Our governance model defined by DRAAP, which is
define | review | adapt | approve | publish.
We are looking for replacement names, all ideas are welcome. So the boys break down each of these stages in the model and cover the value that each section brings to the process of Governance.
If you want to come and discuss this as part of our governance workshop, join us at Sout Coast Summit in October.
The first important subject is Methodology or a Model, and the decision is not to create a podcast on which is most accurate...
Using some real examples, we look at current customers and which state of the DRAAP process they are at and the next stages to be completed. The process does allow you to define at what stage each of the governance documents is at and what the following stage should include. A way to identify the value.
Risk and value are included In the conversation, and Steve thinks this is a key attribute to define the protection required verse the effect on the end users. Governance that drives users away from using the product is not the target.
Then the boys drink a local Whisky from Mechelen in Belgium. Het ANKER’s Molenberg distillery for their anniversary edition
Creators and Guests
Microsoft MVP. Freelance Microsoft 365 expert focusing on user adoption and governance. Trainer. Licensed watchmaker.