ReviewShield Critical Path Action On Node Analysis

The purpose of this narrative is to explain the ReviewShield Critical Path Method (CPM) and how it can be applied to the ReviewShield project using an Activity on Node (AON) diagram.

The ReviewShield Phase 1 AON is presented below. The tasks represent key actions and dependencies that need to be completed. Please note, the duration estimates below are based on the best-guess efforts and not the actual work efforts

Tasks and Dependencies

A: Define Requirements

A.1: Develop Customer-centric and Business Outcome focused SMART Goal

1. • 1. 1. Duration: 2 weeks

        2. Dependencies: None

A.2: Develop Success Metrics and reporting KPIs

1. Duration: 2 weeks

2. Dependencies: A.1

A.3: Develop a KPI reporting Spreadsheet Prototype and high-level resource estimation

1. Duration: 2 Weeks

2. Dependency: A.1

A.4: Develop high-level Product Requirement Narrative Stakeholder review, and product backlog grooming / Epic distribution strategy / Sprint plan for 12 weeks 

1.  Duration: 4 Weeks

2. Dependency: A.2

A.5: Develop Manual Audit SOP, Audit Cadence, and data analysis strategy 

1. • 1. Duration : 3 weeks

     2. Dependency: A.2

A.6: Establish a Progress Reporting mechanism such as routine email updates via an email distribution list, business documents, and stakeholder presentations based on pre-approved / standard templates 

1. • 4. Duration : 3 weeks

     5. Dependency: A.2

A.7: Finalize resource allocation and capacity management strategy to deliver P0 / MVP / V1 product and sprint cadence aligned with delivery schedule 

1. • 6. Duration : 3 weeks

     7. Dependency: A.2

B: Develop AI/ML Model

B.1 Select  State of The Art (SoTA)  AI/ML Algorithm(s) / Ensemble Model 

1. • 7. 1. Duration: 2 weeks

        2. Dependencies: A.1

B.2 Establish Input Signals, Source Data channels, and Data Sourcing Strategy

1. • 7. 3. Duration: 2 weeks

        4. Dependencies: A.1

B.3 Build Data Extract-Load-Transform [ETL] data pipeline for data collection, curation, annotation, preprocessing, and augmentation, develop sampling strategy  and ML model data store 

1. • 7. 5. Duration: 4 weeks

        6. Dependencies: B.2

B.4 Establish baseline ML quality metrics in terms of Precision, Recall, and Confusion Metrics

1. • 7. 7. Duration: 2 weeks

        8. Dependencies: B.3

B.5 Implement data and model version control, automated model testing, and model monitoring framework

1. • 7. 9. Duration: 3 weeks

        10. Dependencies: C.2

B.6 Train and Test ML model output, validate ML output via Human-in-the-loop audit, establish ML model monitoring, re-training, and auto enforcement strategy 

1. • 7. 11. Duration: 4weeks

        12. Dependencies: B.3

B.6 Optimize ML model performance through feature engineering and hyperparameter tuning

1. • 7. 13. Duration: 2 weeks

        14. Dependencies: B.5

B.7 End-to-end validation in shadow/proxy mode to establish production baseline and meet non-functional requirements [scalability, performance, security, and response-time requirements]

1. • 7. 15. Duration: 4 weeks

        16. Dependencies: B.5

B.8 Establish infrastructure monitoring and model capacity management procedures

1. • 7. 17. Duration: 4weeks

        18. Dependencies: B.6

B.9 Develop MLOps (CI/CD) operating guidance to reduce model development to deployment time and operational infrastructure cost

1. • 7. 19. Duration: 4 weeks

        20. Dependencies: B.8

B.10 Establish weekly ML model audit process to evaluate false positives  [FPs] and False Negative [FNs] and develop a feedback loop based on Audit per Week [APW] capacity

1. • 7. 21. Duration: 2 weeks

        22. Dependencies: B.9

 C: Conduct User Testing and implementation  Framework

C.1 Conduct User Testing / A/B Testing / False Positive validation

1. • 7. 23. Duration: 3 weeks

        24. Dependencies: B

C.2 Ehance, Modify ML model - Human Audit sampling strategy

1. • 7. 25. Duration: 2 weeks

        26. Dependencies: C.2

C.3 Establish Auto and Manual Enforcement  / Model outcome implementation workflow, policy updates, and stakeholder communications/reason codes/error reporting mechanism 

1. • 7. 27. Duration: 4 weeks

        28. Dependencies: C.2

C.4 Develop a reporting Key Performance Indicator (KPI) dashboard, progress monitoring metrics

1. • 7. 29. Duration: 3 weeks

        30. Dependencies: C.3

C.5 Automate routine tasks and workflows, reduce manual efforts and human errors 

1. • 7. 31. Duration:  3 weeks

        32. Dependencies: C.3

C.6 Product Documentation, Training, and system implementation workflows

1. • 7. 33. Duration:  3 weeks

        34. Dependencies: C.3

D: Integrate User Feedback and develop ML model integration strategy

D.1 Integrate User Feedback, establish internal and external request submission workflow 

1. Duration: 2 weeks

2. Dependencies: B, C

D.2 Establish Service Level Agreements to address customer-facing issues/escalations/remediation  procedures 

3. Duration: 2 weeks

4. Dependencies: B, C

D.3 Develop API-based model integration to support 3rd party integration efforts

5. Duration: 6 weeks

6. Dependencies: B, C

D.4 Document out-of-scope use cases with supporting rational

7. Duration: 4 weeks

8. Dependencies: B, C

D.5 Publish resource allocation, bandwidth utilization metrics/dashboard 

9. Duration: 3 weeks

10. Dependencies: B, C

D.6 Explore cross-team collaboration opportunities 

11. Duration: X weeks

12. Dependencies: B, C

D.7 Benchmark Product Performance against best-in-class models/industry standards 

13. Duration: 3 weeks

14. Dependencies: B, C

E: Launch ReviewShield

E.1: Launch ReviewShield

1. Duration : 3 Weeks 

2. Dependencies: B, C

E.1: Launch ReviewShield

3. Duration : 3 Weeks 

4. Dependencies: B, C

E.1: Launch ReviewShield

5. Duration : 3 Weeks 

6. Dependencies: B, C

E.1: Launch ReviewShield

7. Duration : 3 Weeks 

8. Dependencies: B, C

About Critical Path Method (CPM) and Activity on Node (AON) Diagram

Critical Path Method (CPM)

Definition: CPM is a project management technique used to identify the longest sequence of dependent tasks (the critical path) that determines the shortest time in which a project can be completed. By focusing on these critical tasks, product managers can effectively allocate resources and manage time to ensure project deadlines are met.

Activity on Node (AON) Diagram

In an AON diagram, each node (or circle) represents an activity, and the arrows between them represent dependencies. This format allows for a clear visualization of task sequences and dependencies.

Business Context

1. Resource Allocation: CPM allows project managers to focus on critical tasks, ensuring that resources are allocated effectively to avoid delays.

2. Risk Management: By identifying the critical path, teams can monitor these tasks closely to mitigate risks that could lead to project overruns.

3. Timeline Planning: CPM provides a clear timeline for project completion, helping stakeholders understand project milestones and deadlines.

4. Efficiency: By prioritizing critical tasks, teams can improve efficiency and ensure that key objectives are met without unnecessary delays.