12/24/2023 0 Comments Command conquer generals hidden unused![]() Then you just “load default templates” to create lists of what you should consider and in what sequence you should set them up in.Īfter you have created this, then just copy the lines into excel and import them into DevOps. You can find these standard templates here: ![]() Here I like to use what already exists in Dynamics 365 Data Management Templates and build a DevOps hierarchy list of all essential elements that needs to be considered and in what sequence you should set them up on. A baseline is a system that is not empty but is populated with as much fundamental setup as possible. To support the processes, we want to quite quickly setup a “baseline” of Dynamics 365. But the important takeaway is that processes vary for each customer based on what they need. When we run this scoping classification, we often see that we and up with a fraction of the 850 processes we have in our model. In essence, we quite quickly get an actionable WBS structure we can divide among the project team, and that can better ensure that the processes are successfully implemented. What we also try to scope is we should aim for creating a “test script” that will be typically used in UAT and for training purposes. The other classifications are improvements. In an implementation project we will prioritize the “Must have” processes and define the implementation of these processes as the critical path. To ensure we end up with a relevant list of processes we are running a MoSCoW process, to scope out “the crap”, and will classify the processes in scope according to the following classifications As the processes organized around standard features there is a very good way of understanding the end-to-end flow. The Level 1 and level 2 processes are for classification, while level 3 is how to perform the processes in the system. The processes describe responsibilities and are tailored towards how out-of-the-box Dynamics 365 functionality and features are supporting the most common processes. At inspirit365 we have a process library that consists of 850 processes that is organized into 3 levels and are End-to-End focused. New cloud technology and new ways of handling responsibilities are key enablers. Too often I have seen projects jumping into actions and details too early, and skipped scoping (aka “Cut the crap”) Processes and responsibilitiesĭoing things in a new way with some degree of business process reengineering can have a positive effect on organization. This allows the main project to be focused on the 3 pillars from a strategic perspective. The main deliverables are a Project Blueprint/SOW, Process Scope Definition and a Draft Solution Design. When we are running projects, we therefore always start with a discovery phase where we try to find the right direction and what the implementation project should focus on. For this there are 3 major pillars of focus in any implementation project: Processes and Responsibilities, People and Planning, Systems and Data I wanted to share with you some of my best practices on how to address scoping on a very early stage in an implementation project, to identify more quickly what to spend time and focus on. To identify the “crap”, there are one VERY important activity in any implementation that becomes a critical prerequisite to succeed within a constrained availability of resources (time, money, people). Like Thomas Edison had to evaluate 10.000 prototypes for a lightbulb before he cracked the solution(myth). You don’t know if something is “crap” unless you understand what is not “crap”. The other element is that “crap” is a retrospective experience. But for one person involved and looking at the entirety it could get this impression. The definition of “crap” is subjective and sometimes controversial, so it’s not always obvious whether something should be viewed as “crap”. Does this mean that 90% of what we have in Dynamics 365 is “crap”? When implementing Dynamics 365 at a customer, we often see that only a fraction (10%?) of the available features is being implemented. I can say with 100% certainty that nobody in the world deeply knows about all the available features and functions. Dynamics 365 is one of the most comprehensive and feature rich business application in the marked and trying to learn or use all the features would be lifelong study effort beyond the capacity of any person. Your have surely heard about Sturgeon’s law that “90% of everything is crap”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |