DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

How does AI transform chaos engineering from an experiment into a critical capability? Learn how to effectively operationalize the chaos.

Data quality isn't just a technical issue: It impacts an organization's compliance, operational efficiency, and customer satisfaction.

Are you a front-end or full-stack developer frustrated by front-end distractions? Learn to move forward with tooling and clear boundaries.

Developer Experience: Demand to support engineering teams has risen, and there is a shift from traditional DevOps to workflow improvements.

Related

  • Top Book Picks for Site Reliability Engineers
  • Security Considerations for Observability: Enhancing Reliability and Protecting Systems Through Unified Monitoring and Threat Detection
  • Key Strategies on How to Advance Your Digital Tech Career
  • Books To Start Your Career in Cloud, DevOps, or SRE in 2024

Trending

  • Beyond Java Streams: Exploring Alternative Functional Programming Approaches in Java
  • How to Improve Software Architecture in a Cloud Environment
  • How Node.js Works Behind the Scenes (HTTP, Libuv, and Event Emitters)
  • AI-Native Platforms: The Unstoppable Alliance of GenAI and Platform Engineering
  1. DZone
  2. Culture and Methodologies
  3. Methodologies
  4. Mid-Mortem Should Not Be Optional

Mid-Mortem Should Not Be Optional

The primary objective of a mid-mortem is to evaluate the current status of the project and its challenges in relation to its predetermined goals and milestones.

By 
KARANVEER ANAND user avatar
KARANVEER ANAND
·
May. 19, 24 · Opinion
Likes (4)
Comment
Save
Tweet
Share
3.0K Views

Join the DZone community and get the full member experience.

Join For Free

The majority of program management encompasses two types of post-incident or post-project review: “pre-mortem” and “post-mortem.” A pre-mortem typically occurs during the project initiation phase, where potential risks are forecast before the project begins and a plan to mitigate these risks is developed. In contrast, a post-mortem occurs following the closing phase of the project, where an analysis of “what went well” and “lessons learned” is conducted. This enables the identification of areas for improvement and their incorporation into subsequent releases or other projects.

These exercises are valuable learning and planning tools for every program. A mid-mortem is equally important as the other "mortems." It is essential to understand the nature and significance of a mid-mortem.

What Is a Mid-Mortem?

A mid-mortem, a self-initiated review exercise, can be conducted by anyone involved in the project at any time during its lifecycle. The primary objective of a mid-mortem is to evaluate the current status of the project and its challenges in relation to its predetermined goals and milestones.

How Does a Mid-Mortem Work?

This review is a collaborative effort to address the challenges faced by the project. For each challenge, your team should brainstorm potential impacts and formulate recommendations.

Assessing each challenge thoroughly will enable the creation of a robust recommendation plan approved by program leads. It is important to approach this activity as a team, as different members may have unique perspectives and suggestions for each challenge.

The second part of the mid-mortem is the project review where you measure the project status against the project goals and milestones you have outlined at the beginning of the project.

Once the mid-mortem is complete, the program manager or engineering manager is responsible for ensuring that all approved recommendations are executed promptly. This may involve allocating additional resources, adjusting the project schedule, or making changes to the project plan.

Different Challenges Faced by the Project That You May Need To Consider During a Mid-Mortem

Scope Creep

Potential Impacts

  • Unrealistic project expectations
  • Increased project costs
  • Delays in project completion
  • Reduced project quality
  • Impacts the project timeline
  • This leads to escalation from the management team

Resource Constraints

Potential Impacts

  • Delays in project completion
  • Reduced project quality
  • Increased stress on project team members

Technical Complexity

Potential Impacts

  • Unanticipated technical challenges
  • Delays in project completion
  • Increased project costs

Communication and Collaboration

Potential Impacts

  • Misunderstandings among team members
  • Delays in project completion
  • Reduced project quality

Stakeholder Management

Potential Impacts

  • Unrealistic expectations from stakeholders
  • Delays in project completion
  • Reduced project quality

How It Adds Value

A mid-mortem is unique because it presents an opportunity to assess risks and challenges during project execution. Forecasting risks in a complex, multi-year project is challenging, as during a project things are dynamic and may not go according to plan. This dynamic environment creates a need for a mid-mortem. It is important to note, as previously conveyed, that these activities are not addressed in either the pre-mortem framework due to the absence of precise forecasting capabilities or in the post-mortem framework, as it is beyond the scope of retrospective analysis and action-taking in the post-mortem phase. 

There are various ways in which a mid-mortem adds value:

  • Ensuring timely corrective actions are taken to address project risks
  • Providing clear recommendations for each challenge faced
  • Fostering transparency and alignment among stakeholders and leadership

Conclusion

The midterm review is an essential tool for ensuring the successful completion of any project. By taking the time to assess the project's progress, identify challenges, and make necessary adjustments, project managers can help ensure that their projects are delivered on time, within budget, and to the satisfaction of all stakeholders.

Project management Reliability engineering Site reliability engineering career

Opinions expressed by DZone contributors are their own.

Related

  • Top Book Picks for Site Reliability Engineers
  • Security Considerations for Observability: Enhancing Reliability and Protecting Systems Through Unified Monitoring and Threat Detection
  • Key Strategies on How to Advance Your Digital Tech Career
  • Books To Start Your Career in Cloud, DevOps, or SRE in 2024

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • [email protected]

Let's be friends: