content 6.docx

Regardless of whether you run your Digitalization Project on basis of a waterfall, agile, or hybrid methodology, there will be [phases in which your plans are carried out] (i.e. Project Execution). If you've planned prudently, many things will go right during Project Execution.\ But there are also...

Regardless of whether you run your Digitalization Project on basis of a waterfall, agile, or hybrid methodology, there will be [phases in which your plans are carried out] (i.e. Project Execution). If you've planned prudently, many things will go right during Project Execution.\ But there are also [many things that might go wrong]. For this reason, successful Project Execution requires you to [measure the progress of your project] and [identify potential hazards] early enough to neutralize them. While this is true of any project, Digitalization Projects have a few unique factors that you should be aware of. We'll walk through these on the next slides, beginning with **(a)** developments you should monitor, and continuing with **(b)** KPIs that are often tracked in Digitalization Project. These are developments you should track in a digitalization project: Document updates: All projects produce documentation, but there are few\ project types where documentation requirements are\ as extensive and as critical as in a Digitalization Project. For this reason, make sure to [monitor the maintenance and updating of all technical documentation] to ensure accuracy and relevance. System performance: [Continuously monitor system performance and responsiveness] to identify and address any necessary improvements. Communication and collaboration: In spite of the prevalence of technical work areas\ in a Digitalization Project, don't forget to [measure\ the effectiveness of communication and collaboration among team members, stakeholders,\ and departments]. Data integrity and security: Ensure ongoing data integrity and security by [\ monitoring access controls and vulnerabilities]. Technical debt: In a Digitalization Project, **Technical Debt** refers to the [accumulated software development work that needs to be done in the future because of taking shortcuts or neglecting best practices] during Development. *Imagine you want to build a house, and you have a limited budget and time. To save costs and finish the project quickly, you decide to use lower quality materials and skip some important steps, like proper foundation work or insulation. Initially, you may have a house that meets your basic needs, but over time, you\'ll start experiencing issues like leaks, poor energy efficiency, and structural problems. Fixing these issues will require more time, effort, and money than if you had done it properly from the start. This is similar to technical debt in software development* [Monitor the accumulation of technical debt in your Digitalization Project] and address it proactively to prevent long-term issues. Code quality: Software code is not automatically high quality.\ For this reason, it is important to [track code quality\ metrics] [and code review feedback], in order to catch\ any code-related issues. User feedback: [Gather ongoing feedback from end users and other\ stakeholders] to gauge satisfaction, identify issues,\ and make improvements. Quality assurance: Monitor the [outcomes of testing efforts] to ensure\ that the digital solution meets both **(a)** functionality standards and **(b)** quality standards. Scope change: Take careful note of all [changes to the project scope]\ (i.e. [the total quantity and or/quality of output that\ is demanded from a project]) and and their impact on timelines, resources, and objectives. Task progress and completeion: Ongoingly monitor the [completion status] of tasks,\ user stories, or features, which indicates whether work is progressing as planned. -