55289-A: Microsoft Project 2019: Digging Deeper — Lesson 4: Reports, Customization, Multiple Projects, and Governance

Learning Objectives

• Explain the role of custom fields, tables, filters, and views in the course scenario.
• Apply visual and built-in reports through a guided implementation or analysis.
• Validate master projects and shared resources using documented evidence and acceptance criteria.
• Troubleshoot risks, quality issues, and operational gaps related to templates, standards, and operational handoff.

Detailed Topics

• Custom Fields, Tables, Filters, And Views: Apply the concept to requirements, configuration, analysis, controls, and expected outcomes.
• Visual And Built-In Reports: Apply the concept to requirements, configuration, analysis, controls, and expected outcomes.
• Master Projects And Shared Resources: Apply the concept to requirements, configuration, analysis, controls, and expected outcomes.
• Templates, Standards, And Operational Handoff: Apply the concept to requirements, configuration, analysis, controls, and expected outcomes.

Guided Demonstration

1. Review the scenario, users, data, dependencies, permissions, risks, and expected result.
2. Demonstrate the relevant configuration, analysis, design, administration, or development workflow step by step.
3. Capture settings, outputs, logs, screenshots, calculations, tests, and other useful evidence.
4. Compare the observed result with acceptance criteria and explain corrective actions.

Hands-on Exercise

1. Translate the scenario into a short implementation or analysis plan.
2. Complete the workflow using the supplied checklist and secure working practices.
3. Test normal, edge, and failure conditions and record the results.
4. Document one improvement that increases quality, security, reliability, usability, or business value.

Validation Checklist

• Requirements, assumptions, owners, and success criteria are documented.
• Configuration or analysis results are supported by reproducible evidence.
• Security, privacy, accessibility, quality, and governance controls are reviewed.
• Errors and unexpected results are investigated before approval.
• The final outcome and next action are communicated clearly.

Troubleshooting and Improvement

Use logs, formulas, queries, settings, permissions, test outputs, and stakeholder feedback to isolate the cause of a problem. Correct the smallest verified cause first, retest the complete workflow, document the evidence, and add the learning to the final improvement plan.