Digital Dilemmas
A role that is responsible for driving the activities of a particular phase of the software development lifecycle.
Active role in a phase
A requirement that describes a specific function or feature that the software must perform.
Functional or Functional Requirement
A high-level view of all issues in a JIRA project, typically showing key attributes such as status and assignee.
JIRA - "Summary View"
App feature requests that come from legal or regulatory requirements.
Legal driven app feature requests
A set of documents or artifacts that capture the requirements for a software project, typically including user stories, use cases, and process flow diagrams.
Requirements Documentation
Business Analysis Body of Knowledge, a guidebook and framework for the practice of business analysis.
BABOK
The person or team responsible for a particular function or feature of a software system.
Functional Owner
A relationship between a JIRA issue and an Epic, which is a larger grouping of related issues.
JIRA - "Ticket/Issue is in the Epic"
App feature requests that come from a specific need or problem that the app is trying to solve.
Need driven app feature requests
The process of gathering and refining requirements for a software project, typically involving interviews, surveys, and other techniques to understand the needs of stakeholders.
Requirements Elicitation
A tangible product or outcome of a particular phase or activity in the software development lifecycle.
Deliverable
Gartner is a research and advisory firm that provides insights and analysis on a variety of topics, including technology trends.
Gartner - creators of the hype cycle
A unit of work or task tracked in JIRA.
JIRA-Issue
A requirement that describes how the software must perform, rather than what it must do. Examples include performance, security, and scalability requirements.
Non-Functional Requirement
Subject Matter Expert, someone with specialized knowledge or expertise in a particular area.
SME
The person or group of people who will use the software system once it is deployed.
End User
App feature requests that come from a source of inspiration such as a similar app or a competitor's product.
Inspiration driven app feature requests
A classification of JIRA issues, such as "Bug," "Task," or "Epic."
JIRA-Issue Type
A role that is not responsible for driving the activities of a particular phase of the software development lifecycle, but may be consulted or provide input.
Passive role in a phase
A unit of ESTIMATION used in Agile project management to estimate the RELATIVE COMPLEXITY of implementing a user story.
Story Points
End of Week, typically used as a deadline or milestone in a project plan.
EOW
A detailed view of a single issue in JIRA, showing all relevant information and comments.
JIRA - "Issue Detail View"
A visual representation of JIRA issues grouped by a particular attribute, such as assignee or status.
JIRA-Swimlane
A statement of what the system must do, describing the expected behavior or functionality of the system.
Requirement
A model developed by Gartner that tracks the lifecycle of a new technology, from initial hype and inflated expectations to eventual disillusionment and maturity.
Technology Hype Cycle