Both. And it's a sliding scale in real life - you might be completely Kanban, or completely Scrum, or somewhere between, where you're doing some Scrum ceremonies and processes but skipping the ones that don't help you .
I usually look at the processes the team want to do, and the main question is "how do you want to plan your work?"
If you want to be planning, estimating and agreeing fixed amounts of work to be delivered in specific time periods, Scrum. If you simply want to let things flow in ad-hoc and let your leads prioritise and the developers take things off a to-do list whenever they're ready, Kanban. Most people do something in-between.
If you try one and it doesn't work, it does not matter. You can swap to the other. Better, you can do both at the same time. There are plenty of places I know of that are doing Scrum pretty much full on. And while they're running Scrum "properly", they're using Kanban boards to visualise, focus and supplement their Scrum process.
Recommended Learning For You
Level up your skills with Atlassian learning
Visualizing Work Across Teams with Plans in Jira Software
Learn how to use Plans to accurately map your team’s work and make better recommendations.
The Beginner's Guide to Agile in Jira
This course has everything you need to get started with agile and Jira Software.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.