February 22, 2021
Why move from ITIL V3 to ITIL 4?

This is the kind of question I often hear from ITIL V3 Experts who are following our ITIL 4 training. My answer is simple: the world as changed so much since the introduction of ITIL V3 (more than ten years ago) that this new ITIL version was actually overdue, to help organizations survive in such a fast-paced and complex environment. However ITIL 4 still uses elements from ITIL V3, so ITIL V3 Experts can still benefit from their investment in ITIL V3 training.

February 8, 2021
The Professional Scrum Master I (PSM I) exam

The Professional Scrum Master I (PSM I) exam is an assessment in the English language where you must correctly answer 68 of 80 multiple choice questions to pass and anyone can take this exam. But how can you prepare for the exam and how does the exam work?

January 25, 2021
Agile in practice

Conclusions based on real Agile Scrum examples and Agile Scrum experiences.

“Agile is new, waterfall is old”. “To deliver services and products (whether or not IT) faster, you have to work Agile” I hear almost every day in my consultancy assignments and training courses. Note: Agile does not have to be Scrum (see eg Agile PM, PRINCE2 Agile, Devops,…). We are now quite a few years further with these exponentially increased methods, what conclusions can we draw from this? A few statements and my

January 12, 2021
Changes to the new Scrum Guide 2020 and difference with the 2017 version

During the Agile Scrum training courses that I regularly enjoy giving, such as the Agile Scrum Foundation and Agile Scrum Master (from EXIN) or via scrum.org, including the Professional Scrum Master (PSM-1) or Professional Scrum Product Owner (PSPO) -1) the scrum guide is always discussed in detail.

The Scrum Guide or Scrum Guide is nothing more than a definition of Scrum where, for example, the roles, events and artifacts are discussed. This document compiled by J. Sutherland & K. Schwaber can be found here:

December 14, 2020
Agile vs PRINCE2

