Using a gross simplification, the main difference is size.
You need to be aware of the definitions for project, program, and portfolio. From the PMBOK:
Project: A project is a temporary endeavor undertaken to create a unique product, service, or result.
Program: A program is a group of related projects, subsidiary programs, and
program activities ...
Due to the nature of most Agile development, the details of a given piece of functionality can change over time (in fact, if this isn't true, you aren't very agile). Therefor, what is on a given card in your backlog is just a description of that point in time, making it ill-suited for long-term documentation. Further, documenting too much in cards can lead ...
I have successfully kept the "issues" in Jira and then used Confluence for the type of documents that you are mentioning. My recommendation would be to keep your documents in a more appropriate system, for instance Confluence.
Sure any kind of documentation system would do. Both Jira and Confluence are from the same provider, Atlassian.
Consider representing Risks (not the same as Opportunities) in a dashboard.
Start with familiarizing with the four states requiring action.
See the sample dashboard, presented as an example for a Risk (one of the four states in a project), and refer to the risk matrix graphic.
Action vs. Action Item - What's the difference?
What is an ...
A research spike is intended to reduce the cone of uncertainty for future work. It is not intended to deliver shippable increments of anything. Treating the output of a spike as anything other than input to story planning/refinement is a Scrum implementation smell.
Time-Box Your Spikes
As an empirical control framework, Scrum is heavily reliant on ...
There are a few different ways to approach this kind of problem. Since this question is tagged Scrum, I'll focus on Scrum as it's defined in the Scrum Guide, but with other lean and agile approaches.
Scrum already accounts for research - it's called "Product Backlog Refinement". The Scrum Guide recommends that the Development Team allocate approximately 10% ...
The purpose of the limited timebox is to force the team to break down larger items into smaller ones. 2 weeks is a long time for research. I usually look for research tasks to be measured in hours, not days, let alone weeks. You may need to consider exactly what it is you are researching. Some common ways to approach this include:
In pure research, what ...