316 lines
13 KiB
Markdown
316 lines
13 KiB
Markdown
# Context Persistence Persona Integration Checklist
|
|
|
|
## Overview
|
|
**Checklist Type:** Context Persistence Integration Validation
|
|
**Target:** All BMAD Personas
|
|
**Purpose:** Ensure proper integration of context persistence methodology across all personas
|
|
**Validation Level:** Comprehensive
|
|
|
|
## Universal Context Integration Validation
|
|
|
|
### Context Awareness Validation
|
|
- [ ] **Context Type Understanding**
|
|
- [ ] Persona demonstrates understanding of session context
|
|
- [ ] Persona demonstrates understanding of project context
|
|
- [ ] Persona demonstrates understanding of user context
|
|
- [ ] Persona demonstrates understanding of organizational context
|
|
|
|
- [ ] **Context Lifecycle Knowledge**
|
|
- [ ] Persona knows when to create context
|
|
- [ ] Persona knows how to retrieve relevant context
|
|
- [ ] Persona knows how to apply context to current work
|
|
- [ ] Persona knows how to update existing context
|
|
|
|
- [ ] **Context Quality Standards**
|
|
- [ ] Persona creates relevant context for future use
|
|
- [ ] Persona ensures context accuracy and completeness
|
|
- [ ] Persona structures context for easy retrieval
|
|
- [ ] Persona validates context quality before persistence
|
|
|
|
### Context Application Validation
|
|
- [ ] **Context Retrieval Process**
|
|
- [ ] Persona identifies what context is needed for current task
|
|
- [ ] Persona effectively queries available context sources
|
|
- [ ] Persona validates context relevance and accuracy
|
|
- [ ] Persona integrates context seamlessly into current work
|
|
|
|
- [ ] **Context Creation Process**
|
|
- [ ] Persona identifies valuable context for future sessions
|
|
- [ ] Persona documents decisions and rationale clearly
|
|
- [ ] Persona structures context for easy understanding
|
|
- [ ] Persona follows context quality standards
|
|
|
|
- [ ] **Context Handoff Process**
|
|
- [ ] Persona understands what context other personas need
|
|
- [ ] Persona prepares context effectively for handoffs
|
|
- [ ] Persona validates context completeness for handoffs
|
|
- [ ] Persona documents handoff rationale and expectations
|
|
|
|
## Persona-Specific Integration Validation
|
|
|
|
### Product Owner Context Integration
|
|
- [ ] **Requirements Context Management**
|
|
- [ ] Maintains comprehensive requirements history across sessions
|
|
- [ ] Documents stakeholder requirements with full context
|
|
- [ ] Creates traceability between requirements and business objectives
|
|
- [ ] References previous requirements decisions when creating new stories
|
|
|
|
- [ ] **Stakeholder Context Building**
|
|
- [ ] Builds stakeholder preference profiles over time
|
|
- [ ] Documents communication patterns and preferences
|
|
- [ ] Tracks decision authority and approval workflows
|
|
- [ ] Adapts communication based on stakeholder history
|
|
|
|
- [ ] **Product Vision Consistency**
|
|
- [ ] Maintains product vision context across sessions
|
|
- [ ] Ensures requirements alignment with product strategy
|
|
- [ ] Documents market insights and competitive analysis
|
|
- [ ] Creates strategic context for future decision-making
|
|
|
|
- [ ] **Context Handoff to Architect**
|
|
- [ ] Provides complete requirements specifications
|
|
- [ ] Documents business constraints and priorities
|
|
- [ ] Shares stakeholder preferences and requirements
|
|
- [ ] Ensures context completeness for technical decisions
|
|
|
|
### Architect Context Integration
|
|
- [ ] **Technical Decision Documentation**
|
|
- [ ] Creates architectural decision records (ADRs) with full context
|
|
- [ ] Documents technology choices and trade-offs
|
|
- [ ] Maintains decision rationale for future reference
|
|
- [ ] References previous decisions to ensure consistency
|
|
|
|
- [ ] **System Design Evolution**
|
|
- [ ] Tracks system architecture evolution over time
|
|
- [ ] Documents component relationships and dependencies
|
|
- [ ] Manages integration pattern context effectively
|
|
- [ ] Creates scalability and performance context
|
|
|
|
- [ ] **Technology Standards Application**
|
|
- [ ] Applies organizational technology standards consistently
|
|
- [ ] Documents compliance and security requirements
|
|
- [ ] Manages technology context across projects
|
|
- [ ] Creates reusable technology pattern context
|
|
|
|
- [ ] **Context Handoff to UX/UI and Developer**
|
|
- [ ] Provides technical constraints and requirements
|
|
- [ ] Documents system architecture and integration needs
|
|
- [ ] Shares technology standards and compliance requirements
|
|
- [ ] Ensures context supports implementation decisions
|
|
|
|
### V0 UX/UI Architect Context Integration
|
|
- [ ] **Design System Maintenance**
|
|
- [ ] Maintains component library context across sessions
|
|
- [ ] Documents design token evolution and rationale
|
|
- [ ] Creates interaction pattern context for consistency
|
|
- [ ] Manages accessibility standard context effectively
|
|
|
|
- [ ] **User Experience Insight Application**
|
|
- [ ] Builds user research insight libraries over time
|
|
- [ ] Documents usability feedback with context
|
|
- [ ] Creates user journey context for design decisions
|
|
- [ ] Manages persona definition context effectively
|
|
|
|
- [ ] **Visual Consistency Management**
|
|
- [ ] Maintains brand guideline context across projects
|
|
- [ ] Documents visual hierarchy decisions with rationale
|
|
- [ ] Creates color and typography context for consistency
|
|
- [ ] Manages iconography standard context effectively
|
|
|
|
- [ ] **Context Handoff to Developer**
|
|
- [ ] Provides complete design specifications with context
|
|
- [ ] Documents component requirements and usage guidelines
|
|
- [ ] Shares interaction patterns and accessibility requirements
|
|
- [ ] Ensures context supports accurate implementation
|
|
|
|
### Developer Context Integration
|
|
- [ ] **Codebase Context Management**
|
|
- [ ] Documents code architecture decisions with rationale
|
|
- [ ] Creates implementation pattern context for consistency
|
|
- [ ] Manages coding standard context across projects
|
|
- [ ] Tracks technical debt context and resolution plans
|
|
|
|
- [ ] **Implementation Progress Tracking**
|
|
- [ ] Maintains work-in-progress context across sessions
|
|
- [ ] Documents testing status and strategies with context
|
|
- [ ] Creates deployment state context for continuity
|
|
- [ ] Manages known issues and resolution context
|
|
|
|
- [ ] **Quality Standards Application**
|
|
- [ ] Applies code quality standard context consistently
|
|
- [ ] Documents testing methodology context for reuse
|
|
- [ ] Creates performance benchmark context for validation
|
|
- [ ] Manages security practice context across implementations
|
|
|
|
- [ ] **Context Handoff to Scrum Master**
|
|
- [ ] Provides implementation progress and status context
|
|
- [ ] Documents technical challenges and impediments
|
|
- [ ] Shares delivery estimates with supporting context
|
|
- [ ] Ensures context supports project management decisions
|
|
|
|
### Scrum Master Context Integration
|
|
- [ ] **Team Dynamics Tracking**
|
|
- [ ] Builds team member strength profiles over time
|
|
- [ ] Documents collaboration pattern context for optimization
|
|
- [ ] Creates communication preference context for effectiveness
|
|
- [ ] Manages conflict resolution history and patterns
|
|
|
|
- [ ] **Process Improvement Documentation**
|
|
- [ ] Maintains agile practice effectiveness context
|
|
- [ ] Documents ceremony improvement context and outcomes
|
|
- [ ] Creates retrospective insight context for continuous improvement
|
|
- [ ] Manages team agreement context and evolution
|
|
|
|
- [ ] **Project Progress Context**
|
|
- [ ] Tracks sprint history and velocity context for planning
|
|
- [ ] Documents impediment pattern context for prevention
|
|
- [ ] Creates delivery metrics context for improvement
|
|
- [ ] Manages stakeholder feedback context for alignment
|
|
|
|
- [ ] **Context Sharing with All Personas**
|
|
- [ ] Provides team dynamics context to support collaboration
|
|
- [ ] Shares process effectiveness context for optimization
|
|
- [ ] Documents project progress context for alignment
|
|
- [ ] Ensures context supports all personas' effectiveness
|
|
|
|
## Cross-Persona Context Validation
|
|
|
|
### Context Handoff Quality
|
|
- [ ] **Completeness Validation**
|
|
- [ ] All necessary context is included in handoffs
|
|
- [ ] Context includes sufficient detail for target persona
|
|
- [ ] Context provides clear rationale and background
|
|
- [ ] Context includes relevant constraints and requirements
|
|
|
|
- [ ] **Accuracy Validation**
|
|
- [ ] Context information is factually correct
|
|
- [ ] Context reflects current state accurately
|
|
- [ ] Context includes up-to-date information
|
|
- [ ] Context has been validated before handoff
|
|
|
|
- [ ] **Relevance Validation**
|
|
- [ ] Context is relevant to target persona's work
|
|
- [ ] Context supports target persona's decision-making
|
|
- [ ] Context aligns with target persona's responsibilities
|
|
- [ ] Context provides actionable information
|
|
|
|
### Context Continuity Validation
|
|
- [ ] **Session Continuity**
|
|
- [ ] Context enables seamless continuation across sessions
|
|
- [ ] Previous decisions and rationale are accessible
|
|
- [ ] Work progress is clearly documented and retrievable
|
|
- [ ] Session state can be effectively restored
|
|
|
|
- [ ] **Project Continuity**
|
|
- [ ] Project-level context is maintained across all personas
|
|
- [ ] Project evolution is documented and accessible
|
|
- [ ] Project decisions are traceable and consistent
|
|
- [ ] Project knowledge is preserved and enhanced
|
|
|
|
- [ ] **User Continuity**
|
|
- [ ] User preferences are maintained and applied
|
|
- [ ] User feedback history is preserved and referenced
|
|
- [ ] User working patterns are recognized and supported
|
|
- [ ] User experience is consistent across sessions
|
|
|
|
## Technical Integration Validation
|
|
|
|
### Context Storage and Retrieval
|
|
- [ ] **Storage Validation**
|
|
- [ ] Context is properly stored according to persistence strategy
|
|
- [ ] Context storage follows security and privacy requirements
|
|
- [ ] Context is organized for efficient retrieval
|
|
- [ ] Context storage meets performance requirements
|
|
|
|
- [ ] **Retrieval Validation**
|
|
- [ ] Context can be efficiently located and retrieved
|
|
- [ ] Context retrieval meets performance targets
|
|
- [ ] Context is accurately restored from storage
|
|
- [ ] Context retrieval supports workflow continuity
|
|
|
|
### Context Quality Assurance
|
|
- [ ] **Quality Metrics**
|
|
- [ ] Context creation meets quality standards
|
|
- [ ] Context utilization rates meet targets
|
|
- [ ] Context accuracy is validated and maintained
|
|
- [ ] Context effectiveness is measured and improved
|
|
|
|
- [ ] **Quality Monitoring**
|
|
- [ ] Context quality is continuously monitored
|
|
- [ ] Context usage patterns are tracked and analyzed
|
|
- [ ] Context effectiveness is measured and reported
|
|
- [ ] Context quality issues are identified and resolved
|
|
|
|
## Training and Adoption Validation
|
|
|
|
### Training Effectiveness
|
|
- [ ] **Knowledge Validation**
|
|
- [ ] All personas demonstrate context persistence understanding
|
|
- [ ] Personas can identify relevant context for their work
|
|
- [ ] Personas understand context quality standards
|
|
- [ ] Personas know how to create and use context effectively
|
|
|
|
- [ ] **Practical Application**
|
|
- [ ] Personas effectively apply context in real scenarios
|
|
- [ ] Context creation quality meets standards
|
|
- [ ] Context handoffs are effective and complete
|
|
- [ ] Cross-session continuity is achieved
|
|
|
|
### Adoption Success
|
|
- [ ] **Usage Metrics**
|
|
- [ ] Context persistence is actively used by all personas
|
|
- [ ] Context utilization rates meet adoption targets
|
|
- [ ] Context quality scores meet standards
|
|
- [ ] User satisfaction with context persistence is high
|
|
|
|
- [ ] **Effectiveness Metrics**
|
|
- [ ] Cross-session continuity has improved
|
|
- [ ] Decision consistency has increased
|
|
- [ ] Inter-persona handoffs are more effective
|
|
- [ ] Overall persona effectiveness has improved
|
|
|
|
## Validation Scoring
|
|
|
|
### Scoring Framework
|
|
\```yaml
|
|
scoring_criteria:
|
|
excellent: "90-100% - All criteria met with high quality"
|
|
good: "80-89% - Most criteria met with acceptable quality"
|
|
acceptable: "70-79% - Basic criteria met with room for improvement"
|
|
needs_improvement: "60-69% - Significant gaps requiring attention"
|
|
inadequate: "Below 60% - Major issues requiring immediate action"
|
|
\```
|
|
|
|
### Validation Results
|
|
- **Universal Context Integration Score:** ___/100
|
|
- **Persona-Specific Integration Score:** ___/100
|
|
- **Cross-Persona Context Score:** ___/100
|
|
- **Technical Integration Score:** ___/100
|
|
- **Training and Adoption Score:** ___/100
|
|
|
|
**Overall Context Persistence Integration Score:** ___/100
|
|
|
|
## Recommendations and Action Items
|
|
|
|
### High Priority Actions
|
|
- [ ] Action Item 1: [Description and Owner]
|
|
- [ ] Action Item 2: [Description and Owner]
|
|
- [ ] Action Item 3: [Description and Owner]
|
|
|
|
### Medium Priority Actions
|
|
- [ ] Action Item 1: [Description and Owner]
|
|
- [ ] Action Item 2: [Description and Owner]
|
|
|
|
### Low Priority Actions
|
|
- [ ] Action Item 1: [Description and Owner]
|
|
- [ ] Action Item 2: [Description and Owner]
|
|
|
|
## Validation Sign-off
|
|
|
|
**Validator Name:** ________________
|
|
**Validation Date:** ________________
|
|
**Next Review Date:** ________________
|
|
**Validation Status:** ________________
|
|
|
|
This checklist ensures comprehensive validation of context persistence integration across all BMAD personas, supporting effective cross-session continuity and enhanced persona effectiveness.
|