As a trainer I am often asked what the difference is or the similarities between Agile (PM) and PRINCE2®. Lay people say a lot about it in the corridors, but what about exactly? Let me begin by saying that both have their value in that they are used by many organizations and individuals and are bearing fruit. When used properly, they increase the chance (!) Of a successful project: - Less costs - Better quality - Reduced throughput time - Less risks - More benefits - More clarity (scope) PRINCE2® Tried and tested for years, a reasonably complete project management method (or best practice), which encompasses almost all aspects of project management and provides checklists throughout the life cycle of the project of processes / activities that should be performed in order to lead and deliver a successful project, taking into account indisputable principles and using adaptable themes such as a Business Case for the project, design of the project organization (with clear roles), defining Quality, Risk, etc. In a Project Brief (mainly with a High Level Business Case), the project answers the question: Do we have to start the project ??? In the (following) Initiation Phase, the Project Initiation Documentation (or ?? PID ?? with ao a project plan, a detailed Business Case, ??) answer to the question: what does the project and the output of the project look like? In the Phase plans, a (sub) plan is presented at a detailed level shortly before the next phase. made by the most updated state of affairs so that it is iterative and ?? to the point ?? remains, with the PID revised where necessary. Info about PRINCE2 Agile (PM) Agile PM wants a more pragmatic approach than the traditional approach and is opposed to the Waterfall method, which is too static. Through an iterative way of working and always in collaboration with the customer, Agile always ensures minimal deviations from the wishes of the customer. Agile chooses to allow the functionality desired by the customer to fluctuate for the benefit of costs and (lead) time, whereby the latter 2 must be fixed and functionality based on the MoSCoW (Must -, Should -, Could -, Won? ? t have) principle to fluctuate in order to stay within time and costs. Info about Agile Differences A difference between the two techniques is of course in terminology, where I tell customers and students that a lot is in the ?? language ?? which one prefers to speak. For example, Dutch is not necessarily better ?? than French, but more convenient ?? if you eg want to ask for directions in the Netherlands, but more awkward if you ask for directions in Paris. Another difference is how the various activities are grouped: for example, PRINCE2 knows the ?? Pre Project ?? looking at the desirability of continuing, which in Agile is again cut into 2 pieces ??: ?? Pre-project ?? and ?? Feasability ?? (..). Also in the amount of roles Agile has more (split) roles than PRINCE2 which groups these roles more together, etc. Another perhaps important difference is the different choices that are made: eg where PRINCE2 works with tolerances with regard to all aspects (time, money, quality of the (end) products, ??.) that must be properly agreed, Agile states in advance that costs and lead time may not be tinkered with and that functionality is the MoSCoW principle (see above) must vary, assuming that not all features ?? are equally important. PRINCE2® also uses MoSCoW, but states that any choice on any of the aspects is a joint decision by both the project supplier and the client / business (or customer). Last but not least, Agile believes there is an essential difference between building software and all other projects. Similarities It is clear to me that the similarities are much greater than the differences and there is no other way and I mean this in an almost "physical way". OF COURSE you have to think carefully about what you are going to do before you start, then continue to fine-tune (with the customer and key stakeholders) whether what you are doing is still intended and worthwhile, evaluate afterwards etc: this basic philosophy also has every decent method. / best practice / ??. on earth! The iterative character is also a vision that has grown stronger over the years and is reflected in Agile, PRINCE2® and any other modern technology. Obviously, it is much more convenient for the supplier of products to have static specifications (specs) (Waterfall method), because the supplier can then work comfortably and unhindered without always taking changed specs into account, but THE WORLD IS UNFORTUNATELY NOT STILL WHEN YOU DO YOUR PROJECT! All PM methods have removed most of the static elements from each technique and replaced them with dynamic / iterative components. Both techniques are NOT NORM, which means that you can / must adjust them so that they work best for your organization and you get the best results from them. Combining Agile / PRINCE2 It is argued by colleagues in the business that ?? partial use ?? The solution of both techniques would be: I am very much against this for several reasons. 1) You ask an organization to know 2 methods where it is already very difficult to know 1 method well. 2) You introduce different terminology, which greatly increases the confusion both internally and externally. You get islands within your organization, each with their own jargon / interpretation of the different methods, while it is difficult enough to make good agreements with 1 method. External parties: suppliers, new employees, ?? will find it extra difficult to integrate. The strength of 1 (!) Method is precisely that everything must be clear to everyone and you prevent discussions about ?? what do you mean ??. ?? 3) You actually develop a new method, while dedicated specialists worldwide sometimes spend decades trying to get a method (or technique) so complete / consistent / (almost) flawless. We're going to mix that up for a while? must there be a good answer to that? Apart from the fact that these ?? colleagues ?? often having too little knowledge / skills for this, this would take years. The result for organizations is therefore often disastrous. PLEASE NOTE: a PRINCE2 Agile method has been developed that could be very interesting for those who would like to do the above. There, too, it must be realized that this is neither PRINCE2® nor Agile PM and so in fact a choice for a new method with the same advantages and the same risks above. Conclusion My conclusion is that there is no ?? best technique / method ?? is. PRINCE2® is by far the most widely used method and this should definitely be a consideration. As the Dutch language is by far the most used language in the Netherlands, this should certainly be a very important argument for using Dutch as the working language in your organization. The same applies to PRINCE2, although Agile is gaining more and more popularity, the proportions are still very strong in favor of PRINCE2®. In addition, organizations must of course look at the situation they find themselves in and ask themselves and stakeholders questions such as: - What technology do we currently use (possibly partly) and how does it work for us and our environment? - In which areas do we have difficulties and does our way of working not give the expected results? - What expectations do our (most important) stakeholders (or stakeholders) have and what technology do they work with? Finally Choosing a well-suited Project Management method is essential for large and small organizations that are going through more and more changes and want to make these changes in an effective (achieving the objectives) and efficient way (without using too much time / costs / resources). implement. In addition to choosing a method, training / certification and guidance of employees is also crucial. You can contact D-ICT Solutions for certified training courses or a free consultation.

