What should I know about the Context feature?
Last Updated: | Applicable Viz Versions: All
Overview
The Context feature helps you document and track issues that impact your work items in real time. Each context annotation consists of three parts:
- Category (what type of issue)
- Reason code (specific cause)
- Description (your detailed notes)
Using Context in your Workflow
Critical issues raised in stand-ups and team updates can finally captured where they belong—with your work items. Use Context to:
- Capture blocking issues and impacts in real time as they happen
- Identify systemic issues that need broader attention vs. one-off problems
- Provide stakeholders at all levels with full visibility into delivery impacts
Accessing Context
Access the Context side panel by clicking on a work item in either:
- The Delivery Forecast widget (portfolio-level)
- The Flow Item Analyzer (product-level)
Categories and Reason Codes
Categories
- Aging: Work incomplete for longer than expected/desired
- At Risk: Work in danger of missing deadlines or quality standards
- Blocked: Work waiting on prerequisites, approvals, or resources before proceeding
- Canceled: Work terminated before expected completion
- Deferred: Work planned to start at a future date
- Unplanned: Emergent work that demands immediate attention
Reason Codes
- Resource Related
- Budget Constraints: Financial limitations that impact work delivery
- Dependencies – External: Requirements from other external resources
- Dependencies – Internal: Requirements from other internal resources
- Team Issues: Problems with development team dynamics or skill sets
- Strategic Factors
- Key Customer/Lead: Changes in customer relationships that impact work value
- Strategic/Business Changes: Changes in company direction/priorities that affect the work
- User Feedback: Direct input from users about specific features or requirements
- Planning & Execution
- Poor Planning: Initial misestimation of effort, resources, or complexity
- Scope Creep: Gradual expansion of project requirements beyond the original agreement
- State Hygiene: Work incorrectly tracked in workflow states
- Technical Challenges: Engineering or architectural complexities impacting work delivery
- External Factors
- Market Changes: External factors that shift priorities
- Regulatory and Compliance Issue: New regulations/requirements affecting work feasibility/approach
- Technological Obsolescence: Rapid advancements in technology causing work to be obsolete
- Lack of Stakeholder Support: Insufficient engagement/backing from internal decision-makers