Lifecycle management
The Lifecycle Mgmt. group in the Agentic Transformation Platform (ATP) sidebar holds 6 assessment pages. Each page is run by the same agent, Marty (lifecycle management agent). Use this page to choose the right assessment and prepare the evidence it asks for.
Before you start
- Every page in this group uses the same assessment workspace. To learn how to upload evidence, run an analysis and ask follow-up questions, read Run an assessment.
- Upload metadata and exports only. Each page's Instructions panel says what not to upload.
Open a page in this group
- In ATP, open the menu at the left of the navigation bar.
- Expand Lifecycle Mgmt..
- Select the page you need.
When a page from this group is open, the navigation bar shows the group's pages as tabs, so you can move between them. Pages that don't fit are under More.
Pages in this group
| Page | What it covers |
|---|---|
| Change Management | IT change management and approval processes. |
| Application Onboarding | Application onboarding and integration workflows. |
| Artifact Repository | Artifact storage and repository management. |
| Source Code Mgmt & CI/CD | Source control and continuous integration/deployment. |
| Automated Testing Frameworks | Automated testing tools and frameworks. |
| SDLC | Software development lifecycle management. |
Change management
Select Change Management to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Marty. The sidebar describes it as: IT change management and approval processes.
The Instructions panel is titled How to Generate Your Change Management Optimization Report. It says:
To generate your change management optimization report, Marty only needs metadata (change records and workflow patterns) — not business data. Upload raw exports from your change management platform, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Change Request Records: Change requests, change categories, priorities, impact classifications, and change history data.
- Approval Workflows: Approval chains, CAB schedules, escalation policies, change windows, and change authority levels.
- PIR Assessments: Post-implementation review records, change success/failure outcomes, rollback events, and lessons-learned data.
- CAB Performance: CAB meeting records, approval cycle times, change backlog data, emergency change volumes, and governance metrics.
- Performance Analytics: Change velocity metrics, change adoption rates, organizational change analytics, and CI/CD deployment frequency data.
The panel also shows this note:
Important: Do not upload infrastructure configurations or sensitive system data — Marty analyzes change process patterns and workflows, not infrastructure configurations.
Application onboarding
Select Application Onboarding to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Marty. The sidebar describes it as: Application onboarding and integration workflows.
The Instructions panel is titled How to Generate Your Application Onboarding Report. It says:
To generate your application onboarding report, Marty only needs metadata (onboarding schedules and provisioning patterns) — not business data. Upload raw exports from your onboarding or service management tools, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Onboarding Requests: Application onboarding intakes, requirements documentation, intake form data, and business justification records.
- Provisioning Workflows: Infrastructure provisioning templates, environment setup records, integration configuration data, and automation scripts.
- Onboarding Timelines: Milestone schedules, phase completion records, dependency tracking data, and onboarding SLA performance.
- Validation & Testing: Acceptance testing records, functional validation checklists, integration test results, and go-live sign-off data.
- Runbooks & Documentation: Onboarding runbooks, operational handoff documentation, support transition records, and knowledge transfer artifacts.
The panel also shows this note:
Important: Do not upload infrastructure configurations or sensitive system data — Marty analyzes onboarding workflows and provisioning patterns, not infrastructure configurations.
Artifact repository
Select Artifact Repository to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Marty. The sidebar describes it as: Artifact storage and repository management.
The Instructions panel is titled How to Generate Your Artifact Repository Optimization Report. It says:
To generate your artifact repository optimization report, Marty only needs metadata (repository structure and usage patterns) — not business data. Upload raw exports from your artifact management tools, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Repository Structure: Repository strategy, artifact types, versioning schemes, naming conventions, and repository topology data.
- Storage Metrics: Storage consumption data, artifact size distributions, growth rate trends, and repository capacity records.
- Access Policies: Access control configurations, permission models, team-level access records, and authentication integration data.
- Security & Compliance: Security scan results, vulnerability findings, compliance audit records, and license compliance data.
- Lifecycle Policies: Retention policy configurations, cleanup rule definitions, artifact promotion workflows, and archival process records.
The panel also shows this note:
Important: Do not upload infrastructure configurations or sensitive system data — Marty analyzes repository structures and usage patterns, not infrastructure configurations.
Source code management and CI/CD
Select Source Code Mgmt & CI/CD to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Marty. The sidebar describes it as: Source control and continuous integration/deployment.
The Instructions panel is titled How to Generate Your Source Code Management CI/CD Optimization Report. It says:
To generate your source code management and CI/CD optimization report, Marty only needs metadata (pipeline configurations and repository patterns) — not business data. Upload raw exports from your source control and CI/CD tools, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Repository Structure: Branch strategies, commit patterns, contribution frequency, code review metrics, and merge template configurations.
- CI/CD Pipeline Config: Pipeline configurations, build stage definitions, test coverage integrations, deployment frequency data, and pipeline health metrics.
- Build Performance: Build success/failure rates, build duration trends, flaky test records, and pipeline bottleneck data.
- Release Management: Release records, rollback procedures, deployment environment configurations, and release workflow documentation.
- Release Automation: Deployment automation scripts, environment promotion rules, gating criteria, and release cadence data.
The panel also shows this note:
Important: Do not upload infrastructure configurations or sensitive system data — Marty analyzes pipeline patterns and repository structures, not infrastructure configurations.
Automated testing frameworks
Select Automated Testing Frameworks to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Marty. The sidebar describes it as: Automated testing tools and frameworks.
The Instructions panel is titled How to Generate Your Automated Testing Optimization Report. It says:
To generate your automated testing optimization report, Marty only needs metadata (test configurations and coverage patterns) — not business data. Upload raw exports from your testing frameworks, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Test Suite Structure: Test case organization, test type categorization, framework configuration data, and test ownership records.
- Coverage Metrics: Code coverage reports, coverage by module, gap analysis outputs, and untested area summaries.
- Test Execution: Execution history records, pass/fail rate trends, flaky test data, test duration metrics, and run frequency data.
- Performance Testing: Performance test results, load testing outputs, scalability benchmark data, and stress test findings.
- Test Maintenance: Test debt records, maintenance cost data, obsolete test inventories, and framework upgrade history.
The panel also shows this note:
Important: Do not upload customer data, PII, or sensitive records — Marty analyzes test configurations and coverage patterns, not customer content.
SDLC
Select SDLC to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Marty. The sidebar describes it as: Software development lifecycle management.
The Instructions panel is titled How to Generate Your SDLC Report. It says:
To generate your SDLC report, Marty only needs metadata (process workflows and delivery metrics) — not business data. Upload raw exports from your development management tools, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Development Process Data: Sprint metrics, velocity data, sprint planning outputs, retrospective action records, and change frequency data.
- Delivery Metrics: Lead time, cycle time, deployment frequency, change failure rates, and mean-time-to-restore data.
- Quality Frameworks: Code quality metrics, technical debt analysis, code review outcome data, and quality standard definitions.
- Team Collaboration: Team structure data, collaboration patterns, cross-team handoff records, and dependency tracking data.
- Process Enablement: Toolchain configurations, workflow automation records, SDLC governance policies, and process maturity assessments.
The panel also shows this note:
Important: Do not upload infrastructure configurations or sensitive system data — Marty analyzes SDLC process patterns and delivery metrics, not infrastructure configurations.