Knowledge Nugget

When to raise an alert – practical examples
person Author: Process Fellows
There could be many scenarios where a notification about a problem should be send to relevant stakeholders (typically outside of the project, where the problem was identified). Do not mix this up with the need for urgent resolution or escalation. First of all we are talking about a notification only. But of course, depending on the impact of the problem, the notified stakeholders could ask for an urgent action.
  • Example Scenario 1 – Cross-Project Component Dependency
    • Context: Project A is reusing a component or platform that was originally delivered and is currently maintained by another project, Project B.
    • Situation: Project A identifies a problem, and the root cause is traced back to the reused component from Project B. In this case, Project A must inform Project B about the issue.
    • Urgency and Impact: Depending on the severity and impact of the problem, this may require an urgent resolution action from Project B. In addition, project B must assess whether the affected component is also being used by other projects (e.g., project C). If so, project B is responsible for informing all dependent projects to ensure coordinated communication and risk mitigation.
  • Example Scenario 2 - Cross-Generational Product Issue Escalation
    • Context: Project B is developing a "next-generation" version of a product that was originally created by Project A as the "first-generation" version.
    • Situation: During development, Project B identifies a problem. A root cause analysis reveals that the same issue also affects the first-generation product. Despite thorough qualification during its initial development, the problem was not detected earlier. The first-generation product is already in mass production and has been released to the market.
    • Urgency and Impact: Depending on the severity of the issue, corrective actions may include a product recall. Additionally, customers who have purchased the first-generation product may need to be proactively informed and warned about potential risks associated with continued use.
Mapped with these items:
  • Automotive SPICE 4.0
    • SUP.9.BP4 Raise alert notifications.
  • Automotive SPICE Potential Analysis 1.0
    • TEPR Technical Problem Resolution