November 30, 2020
BiSL® and Agile Scrum, how does that fit (best)?

During the BiSL training courses, the question is increasingly asked whether BiSL fits within Agile or more specifically within Scrum. In the BiSL version 2.0 - 2nd edition, not a word about this, but since the update to the new BiSL version 3.0 - 3rd edition, more attention is paid to how BiSL relates to other models, approaches, frameworks and standards, including Agile Scrum . Bisl-version-3.0-3rd-edition-dictsolutions For example, a small paragraph about Agile Scrum has been included, which explains in a nutshell what Agile Scrum is compared to the traditional waterfall approach. Furthermore, BiSL refrains from prescribing methods and approaches, but makes it clear that Business Information Management (BIM) must be clearly represented in a Scrum or project team. Does this answer the question whether BiSL fits within an approach such as Agile Scrum? Yes and no?? BiSL assumes that it is suitable for any method and approach, but we may have to rephrase the question in order to get the answer clearly. BiSL focuses on the so-called user perspective and acts from the customer's thoughts. And this also seems logical, after all, the customer determines what requirements and expectations they set for a product or service. We are therefore on the demanding side with BiSL and as far as I am concerned, we are also leading in any project. Agile / Scrum was conceived as an approach for developing software within IT. Just say the supply side, who want to solve an IT question or problem. It arose because many IT projects generally did not run well in terms of lead time and costs and the users / customers ultimately did not get what they expected. The solution to this lay in a more iterative / short-cyclical approach. Meanwhile, the Agile Scrum approach has grown in popularity and this seems to be the approach in every organization and also prescribed by every IT person. Although this has changed the approach, IT organizations still tell customers how and what to do. For me, the question is therefore not whether BiSL fits within Agile Scrum, but how BiSL and Agile Scrum fit (best). The demand and therefore the starting point therefore lies with the customer and BiSL (or FSM, etc.) is leading. Together with IT, it can then be determined what the best approach is for the realization. That can be Agile Scrum, but also a project via Prince2. Too often we hear that IT determines the working method and years ago that was project-based work and has now become Scrum. Maybe another method in a few years? IT should be able to offer many more different methods and approaches and they should also be able to be used side by side. It is actually special that you can have a house built to order by a contractor, who, after hearing what you want, builds the house for you on a project basis.If you go to IT with a wish, question or problem, it is often too difficult and for that you know, IT is in the customer's chair to think about what is good for the customer. So they still largely determine how work is done and what must be delivered. As a customer you have to show up regularly when things threaten to go wrong. The customer must educate IT, take control. If you as a customer want to develop a new service and you choose a big-bang implementation because you want to stay ahead of the competition or for other legitimate reasons, then IT will immediately be on its back feet given its current status. This is possible and allowed, but ultimately the customer must determine what and how he / she wants it, taking into account the risks involved. But if you, as a customer, want to have a service or product made in small steps, then it must also be possible for the same IT to perform as such. The statement of BiSL that Business Information Management (BIM) must be clearly represented in the Scrum or project team is therefore partly true. At that time, a certain approach has already been chosen, Business Information Management (BIM) largely determines what this approach is and which IT best suits it. As a customer you want to be able to use an IT with the necessary knowledge. Knowledge of tools, but also of different methods and approaches. You want to use an IT that has its processes in order internally, which unfortunately does not always turn out to be the case in many cases. As a customer you don't want to be confronted with yet another new method and / or a new approach ????????. But on the customer side, there is still work to be done. Taking more control, indicating what the actual need is, setting clear priorities and, as BiSL puts it, being clearly represented within the Scrum and project teams. Conclusion: The question is therefore whether Agile scrum should / can also fit within BiSL and not the other way around. Sometimes this will work fine, but sometimes not at all. But if IT has sufficient knowledge and sufficient methods and approaches, this will not be a bad thing.

November 22, 2020
Anger Management training on January 21 in Amsterdam for € 415!

On January 21, 2021, D-ICT Solutions will provide another Anger Management course, for the price of € 415 including lunch! The modules included in this course are: getting started, acting anger, do's and don'ts, gaining control, separating the people from the problem, working on the problem, solving the problem, a personal […]

November 8, 2020
Retraining programs for a job with a future perspective

Your organization is under pressure, which means that you sometimes have to look for other work: within your organization or outside it. Especially for you, DICT has a number of popular short courses with a diploma / certificate that will help you to increase your chances on the labor market. The D-ICT training courses take extra into account your experience, so you never have to worry that you will not be able to participate and / or that you will not pass your exam! dictsolutions-retraining pathways-future perspective If you want to participate in projects (of any kind and in whatever role), the most requested certificates are: PRINCE2 (3 days), this is a general project management method for any type of project from is applicable. Agile Scrum (2 days), this very popular and simplified method is increasingly used in different organizations for various projects. With these certificates in your pocket, you at least have all the necessary papers! Do you want to take a first step in IT and do you want, for example: A service / help desk function: then choose ITIL (3 days), which is ALWAYS required. An application management function: then choose ASL, which is ALWAYS required. We also have job-oriented retraining programs available, namely: Agile Tester Project and change manager Information manager Service Manager Portfolio manager Service Manager Looking for other (in-company) training courses or tailor-made programs? DICT has more than 200 courses that help you take the next step in your career, always tailored to your wishes, knowledge and experience!

October 11, 2020
Business Process Model & Notation 2.0 (BPMN) training at D-ICT Solutions

Processes are increasingly automated, but must follow YOUR business processes instead of the other way around! Easily create your desired business processes so that they can be automated in your tools with BPMN. Business-Process-Model-Notation-BPMN-Dictsolutions What is BPMN? The Business Process Modeling Notation is a graphical notation that shows the steps in a business process. Business Process Modeling Notation represents the start-to-finish flow of a business process. The format is specifically designed to coordinate the order of processes and the messages that flow between different process participants in a related set of activities. Why is BPMN Important? The world of business processes has changed radically in recent years. Processes can be coordinated from behind, within and above the natural boundaries of organizations. A business process now includes multiple participants and coordination can be complex. Until Business Process Modeling Notation, no standard modeling technique had been developed to address these problems. Business Process Modeling Notation is really developed to provide users with royalty-free notation. Who is BPMN intended for? Business Process Modeling Notation is aimed at a high level for business users and at a lower level for process implementers. The business users should be able to read and understand a Business Process Modeling Notation business process diagram easily. The process implementer must be able to decorate a business process diagram with more detail to represent the process in a physical implementation. Business Process Modeling Notation is aimed at users, suppliers and service providers who need to communicate business processes in a standard way. Certificate The exam with certificate can be taken online immediately after the training. The cost for the exam is 165. Mock exams are covered in the training. Do you want advice on what is the best choice for you? Then you can always contact D-ICT Solutions via info@dictsolutions.com or 020-2050324. The author of this article Keesjan Fijma is a marketing and sales specialist. Together with the certified trainers, interim managers, coaches and other staff of D-ICT Solutions (Secondment, Interim Management, Consultancy and Training), leading in the field of certified training worldwide in various Process, Project, Service and quality management techniques such as ITIL , ISO, PRINCE2, Agile, Lean Six Sigma, BiSL and many others.

September 24, 2020
A time of exciting change and full of opportunity for ITIL® 4 implementation!

Digital services are helping organizations to compete in the modern digital economy. However this increasingly fast-paced and complex environment creates new challenges for organizations and professionals to manage. This new digital era is known as the 'Fourth Industrial Revolution', characterized by the digital transformation of our world and the unavoidable interaction between humans, digital technologies […]

© Copyright 2021 - Dict Solutions - All Rights Reserved

Pin It on Pinterest

linkedin facebook Pinterest youtube rss twitter Instagram facebook-Blank rss blank LinkedIn-blank Pinterest youtube twitter Instagram