The document outlines a multi-step data governance risk assessment process for classifying projects and assessing their data governance risks. It involves:
1) Classifying projects into categories based on their data handling activities and assigning maturity levels.
2) Assessing projects' compliance with data governance best practices and scoring their risk levels.
3) Defining policies and procedures to address risks and monitoring projects' risk reduction over time with regular reviews.
The process aims to improve how projects govern their data through ongoing classification, assessment, policy implementation, and risk tracking.
This document provides a checklist for reviewing audit documentation and workpapers. It contains 3 sections: 1) Audit administration and documentation, 2) Audit effectiveness, and 3) Report issuance and other administrative matters. Each section contains a list of review areas to check compliance with standards for planning, documentation, conclusions, and administrative procedures such as securing files. The reviewer uses the checklist to verify audits meet quality standards for key areas like objectives, program, conclusions, and proper documentation and approval of workpapers and reports.
لمشاهدة ملفات الفيديو
https://www.youtube.com/watch?v=gKbK6kCp7G0&list=PL0CTRdzzWSMuvJ9nKHzyxGAYCapJMQ8_Y&index=19
للمتابعة في جروب المذاكرة
https://www.facebook.com/groups/PMP.SG
How performance management can improve client satisfactionSkanska USA
Early in her construction career, Wendy (Li) MacLeod-Roemer realized there was significant room to improve construction delivery beyond traditional means. To help advance our industry, she decided to pursue a PhD in organization management to understand what changes would be most effective. She dedicated her thesis to exploring how performance management can transform construction projects. Here, Wendy – now one of our senior project managers – explains how her research shows that cost isn’t what is most important to clients.
This lecture provides a short review of postmortem analysis. The core responsibility of software project manager. Postmortem analysis describes reasons of software project failure or success.
The document discusses various software project life cycle models and cost estimation techniques. It begins by describing agile methods like Scrum and Extreme Programming that emphasize iterative development, communication, and customer involvement. It then covers traditional models like waterfall and incremental development. Key estimation techniques discussed include function points, COCOMO, and analogy-based estimation. The document provides details on calculating sizes and estimating effort for different models.
The document is a sample exam for the Certified Software Quality Engineer (CSQE) certification. It contains 18 multiple choice questions about software quality topics like testing, requirements, configuration management, metrics, and process improvement. For each question there is a short explanation of the correct answer along with a reference to further information in the CSQE Handbook.
This document provides a checklist for reviewing audit documentation and workpapers. It contains 3 sections: 1) Audit administration and documentation, 2) Audit effectiveness, and 3) Report issuance and other administrative matters. Each section contains a list of review areas to check compliance with standards for planning, documentation, conclusions, and administrative procedures such as securing files. The reviewer uses the checklist to verify audits meet quality standards for key areas like objectives, program, conclusions, and proper documentation and approval of workpapers and reports.
لمشاهدة ملفات الفيديو
https://www.youtube.com/watch?v=gKbK6kCp7G0&list=PL0CTRdzzWSMuvJ9nKHzyxGAYCapJMQ8_Y&index=19
للمتابعة في جروب المذاكرة
https://www.facebook.com/groups/PMP.SG
How performance management can improve client satisfactionSkanska USA
Early in her construction career, Wendy (Li) MacLeod-Roemer realized there was significant room to improve construction delivery beyond traditional means. To help advance our industry, she decided to pursue a PhD in organization management to understand what changes would be most effective. She dedicated her thesis to exploring how performance management can transform construction projects. Here, Wendy – now one of our senior project managers – explains how her research shows that cost isn’t what is most important to clients.
This lecture provides a short review of postmortem analysis. The core responsibility of software project manager. Postmortem analysis describes reasons of software project failure or success.
The document discusses various software project life cycle models and cost estimation techniques. It begins by describing agile methods like Scrum and Extreme Programming that emphasize iterative development, communication, and customer involvement. It then covers traditional models like waterfall and incremental development. Key estimation techniques discussed include function points, COCOMO, and analogy-based estimation. The document provides details on calculating sizes and estimating effort for different models.
The document is a sample exam for the Certified Software Quality Engineer (CSQE) certification. It contains 18 multiple choice questions about software quality topics like testing, requirements, configuration management, metrics, and process improvement. For each question there is a short explanation of the correct answer along with a reference to further information in the CSQE Handbook.
Defining the Problem - Goals and requirementsStephennancy
This document discusses goals and requirements in software engineering projects. It makes the following key points:
- Goals define targets for both the development process and final work products, and can be qualitative or quantitative. Examples of each type are given.
- Requirements specify the capabilities needed to solve the problem, and include functional, performance, and interface requirements. They provide standards for the project and product.
- Both goals and requirements should be specified quantitatively when possible to avoid later misunderstandings, though this can be difficult in the planning phase. Methods for verification should also be defined.
- High-level goals can be translated into specific requirements related to quality attributes like reliability. Milestones can quantify goals
Unit4 Proof of Correctness, Statistical Tools, Clean Room Process and Quality...Reetesh Gupta
Program testing seeks to show that input values produce acceptable output values but can never prove the absence of errors. Proof of correctness uses formal logic to prove that if input values satisfy constraints, output values will satisfy specific properties. Total quality control is a management framework that links different business functions through information sharing to ensure continuous excellence. It involves applying tools like control charts, histograms, Pareto charts, fishbone diagrams, and scatter diagrams to identify and address quality issues.
Software quality assurance (sqa) Parte II- Métricas del Software y Modelos d...Renato Gonzalez
This document discusses software metrics and quality models. It begins by explaining that measurements are necessary to control and improve processes. It then discusses different types of software complexity metrics, including code-oriented metrics like lines of code, control structure metrics like McCabe's cyclomatic complexity, linguistic metrics, design metrics, and functional size metrics. The document also covers software process metrics and quality metrics. Overall, it provides an overview of various metrics used to measure different aspects of software size, development processes, and product quality.
This document discusses metrics that can be used to measure software processes and projects. It begins by defining software metrics and explaining that they provide quantitative measures that offer insight for improving processes and projects. It then distinguishes between metrics for the software process domain and project domain. Process metrics are collected across multiple projects for strategic decisions, while project metrics enable tactical project management. The document outlines various metric types, including size-based metrics using lines of code or function points, quality metrics, and metrics for defect removal efficiency. It emphasizes integrating metrics into the software process through establishing a baseline, collecting data, and providing feedback to facilitate continuous process improvement.
Systematic review on evaluating planning process in agile development methodsTELKOMNIKA JOURNAL
Agile development methods have been catering the need of faster delivery of theever-demanding domain of software engineering. These methods are able to deliver value to users and businesses via fast, reliable, and repeatable process. Planning requirements and processes takes the driving seat in a dynamic environment because the value proposition rapidly changes. This paper exhibits asystematic literature review of planning processes implementedby various agile methods in order to find the best suited agile method in terms of robust planning. Keywords: It was found that Scrum is the best suited agile method for planning processes.
Project Management: Initiating Process Group - Lesson 1 JMBOKAcademy
This document contains 5 questions from the Initiating Process Group chapter of the PMBOK Guide. Each question is multiple choice and is followed by an explanation of the correct answer. The questions cover topics such as the definition of ongoing work versus projects, the meaning of "temporary" in relation to projects, examples of projects versus ongoing work, the process group that precedes planning, and examples of project constraints.
The document discusses topics related to software quality assurance and testing. It covers definitions of testing, types of testing activities like static and dynamic testing, different levels of testing from unit to system level. It also discusses test criteria, coverage, and agile testing approaches. The overall document provides an overview of key concepts in software quality assurance and testing.
After the course, student will:
Understand Fsoft metric system.
Know about Fsoft PCBs and norms.
Be able to use data for managing projects.
Effort (Project, work product, process, type of activity): Weekly
Schedule (Start-date, expected end-date, actual end-date, delivery): At milestones
Defect (Project, work product, stage detected, QC activities, stage injected, process origin, severity, classification type, priority): Weekly
Size (Total, work product, activity): At milestones
Requirement (Total, size, status): Weekly
Customer complaints, customer satisfaction survey point, NC
Tools: Fsoft management suite (Timesheet, DMS, NCMS, Dashboard, Fsoft Insight)
This document outlines the 10 step process for software project planning. It begins with selecting the project and identifying its scope and objectives. It then covers identifying the project infrastructure, analyzing project characteristics, and identifying products and activities. Steps also include estimating effort for each activity, identifying risks, allocating resources, and reviewing/publicizing the plan. Execution then involves lower level planning. The document also discusses software effort estimation techniques such as algorithmic models, expert judgment, analogy, and top-down and bottom-up approaches.
The document discusses software development lifecycles and strategies. It describes:
1) Common lifecycle activities like planning, development, testing and maintenance. Different models can be used depending on the product.
2) Solution strategies are developed to determine the nature of possible solutions and provide a framework for design and implementation. The best strategies are developed by trained groups using techniques like brainstorming.
3) The phased lifecycle model involves a series of defined activities with inputs, processes, and outputs at each phase. Resources are required to complete each defined phase.
In this advanced business analysis training session, you will learn Requirement Verification and Validation. Topics covered in this session are:
• Requirements Negotiation And Prioritization
• Requirements Management
• Requirements Traceability
• Requirements Variability and Software/System Product Lines
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
A software system is more than the code; it is a set of related artifacts; these may contain defects or problem areas that should be reworked or removed; quality-related attributes of these artifacts should be evaluated
Reviews allow us to detect and eliminate errors/defects early in the software life cycle (even before any code is available for testing), where they are less costly to repair
Most problems have their origin in requirements and design; requirements and design artifacts can be reviewed but not executed and tested
A code review usually reveals directly the location of a bug, while testing requires a debugging step to locate the origin of a bug
Adherence to coding standards cannot be checked by testing
An integrated security testing framework and toolMoutasm Tamimi
The document presents an integrated security testing framework for the secure software development life cycle (SSDLC). The framework includes four main phases: 1) defining security guidelines based on enterprise security requirements for each SSDLC phase, 2) constructing security test cases based on the guidelines, 3) executing test cases by integrating various security testing tools, and 4) converging results from different tools using a meta-vulnerability data model. The framework aims to adopt security activities into each SSDLC phase to improve security, generate test cases, integrate testing tools, and provide accurate results. It was evaluated through prototype testing of 50 software projects.
This document discusses software metrics. It defines a software metric as a standard measure of a software system or process's properties. The document then classifies metrics into product, process, and resource metrics. It describes several types of product metrics including size, complexity, Halstead's, and quality metrics. The document recommends using a GQM (Goal, Question, Metric) approach to implement an effective metrics program. It provides references for further reading.
This document provides information and requirements for Mark Johnman's Year 11/12 Information Processing and Technology major project at Hillcrest Christian College. It outlines the four phases of the project, which involve defining the problem, designing a solution, implementing the design, and testing and evaluating the completed application. The project requires designing a single-page web application using JavaScript, HTML, and CSS to meet the needs of a proposed client. Standards for each phase are provided, along with criteria for assessing knowledge and application, analysis and synthesis, and evaluation and communication.
The document discusses key concepts for managing software projects including the four Ps of project management: People, Product, Process, and Project. It describes stakeholders and team structures, and emphasizes establishing clear objectives and scope, tracking progress, and learning lessons through post-mortem reviews. Metrics for both processes and products are discussed to assess status, risks, and quality in order to guide improvement.
لمشاهدة ملفات الفيديو
https://www.youtube.com/playlist?list=PL0CTRdzzWSMuvJ9nKHzyxGAYCapJMQ8_Y
للمتابعة في جروب المذاكرة
https://www.facebook.com/groups/PMP.SG/
Este documento resume las características demográficas, geográficas e históricas de la ciudad de San Bernardino, Paraguay. La ciudad fue fundada por colonos alemanes en 1881 y actualmente tiene una población de 11,000 habitantes, la mayoría de los cuales viven en áreas rurales. La economía de San Bernardino depende en gran medida del turismo debido a sus atracciones naturales como el lago Ypacarai.
Defining the Problem - Goals and requirementsStephennancy
This document discusses goals and requirements in software engineering projects. It makes the following key points:
- Goals define targets for both the development process and final work products, and can be qualitative or quantitative. Examples of each type are given.
- Requirements specify the capabilities needed to solve the problem, and include functional, performance, and interface requirements. They provide standards for the project and product.
- Both goals and requirements should be specified quantitatively when possible to avoid later misunderstandings, though this can be difficult in the planning phase. Methods for verification should also be defined.
- High-level goals can be translated into specific requirements related to quality attributes like reliability. Milestones can quantify goals
Unit4 Proof of Correctness, Statistical Tools, Clean Room Process and Quality...Reetesh Gupta
Program testing seeks to show that input values produce acceptable output values but can never prove the absence of errors. Proof of correctness uses formal logic to prove that if input values satisfy constraints, output values will satisfy specific properties. Total quality control is a management framework that links different business functions through information sharing to ensure continuous excellence. It involves applying tools like control charts, histograms, Pareto charts, fishbone diagrams, and scatter diagrams to identify and address quality issues.
Software quality assurance (sqa) Parte II- Métricas del Software y Modelos d...Renato Gonzalez
This document discusses software metrics and quality models. It begins by explaining that measurements are necessary to control and improve processes. It then discusses different types of software complexity metrics, including code-oriented metrics like lines of code, control structure metrics like McCabe's cyclomatic complexity, linguistic metrics, design metrics, and functional size metrics. The document also covers software process metrics and quality metrics. Overall, it provides an overview of various metrics used to measure different aspects of software size, development processes, and product quality.
This document discusses metrics that can be used to measure software processes and projects. It begins by defining software metrics and explaining that they provide quantitative measures that offer insight for improving processes and projects. It then distinguishes between metrics for the software process domain and project domain. Process metrics are collected across multiple projects for strategic decisions, while project metrics enable tactical project management. The document outlines various metric types, including size-based metrics using lines of code or function points, quality metrics, and metrics for defect removal efficiency. It emphasizes integrating metrics into the software process through establishing a baseline, collecting data, and providing feedback to facilitate continuous process improvement.
Systematic review on evaluating planning process in agile development methodsTELKOMNIKA JOURNAL
Agile development methods have been catering the need of faster delivery of theever-demanding domain of software engineering. These methods are able to deliver value to users and businesses via fast, reliable, and repeatable process. Planning requirements and processes takes the driving seat in a dynamic environment because the value proposition rapidly changes. This paper exhibits asystematic literature review of planning processes implementedby various agile methods in order to find the best suited agile method in terms of robust planning. Keywords: It was found that Scrum is the best suited agile method for planning processes.
Project Management: Initiating Process Group - Lesson 1 JMBOKAcademy
This document contains 5 questions from the Initiating Process Group chapter of the PMBOK Guide. Each question is multiple choice and is followed by an explanation of the correct answer. The questions cover topics such as the definition of ongoing work versus projects, the meaning of "temporary" in relation to projects, examples of projects versus ongoing work, the process group that precedes planning, and examples of project constraints.
The document discusses topics related to software quality assurance and testing. It covers definitions of testing, types of testing activities like static and dynamic testing, different levels of testing from unit to system level. It also discusses test criteria, coverage, and agile testing approaches. The overall document provides an overview of key concepts in software quality assurance and testing.
After the course, student will:
Understand Fsoft metric system.
Know about Fsoft PCBs and norms.
Be able to use data for managing projects.
Effort (Project, work product, process, type of activity): Weekly
Schedule (Start-date, expected end-date, actual end-date, delivery): At milestones
Defect (Project, work product, stage detected, QC activities, stage injected, process origin, severity, classification type, priority): Weekly
Size (Total, work product, activity): At milestones
Requirement (Total, size, status): Weekly
Customer complaints, customer satisfaction survey point, NC
Tools: Fsoft management suite (Timesheet, DMS, NCMS, Dashboard, Fsoft Insight)
This document outlines the 10 step process for software project planning. It begins with selecting the project and identifying its scope and objectives. It then covers identifying the project infrastructure, analyzing project characteristics, and identifying products and activities. Steps also include estimating effort for each activity, identifying risks, allocating resources, and reviewing/publicizing the plan. Execution then involves lower level planning. The document also discusses software effort estimation techniques such as algorithmic models, expert judgment, analogy, and top-down and bottom-up approaches.
The document discusses software development lifecycles and strategies. It describes:
1) Common lifecycle activities like planning, development, testing and maintenance. Different models can be used depending on the product.
2) Solution strategies are developed to determine the nature of possible solutions and provide a framework for design and implementation. The best strategies are developed by trained groups using techniques like brainstorming.
3) The phased lifecycle model involves a series of defined activities with inputs, processes, and outputs at each phase. Resources are required to complete each defined phase.
In this advanced business analysis training session, you will learn Requirement Verification and Validation. Topics covered in this session are:
• Requirements Negotiation And Prioritization
• Requirements Management
• Requirements Traceability
• Requirements Variability and Software/System Product Lines
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
A software system is more than the code; it is a set of related artifacts; these may contain defects or problem areas that should be reworked or removed; quality-related attributes of these artifacts should be evaluated
Reviews allow us to detect and eliminate errors/defects early in the software life cycle (even before any code is available for testing), where they are less costly to repair
Most problems have their origin in requirements and design; requirements and design artifacts can be reviewed but not executed and tested
A code review usually reveals directly the location of a bug, while testing requires a debugging step to locate the origin of a bug
Adherence to coding standards cannot be checked by testing
An integrated security testing framework and toolMoutasm Tamimi
The document presents an integrated security testing framework for the secure software development life cycle (SSDLC). The framework includes four main phases: 1) defining security guidelines based on enterprise security requirements for each SSDLC phase, 2) constructing security test cases based on the guidelines, 3) executing test cases by integrating various security testing tools, and 4) converging results from different tools using a meta-vulnerability data model. The framework aims to adopt security activities into each SSDLC phase to improve security, generate test cases, integrate testing tools, and provide accurate results. It was evaluated through prototype testing of 50 software projects.
This document discusses software metrics. It defines a software metric as a standard measure of a software system or process's properties. The document then classifies metrics into product, process, and resource metrics. It describes several types of product metrics including size, complexity, Halstead's, and quality metrics. The document recommends using a GQM (Goal, Question, Metric) approach to implement an effective metrics program. It provides references for further reading.
This document provides information and requirements for Mark Johnman's Year 11/12 Information Processing and Technology major project at Hillcrest Christian College. It outlines the four phases of the project, which involve defining the problem, designing a solution, implementing the design, and testing and evaluating the completed application. The project requires designing a single-page web application using JavaScript, HTML, and CSS to meet the needs of a proposed client. Standards for each phase are provided, along with criteria for assessing knowledge and application, analysis and synthesis, and evaluation and communication.
The document discusses key concepts for managing software projects including the four Ps of project management: People, Product, Process, and Project. It describes stakeholders and team structures, and emphasizes establishing clear objectives and scope, tracking progress, and learning lessons through post-mortem reviews. Metrics for both processes and products are discussed to assess status, risks, and quality in order to guide improvement.
لمشاهدة ملفات الفيديو
https://www.youtube.com/playlist?list=PL0CTRdzzWSMuvJ9nKHzyxGAYCapJMQ8_Y
للمتابعة في جروب المذاكرة
https://www.facebook.com/groups/PMP.SG/
Este documento resume las características demográficas, geográficas e históricas de la ciudad de San Bernardino, Paraguay. La ciudad fue fundada por colonos alemanes en 1881 y actualmente tiene una población de 11,000 habitantes, la mayoría de los cuales viven en áreas rurales. La economía de San Bernardino depende en gran medida del turismo debido a sus atracciones naturales como el lago Ypacarai.
This document provides information on a company called AMACEN DE ELECTROMESTICOS Y SIMILARES LTDA located at Calle 70 No. 44-36 with a registration number of 5258901.
El violoncello surgió en el siglo XVI como el bajo de la familia de violas. Durante el Barroco tuvo un papel importante como instrumento de continuo y reemplazó a la viola da gamba. En el siglo XVIII su presencia en la orquesta se estabilizó y aumentó en número, apareciendo la primera literatura concertística para el instrumento. Las fuentes iconográficas muestran que el arco comenzó a agarrarse con la palma hacia abajo y más hacia el extremo, imponiéndose su ejecuc
Mspark's Monthly Trends Monitor - Aug 16 issue Frank Boggess
1) Dollar General has bought 41 former Walmart Express small-format stores across several states. Dollar General plans to relocate existing stores and add fresh food options to these new locations.
2) A survey found that one-third of respondents have already begun holiday planning for 2016, with many starting to save in June or earlier. Respondents expect to spend between $100-$1000 on gifts and other holiday expenses.
3) McDonald's reported weaker-than-expected sales growth in the US, partly due to grocery prices rising more slowly than restaurant prices. Lower grocery inflation is encouraging more people to eat at home.
Este documento describe los platos favoritos, lugares favoritos y eventos que más le gustan a la autora en su ciudad de Barranquilla, Colombia. Algunos de sus platos favoritos incluyen la bandeja paisa y el sancocho de gallina. Sus lugares favoritos son el estadio Metropolitano, el zoológico y las playas. El evento anual que más disfruta es el Carnaval de Barranquilla.
Dollar General buys 41 former Walmart Express stores
- Walmart abandoned its small-format Walmart Express stores in January 2016, closing all 102 locations
- Dollar General has purchased 41 of the former Walmart Express stores located across almost a dozen states
- Dollar General plans to relocate some existing stores to the larger Walmart Express locations and add fresh produce and meat to shelves
[PDF] Pressemitteilung: Hollywood-Stylist Ken Pavés präsentiert bei HSE24 innovative Haarverlängerung hairdo aus Amerika
[http://www.lifepr.de?boxid=106785]
This document is a resume for Kaycee Aquino, a 16-year-old student currently completing Year 10 at St Columba's College in Essendon, Victoria, Australia. It outlines her education, work experience including volunteering and babysitting, employment history helping in her father's workplace, and key employability skills such as communication, problem solving, and teamwork. Her hobbies include soccer, piano, tuba, volleyball, and helping others.
A economia é o estudo da produção, distribuição e consumo de bens e serviços. Ela busca entender como os recursos escassos são alocados para satisfazer as necessidades humanas ilimitadas. A economia usa métodos quantitativos e qualitativos para analisar decisões individuais e coletivas relacionadas a escolhas sobre como usar recursos escassos.
Este documento presenta una secuencia didáctica para enseñar figuras geométricas a niños de primer grado utilizando objetos, software educativo y actividades prácticas. La lección comienza identificando formas básicas, luego los estudiantes encuentran ejemplos en el salón de clase y sacan objetos al azar de una caja mágica. Más tarde usan un juego en línea para crear figuras, y finalmente construyen objetos con formas geométricas.
Este documento contiene información sobre un estudiante de ingeniería química en su primer año que está tomando la asignatura de física básica durante el año 2016-2017 en El Oro, Ecuador.
The document discusses food and beverage services, with a focus on alcoholic beverages and wines. It defines key terms like food, beverage, and different types of alcoholic and non-alcoholic drinks. It also covers the production of wines, including important factors like grapes, climate, soil and winemaking process. Finally, it discusses various wine-producing regions and countries around the world.
Planning is the most
difficult process in
project management.
The framework described
is called the Stepwise
method to help to
distinguish it from
other methods.
This document outlines a step-wise process for project planning. It describes 6 main steps: 1) identify project scope and objectives, 2) identify project infrastructure, 3) analyze project characteristics, 4) identify project products and activities, 5) estimate effort for each activity, and 6) identify activity risks. Each step contains several sub-steps to thoroughly plan the project. The goal is to establish a structured framework to help distinguish this planning method from others and ensure all critical aspects are considered to maximize the project's success.
CAPM exam preparation developed for self learning.
Plz don't mind some logo and strikethrough.. they were meant to create fun for myself.
You may join the course from Udemy as I take and enjoy the class from there.
With discount it was only $11.
Mr.Joseph Phillips
https://www.udemy.com/share/101WE2AkcZd15VRn4=/
PRINCE2 is a structured project management methodology used widely in the UK. It covers the planning stage of projects with 10 defined steps: (1) select the project, (2) identify scope and objectives, (3) analyze characteristics, (4) identify products and activities, (5) estimate effort, (6) identify risks, (7) allocate resources, (8) review the plan, (9) execute the plan, and (10) conduct lower-level planning as needed. The document then provides details on each of the 10 planning steps and how to implement them for effective project management.
This document outlines an agenda for a project kickoff meeting covering introductions, an agile project charter, responsibilities assignment, communication plans, change management, risk management, quality management, and a high-level project plan. It includes a project vision statement, scope, stakeholders, and methodology overview. Documentation like status reports, backlogs, and a project repository are also discussed.
The document discusses key aspects of project evaluation including:
1) It defines project evaluation as both a value judgement of the subject and a process of gathering information for decision making.
2) It outlines the evaluation process of measurement, comparison, and description leading to decisions.
3) It discusses the importance of evaluating projects for improving management and implementation through gathering information on objectives, costs, effects and recommendations.
The document discusses key aspects of project evaluation including:
1) It defines project evaluation as both a value judgement of the subject and a process of gathering information for decision making.
2) It outlines the evaluation process of measurement, comparison, and description leading to decisions.
3) It discusses the importance of evaluating projects for improving management and implementation through gathering information on objectives, costs, effects and recommendations.
This document outlines the 10 step process for step-wise project planning for software projects. The 10 steps are: 1) identify project scope and objectives, 2) identify project infrastructure, 3) analyze project characteristics, 4) identify project products and activities, 5) estimate effort for each activity, 6) identify activity risks, 7) allocate resources, 8) review and publicize the plan, 9) execute the plan, and 10) conduct lower level planning as more details emerge. The goal of these steps is to ensure project tasks are well coordinated and meet objectives like timely completion through processes like stakeholder analysis, risk assessment, and resource planning.
A project audit examines all aspects of a project including its management, methodology, records, budgets, expenditures, and completion status. The purpose is to evaluate project performance, identify strengths and weaknesses, and provide recommendations to improve the project and future projects. Key aspects reviewed include current and future project status, progress on crucial tasks, risk assessment, lessons learned, and assumptions or limitations of the audit. The audit report documents findings on these aspects.
We provide live online tutoring which can be accessed at anytime and anywhere according to student’s convenience. We have tutors in every subject such as Math, Chemistry, Biology, Physics and English whatever be the school level. Our college and university level tutors provide engineering online tutoring in areas such as Computer Science, Electrical and Electronics engineering, Mechanical engineering and Chemical engineering.
• www.onlineassignmenthelp.com.au
• www.cheapassignmenthelp.co.uk
• www.freeassignmenthelp.com
• www.cheapassignmenthelp.com.au
• http://btechndassignment.cheapassignmenthelp.co.uk/
Final Class Presentation on Project Audit and Closure.pptGeorgeKabongah2
To understand the process of project audit
To recognize the value of an audit to project management
To determine when to terminate a project
To identify various reasons why a project is terminated
To identify checklist
A project audit evaluates the progress and performance of a project compared to its planned objectives. It examines all aspects of a project including its management, methodology, budgets, and completion status. The audit report assesses the current status, future projections, critical tasks, risks, and lessons learned. It follows a life cycle of initiation, baseline definition, data collection, analysis, reporting, and termination. The auditor maintains independence and objectivity to truthfully evaluate the project's strengths and weaknesses.
Do you know what is the main factor that determines a successful project? At Savvycom, we believe that good project management is the key. Therefore, we conducted a training workshop on this topic for our team to have a good understanding of the project management. During the workshop, we went through the basic definitions to very advanced techniques and tips. We do hope that after the workshop, our member will be equipped with essential tools to manage project more effectively.
Freelancer Magento Experts model allows you to hire designers on full-time, part-time or hourly basis. This model can save you at least 30% of cost against any fixed price quotes calculated even at $15/hr.
Unlike the freelancing project portals, we are accountable for the results and ensure that only qualified designers work for you. The designers that you hire will be our full-time employees and they will work exclusively on your assignments for the duration of the contract. It's the easiest way to get design projects done. We guarantee it!
We are dedicated to help our clients continually grow and succeed in their online business and we incorporate this dedication into every thread of what we do. Our values aren't just something we list on our site. We believe in them. Recruit by them. Review by them. And work according to them.
Our numbers speak for themselves. With a proven track record to deliver creative, robust and most importantly, increasingly profitable eCommerce sites, our diverse group of experts are committed to customer satisfaction and project excellence.
Topic 1a overview program and project structuresAllan Cunningham
This document provides an overview of key concepts in program and project management. It discusses strategies, governance structures, life cycles and phases. Some key points:
- Programs are groups of related projects managed in a coordinated way to obtain benefits not available from managing them individually. Projects are temporary endeavors that create unique products or services.
- A program life cycle typically includes phases for pre-program setup, program setup, establishing management, delivering benefits, and closing the program.
- A project life cycle usually involves initiation, planning, execution, monitoring and control, and closeout phases.
- Governance structures for programs include a program board, steering committee, and program/project champions. Programs and
The document discusses the process for closing projects, including administrative closure, performance evaluations, and project audits. It outlines the key activities for project closure like assigning closure tasks and monitoring implementation. The project audit process is also summarized, including collecting data from the project team, organization, and stakeholders to identify lessons learned and areas for improvement on future projects.
Sonia Usih presented the project kickoff meeting for a new change implementation project. The presentation included an overview of the project phases and management plans, as well as a review of the project scope, status, issues, next steps, and questions. Key topics discussed were the communication plan, risk plan template, quality plan template, fulfillment by the company and vendor, and future perspectives.
Sonia Usih presented the project kickoff meeting for a new change implementation project. The presentation included an overview of the project phases and management plans, as well as a review of the project scope, status, issues, next steps, and questions. Key topics discussed were the communication plan, risk plan template, quality plan template, fulfillment by the company and vendor, and future perspectives.
This document outlines the process of evaluating forest business management projects. It discusses that project evaluation is a systematic assessment of ongoing or completed projects to determine their objectives, effectiveness, efficiency, impact, and sustainability. The key steps of project evaluation include:
1) Setting evaluation questions regarding project effectiveness, efficiency, rationale, and equity.
2) Identifying stakeholders and their information needs.
3) Developing evaluation questions based on stakeholder priorities.
4) Tracking project outputs and outcomes to measure results.
5) Creating a communication plan to share evaluation findings with stakeholders.
1. Data Governance Risk Assessment Process
A guide to classifying, assessing and scoring projects for Data
Governance (DG) Risk and monitoring their improvement.
2. Data and Data Governance
This purpose of this process is to improve the way that projects and project portfolios
govern their data. To do this, we must first define data and data governance.
Data
Facts and artifacts as found or created in data sets, files, or
databases from clients, third party providers, and our teams
including markups and reviewer notes as well as qualitative,
quantitative, analytic, and summary data.
Data Governance
(DG)
Standards based management of data and accountability for
its integrity and control throughout its life cycle.
3. 1. First
Project
Review
2. Pre-Second
Project
Review
3. Second
Project
Review
4. Third to nth
Project
Review
Data Governance Risk Assessment Process
Process Inception 1-2 Months Following
Inception
2 Months Following
Inception
Every 60 days following
4. Project Types for DG Classification
Review Only
- Review reports and other information from clients and provide insight through advice,
suggestions, and recommendations
Maturity Level 1
- Query and analyze data without transformation (e.g. changing or adding)
- Produce or download a table, report, or other outputs from a public data source
Maturity Level 2
- Acquire, collect, or produce data
- Adhere to contract and related agreement or license conditions for data
- Analyze and transform (e.g. change or add to) data for the purpose of producing
analytic output
- Enforce limited access to data
Maturity Level 3
- Make changes to correct or improve permanent data
- Produce a new data set that will be used by others or published and that persists on its
own
- Produce a data set intended for analysis that is delivered to a client for use or
publication
Projects in each of these categories perform the following activities:
RiskIncrease
5. 1. First Project
Review
Process Inception
2. Pre-Second
Project Review
1-2 Months
Following Inception
3. Second
Project Review
2 Months Following
Inception
4. Third to nth
project review
Every 60 days
following
DG Risk Assessment Process Outline
Activity Classify 1 Assess Classify 2 Assess Review Review
Review Only ✔ N/A N/A N/A N/A
Maturity Level
1
✔ ✔ ✔ ✔
Maturity Level
2
✔ ✔ ✔ ✔ ✔
Maturity Level
3
✔ ✔ ✔ ✔ ✔
Project Type
6. 1. First Project Review
Time Process Inception
Review Only
Classify 1
Interview project managers about basic Data Governance (DG) Activity requirements
Determine projects that do not deal with governable data of any kind (e.g. advice, suggestions, and recommendations)
Maturity Level 1
Classify 1 Assess
Interview project managers about basic DG Activity requirements
Interview project managers about Level 1 DG Activity
requirements
Determine and designate Maturity Level 1 Projects
Determine weighted risk score based on Maturity Level
and responses to Level 1 DG Activities interview
Define and plan policies and procedures, based on
weighted risk score, to satisfy DG requirements
Determine action items going forward
Maturity Level 2
Classify 1
Interview project managers about basic DG Activity requirements
Determine and designate Maturity Level 2 or 3 Projects
Maturity Level 3
Classify 1
Interview project managers about basic DG Activity requirements
Determine and designate Maturity level 2 or 3 Projects
Project Type
7. 2. Pre-Second Project ReviewProject Type
Time 1-2 Months Following Inception
Review Only
Maturity Level 1
Maturity Level 2
Classify 2 Assess
Interview project managers about Level 2 and 3 DG Activity
requirements
Interview project managers about Maturity Level 1 and 2 Activity
requirements
Determine and designate Maturity Level 2 Projects
Determine weighted risk score based on Maturity Level and
responses to Level 1 and 2 DG Activities interview
Define and plan policies and procedures, based on weighted risk
score, to correct issues in DG Activities
Maturity Level 3
Classify 2 Assess
Interview project managers about Level 2 and 3 DG Activity
requirements
Interview project managers about Maturity Level 1, 2, and 3
Activity requirements
Determine and designate Maturity Level 3 Projects
Determine weighted risk score based on Maturity Level and
responses to Level 1, 2, and 3 Activities interview
Define and plan policies and procedures, based on weighted risk
score, to correct issues in DG Activities
8. 3. Second Project ReviewProject Type
Time 2 Months Following Inception
Review Only
Maturity Level 1
Review
Review progress in fulfilling action items
Re-answer risk assessment questions
Evaluate progress in decreasing risk footprint
Determine action items going forward
Maturity Level 2
Review
Determine action items going forward
Maturity Level 3
Review
Determine action items going forward
9. 4. Third to nth Project ReviewProject Type
Time Every 60 days following
Review Only
Maturity Level 1
Review
Review progress in fulfilling action items
Re-answer risk assessment questions
Evaluate progress in decreasing risk footprint
Determine action items going forward
Maturity Level 2
Review
Review progress in fulfilling action items
Re-answer risk assessment questions
Evaluate progress in decreasing risk footprint
Determine action items going forward
Maturity Level 3
Review
Review progress in fulfilling action items
Re-answer risk assessment questions
Evaluate progress in decreasing risk footprint
Determine action items going forward
10. Data Advisor Skills (Cumulative)
White Belt Green Belt Black BeltBrown Belt
• Has general
knowledge on the
subject of data
governance
• Understands the 15
key data governance
activities
• Has taken at least one
project of any type
through the risk
assessment process
• Has taken multiple
projects of multiple
types through the risk
assessment process
• Has trained another
data advisor into a
brown belt
• Has taken projects of
all levels through the
risk assessment
process
11. First Project Review
Objectives:
• Part 1: Classify 1(All projects)
• Determine which projects do not deal with governable data at all (e.g. advice,
suggestions, and recommendations)
• Determine and designate Maturity Level 1 projects
• Determine Maturity Level 2 or 3 projects
• Parts 2, 3, 4, and 5: Assess (Level 1 Projects only)
• Assess the compliance of Level 1 projects with the first five key DG Activities
• Score Level 1 projects based on their level of compliance
• Define and plan appropriate policies and procedures
• Determine Action items going forward
12. First Project Review
Part 1 - Classify 1
- To begin the interview at the first project review, the projects must
first be classified into their appropriate maturity Levels
- At this point, it is only relevant to separate Maturity Level 1 projects
from Maturity Level 2 and 3 Projects.
- Determine and designate which projects are Maturity Level 1 by
asking project managers during their project review whether their
projects perform any of the activities in each question
13. First Project Review
Part 1 - Classify 1
1. In this project, does your team:
a. Review reports and other information from clients and
provide insight through advice, suggestions, and
recommendations
2. In this project, does your team: (select all that apply)
a. Query and analyze data without transformation (e.g.
changing or adding)
b. Produce or download a table, report, or other outputs from
a public data source
3. In this project, does your team: (select all that apply)
a. Acquire collect, or produce data
b. Adhere to contract and related agreement or license conditions
for data
c. Analyze and transform (e.g. change or add to) data for the
purpose of producing analytic output
d. Enforce limited access to data
4. In this project, does your team handle data which falls under
any of the following restrictions: (select all that apply)
a. PPI - Personal protected information
b. PII- Personal identifying information
c. HIPAA- Health insurance portability and accountability act
d. FERPA- Family educational rights and privacy act
14. First Project Review
Part 1 - Classify 1
To determine the Maturity Level of the project being assessed and
finish classifying Maturity Level 1 projects, follow the directions below:
1. If a project selects an answer for question 1 and does not select an answer for
any of the following questions, they are a Review Only project
2. If a project selects any answer to question 2 and does not select an answer for
any of the following questions, they are a Maturity Level 1 Project
3. If a project selects any answer to question 3, they are a Maturity Level 2 or 3
project
4. If a project selects any answer to question 4, they are a Maturity Level 2 or 3
project
15. First Project Review
Part 2 - Assess
- At this time, ONLY Maturity Level 1 projects are assessed to
determine a weighted risk score
- The following five questions assess a Maturity Level 1 project’s
compliance with the first five key DG activities, and project managers
should answer them to the best of their ability
16. First Project Review
Part 2 - Assess (Question 1)
1. Which of the following statements best describes the way you and your project
team capture and communicate project data requirements*?
a. Automated: Our team uses an automated system that captures and communicates project
data requirements
b. Written and Reviewed: Our team documents project data requirements in writing, which I
then review
c. Written: Our team documents project data requirements in writing
d. Verbal: Our team discusses project data requirements
e. None: Our team does not document or discuss project data requirements in any way
*Project Data Requirements: Specifications describing the content, format, and structure of the data.
17. First Project Review
Part 2 - Assess (Question 2)
2. On this project, is your team maintaining a catalog of your data with information
about its location, sensitivity, and type?
a. Automated: Our team uses an automated system that maintains a catalog of our data
b. Written and Verified: Our team documents how it maintains a catalog of our data, which I
then review
c. Written: Our team documents how it maintains a catalog of our data
d. Verbal: Our team discusses how it maintains a catalog of our data
e. None: Our team does not have a method for maintaining a catalog of our data
18. First Project Review
Part 2 - Assess (Question 3)
3. Which of the following statements best describes the way you and your project
team control the location, movement, copying, and backup of your data?
a. Automated: Our team uses an automated system controls the locations, movements,
copying, and backup of our data
b. Written and Reviewed: Our team documents how it controls the locations, movements,
copying, and backup of our data, which I then review
c. Written: Our team documents how it controls the locations, movements, copying, and
backup of our data
d. Verbal: Our team discusses how it controls the locations, movements, copying, and backup
of our data
e. None: Our team does not have a method for controlling the locations, movements,
copying, and backup of our data
19. First Project Review
Part 2 - Assess (Question 4)
4. Which of the following statements best describes the way you and your project
team capture information about your data in tags* or the data catalog?
a. Automated: Our team has an automated system that captures information about our data
in tags or the data catalog
b. Written and Reviewed: Our team documents how it captures information about our data
in tags or the data catalog, which I then review
c. Written: Our team documents how it captures information about our data in tags or the
data catalog
d. Verbal: Our team discusses how it captures information about our data in tags or the data
catalog
e. None: Our team does not have a method for capturing information about our data in tags
or the data catalog
*Tags: Small attachments that accompany data files and include information about them, such as content, classification, or owner.
20. First Project Review
Part 2 - Assess (Question 5)
5. Which of the following statements best describes the way you and your project
team ensure data destruction, return, or retention requirements are complete &
assigned as part of project close out preparation?
a. Automated: Our team uses an automated system which assigns data destruction, return,
or retention requirements
b. Written and Reviewed: Our team documents data destruction, return, or retention
requirements, which I then review
c. Written: Our team documents data destruction, return, or retention requirements
d. Verbal: Our team discusses data destruction, return, or retention requirements
e. None: Our team does not have a plan that addresses this
21. First Project Review
Part 3 – Score (Maturity Level 1)
- Only Maturity Level 1 projects, who have answered the preceding
five questions, can be given a risk score at this time
- The answers the the preceding five questions will determine the
weighted score the project will receive, and Maturity Table 1 will be
used to weigh the relative risk of each answer to each question
23. Directions for use:
1. Match the question number to the activity number in the far left column
2. Match response options at the beginning of the answer selected to one of the
responses at the top of the columns, record the score
3. Repeat for each of the questions
4. Sum the scores to create the total weighted risk score
5. Record this score in the project review system
First Project Review
Part 3 – Score (Maturity Level 1)
24. First Project Review
Part 4 - Define and Plan DG Procedures
Procedure Table 1
Activity None Verbal Written Reviewed Automated
Activity 5
Data return &
destruction
Engage TS, DA and IT to ensure all data retention, return and destruction requirements
identified in Activity 1 are fully planned and supported based on contract and policy
terms and dates. This includes data classification and retention policy validation with
Das, CISO and CPO. 0
Activity 4
Tagging or
Metadata creation
Engage TS & DA to determine the best approach to maintaining required metadata from
Activity 1 with the data (tags) or specify catalog based capture & maintenance in Activity
2 0
Activity 3
Maintain inventory
Create a regular update of all data created, acquired to changed by the project using the
catalog template from Activity 2 N/A
Activity 2
Data catalog
requirements
Apply the data requirements captured in Activity 1 to define your project data catalog
template N/A
Activity 1
Analytic
requirements
Engage TS and DA to provide templates and support for written capture with a standard
review process N/A
Maturity
Level 1:
Defined
25. - Based on a project’s answers to the five risk assessment questions,
define and assign action items that the project must address moving
forward in order to improve their compliance with DG activities and
decrease their risk footprint
First Project Review
Part 5 – Action Items
26. Pre-Second Project Review
Objectives:
• Part 1: Classify-2 (Maturity Level 2 and 3 Projects)
• Determine and designate Maturity Level 2 Projects
• Determine and designate Maturity Level 3 Projects
• Parts 2, 3, 4, and 5: Assess (Maturity Level 2 and 3 Projects)
• Assess the compliance of Level 2 projects with the first 10 key DG Activities
• Score Level 2 projects based on their level of compliance
• Assess the compliance of Level 3 projects with all 15 key DG Activities
• Score Level 3 Projects based on their level of compliance
• Define and plan appropriate policies and procedures
• Create a Final Project Report
27. Pre-Second Project Review
Part 1 - Classify 2
- At this point, Maturity Level 2 and 3 projects must be differentiated
and designated appropriately
- The following questions should be asked of the project managers
about their current project during their pre-second project review to
determine the Maturity Level of their project
28. Pre-Second Project Review
Part 1 - Classify 2
1. In this project, does your team: (check all that
apply)
a. Acquire, collect, or produce data
b. Adhere to contract and related agreement or
license conditions for data
c. Analyze and transform (e.g. change or add to)
data for the purpose of producing analytic output
d. Enforce limited access to data
2. In this project, does your team: (check all that
apply)
a. Make changes to correct or improve permanent
data
b. Produce a new data set that will be used by others
or published and that persists on its own
c. Produce a data set intended for analysis that is
delivered to a client for use or publication
29. Pre-Second Project Review
Part 1 - Classify 2
To determine the Maturity Level of the project being assessed and
finish classifying Maturity Level 2 and 3 projects, follow the directions
below:
1. If a project selects any answer to question one and does not select any of the
answers to the following question, they are a Maturity level 2 project
2. If a project selects any answer to question 2, they are a Maturity Level 3
Project
30. Pre-Second Project Review
Part 2 - Assess
- The risk assessment should now be done for both Maturity Level 2
and 3 projects
- First, answer the first five questions from part 3 of the first tier
interview, then answer the following five questions
31. Pre-Second Project Review
Part 2 - Assess (Question 6)
6. Which of the following statements best describes the way you and your project
team define, enforce, and monitor limited access to your data?
a. Automated: Our team uses an automated system that enforces limited access to our data
and generates automatic reports
b. Written and Reviewed: Our team documents how it defines, enforces, and monitors
limited access to our data, which I then review
c. Written: Our team documents how it defines, enforces, and monitors limited access to our
data
d. Verbal: Our team discusses how it defines, enforces, and monitors limited access to our
data
e. None: Our team does not have a method for defining, enforcing, and monitoring limited
access to our data
32. Pre-Second Project Review
Part 2 - Assess (Question 7)
7. Which of the following statements best describes the way you and your project team
enforce change control and versioning* for all of your project data and data sets?
a. Automated: Our team uses an automated system that enforces change control and versioning
for all of our project’s data and data sets
b. Written and Reviewed: Our team documents how it enforces change control and versioning for
all of our project’s data and data sets, which I then review
c. Written: Our team documents how it enforces change control and versioning for all of our
project’s data and data sets
d. Verbal: Our team discusses how it enforces change control and versioning for all of our project’s
data and data sets
e. None: Our team does not have a method for enforcing change control and versioning for its
data and data sets
*Change control and versioning: The creation and management of multiple releases of a data set
33. Pre-Second Project Review
Part 2 - Assess (Question 8)
8. Which of the following statements best describes the way you and your project
team ensure data destruction, return, or retention execution as required?
a. Automated: Our team has an automated system that destroys, returns, or retains data as
required
b. Written and Reviewed: Our team documents how it ensures data destruction, return, or
retention execution as required, which I then review
c. Written: Our team documents how it ensures data destruction, return, or retentions
execution as required
d. Verbal: Our team discusses how it ensures data destruction, return, or retention execution
as required
e. None: Our team does not have a method for ensuring data destruction, return, or
retention execution as required
34. Pre-Second Project Review
Part 2 - Assess (Question 9)
9. Which of the following statements best describes the way you and your project
team identify and report any data events*?
a. Automated: Our team uses an automated system that identifies and reports any data
events
b. Written and Reviewed: Our team documents how it identifies and reports data events,
which I then review
c. Written: Our team documents how it identifies and reports data events
d. Verbal: Our team discusses how it identifies and reports data events
e. None: Our team does not have a method for identifying and reporting data events
*Data Events: Events that put data, privacy, or security at risk
35. Pre-Second Project Review
Part 2 - Assess (Question 10)
10. Which of the following statements best describes the way you and your project
team ensure compliance with data usage agreements, contract terms for data use,
and restricted use license terms?
a. Automated: Our team uses an automated system that ensures compliance with data usage
agreements, contract terms for data use, and restricted use license terms
b. Written and Reviewed: Our team documents how it ensures compliance with data usage
agreements, contract terms for data use, and restricted use license terms, which I then
review
c. Written: Our team documents how it ensures compliance with data usage agreements,
contract terms for data use, and restricted use license terms
d. Verbal: Our team discusses how it ensures compliance with data usage agreements,
contract terms for data use, and restricted use license terms
e. None: Our team does not have a method for ensuring compliance with data usage
agreements, contract terms for data use, and restricted use license terms
36. Pre-Second Project Review
Part 2 - Assess
- This section of the risk assessment should ONLY be done for Maturity
Level 3 projects
- Once a Maturity Level 3 project has answered the preceding ten
questions, they complete the following four or five
37. Pre-Second Project Review
Part 2 - Assess (Question 11)
11. Which of the following statements best describes the way you and your project
team evaluate data quality, including adherence to data requirements, and identify
necessary corrections or improvements?
a. Automated: Our team uses an automated system that evaluates data quality, including
adherence to data requirements, and identifies necessary corrections or improvements
b. Written and Reviewed: Our team documents how it evaluates data quality, including
adherence to data requirements, and how it identifies necessary corrections or
improvements, which I then review
c. Written: Our team documents how it evaluates data quality, including adherence to data
requirements, and how it identifies necessary corrections or improvements
d. Verbal: Our team discusses how it evaluates data quality, including adherence to data
requirements, and how it identifies necessary corrections or improvements
e. None: Our team does not have a method for evaluating data quality, including adherence
to data requirements, or identifying necessary corrections or improvements
38. Pre-Second Project Review
Part 2 - Assess (Question 12)
12. Which of the following statements best describes the way you and your project
team execute corrections & improvements with change history*?
a. Automated: Our team uses an automated system that executes corrections and
improvements with change history
b. Written and Reviewed: Our team documents how it executes corrections and
improvements with change history, which I then review
c. Written: Our team documents how it executes corrections and improvements with change
history
d. Verbal: Our team discusses how it executes corrections and improvements with change
history
e. None: Our team does not have a method for executing corrections and improvements with
change history
*Change history: Documentation of changes to a product or system that are introduced in a controlled and coordinated manner
39. Pre-Second Project Review
Part 2 - Assess (Question 13)
13. Which of the following statements best describes the way you and your project
team verify data changes in new versions?
a. Automated: Our team uses an automated system that verifies data changes in new
versions
b. Written and Reviewed: Our team documents how it verifies data changes in new versions,
which I then review
c. Written: Our team documents how it verifies data changes in new versions
d. Verbal: Our team discusses how it verifies data changes in new versions
e. None: Our team does not have a method for verifying data changes in new versions
40. Pre-Second Project Review
Part 2 - Assess (Question 14)
14. Which of the following statements best describes the way you and your project
team promote new versions of data and verify analytic logic?
a. Automated: Our team uses an automated system that promotes new versions of data and
verifies analytic logic
b. Written and Reviewed: Our team documents how it promotes new versions of data and
verifies analytic logic, which I then review
c. Written: Our team documents how it promotes new versions of data and verifies analytic
logic
d. Verbal: Our team discusses how it promotes new versions of data and verifies analytic logic
e. None: Our team does not have a method for promoting new versions of data and verifying
analytic logic
*Analytic logic: analysis formulae, rules & logic, coding, scripts and other automation routines
41. Pre-Second Project Review
Part 2 – Assess
- This section of the risk assessment should ONLY be done for Maturity
Level 3 projects where data advisors have determined that the
following DG activity is relevant
42. Pre-Second Project Review
Part 2 - Assess (Question 15)
15. Which of the following statements best describes the way you and your project team
test corrected or improved data with an analytic script or program* to confirm integrity?
a. Automated: Our team uses an automated system that tests corrected or improved data with an
analytic script or program to confirm integrity
b. Written and Reviewed: Our team documents how it tests corrected or improved data with an
analytic script or program to confirm integrity, which I then review
c. Written: Our team documents how it tests corrected or improved data with an analytic script or
program to confirm integrity
d. Verbal: Our team discusses how it tests corrected or improved data with an analytic script or
program to confirm integrity
e. None: Our team does not have a method for testing corrected or improved data with an
analytic script or program to confirm integrity
*Analytic script or program: analysis formulae, rules & logic, coding, scripts and other automation routines
43. Pre-Second Project Review
Part 3 - Score (Maturity Levels 2 and 3)
- Maturity Level 2 and 3 projects, who have answered the appropriate
number of questions, can be given a risk score at this time
- The answers the the appropriate ten to fifteen questions determine
the weighted risk score for the project
45. Directions for use:
1. Match the question number to the activity number in the far left column
2. Match response options at the beginning of the answer selected to one of the
responses at the top of the columns, record the score
3. Repeat for each of the questions
4. Sum the scores to create the total weighted risk score
5. Record this score in the project review system
Pre-Second Project Review
Part 3 - Score (Maturity Level 2)
47. Directions for use:
1. Match the question number to the activity number in the far left column
2. Match response options at the beginning of the answer selected to one of the
responses at the top of the columns, record the score
3. Repeat for each of the questions
4. Sum the scores to create the total weighted risk score
5. Record this score in the project review system
Pre-Second Project Review
Part 3 - Score (Maturity Level 3)
48. Procedure Table 2 (Activities 6-10)
Pre-Second Project Review
Part 4 - Define and Plan DG Procedures
Activity None Verbal Written Reviewed Automated
Maturity
Level 2:
Activity 10
Data agreement compliance
Engage DA to help monitor compliance including required
reports from Activities 8,9, & 10 N/A
Controlled Activity 9
Periodic Updates
Engage DA to assist with periodic update requirements
N/A
Activity 8
Data Deletion
Engage DA to identify verification reports required from IT
as part of project data destruction and retention
requirements
N/A
Activity 7
Change Control
Engage DA to assist with change control requirements,
settings and alerts, then engage TS to apply with IT
N/A
Activity 6
Access Control
Engage with DA, TS and IT to obtain access control rights
by person and recieve ongoing access audit trail reports
N/A
49. Procedure Table 2 (Activities 11- 15)
Pre-Second Project Review
Part 4 - Define and Plan DG Procedures
Activity None Verbal Written Reviewed Automated
Maturity
Level 3:
Activity 15
Verify data & analytic integrity
Engage DA and TS as needed to support data corrections
and verification process
N/A
Improved
Activity 14
Data & Analytic production control
Engage DA and TS as needed to control promotion of new
versions of analytic scripts and data sets to shared use and
publication (production)
N/A
Activity 13
Verify data corrections
Engage DA and TS as needed to support data corrections
and verification process N/A
Activity 12
Data correction & improvement
Engage DA and TS as needed to support data corrections
and verification process
N/A
Activity 11
Data Requirements Adherence
Engage DA to help monitor requirements satisfaction from
Activities 1 and 13
N/A
50. Objectives
• Part 1: Review (Level 1 projects)
• Review progress in fulfilling action items
• Re-answer risk assessment questions
• Evaluate progress in decreasing risk footprint
• Determine action items going forward
• Part 1: Review (Level 2 and 3 projects)
• Determine action items going forward
Second Project Review
51. - Based on the action items determined in Part 5 of the first project review,
determine which have and which have not been fulfilled
- Have each project manager, on their own before the second project review, re-
answer the five questions they previously answered during Part 2 of the first
project review and determine a new risk score
- Determine where each project has improved, regressed, or plateaued across
each of the five DG activities
- Determine which action items should be renewed and what new action items
should be addressed moving forward
Second Project Review
Part 1 – Review (Maturity Level 1)
52. - Based on a project’s answers to the appropriate risk assessment
questions, define and assign action items that the project must
address moving forward in order to improve their compliance with
DG activities and decrease their risk footprint
Second Project Review
Part 1 – Review (Maturity Levels 2 and 3)
53. Objectives:
Part 1: Review (All projects)
• Review progress in fulfilling action items
• Re-answer risk assessment questions
• Evaluate progress in decreasing risk footprint
• Determine action items going forward
Third to nth Project Review
54. - Based on the action items determined in previous project reviews, determine
which have and which have not been fulfilled
- Have each project manager, on their own before the third and following project
reviews, re-answer questions they previously answered during the first project
review or pre-second project review and determine a new risk score
- Determine where each project has improved, regressed, or plateaued across
each of the appropriate DG activities
- Determine which action items should be renewed and what new action items
should be addressed moving forward
Third to nth Project Review
Part 1 - Review
Get language from Sandy about the second classify option for review only
Q1: If a project selects any answer to this questions and does not select any of the answers to the following question, they are a Maturity level 2 project
Q2: If a project selects any answer to this question, they are a Maturity Level 3 Project