Projects of course. They don't have to adhere to some theoretical waterfall process, and anecdotally never have. There's Kanban, and any informal process a group of cross-functional people may come up with. In fact, it's much more important to make something that works, than copying some task-list because it's said to have worked somewhere else.
Incidentally, and this is going to shake up the "Agile" world going forward, is the missing piece, the link to management (budgets and trust really!) and innovation (the creative spark!). That should be less about process, and much more about culture and learning. That has remained elusive and underappreciated.
Google Design Sprint may be the closest "process", though will still depend more on the mentioned above.
With a great team, it anyway depends on the people. Though, the experience and output also depends on who you ask. Which is why great teams may get split up, for good reasons but also bad reasons at the same time.
Though try put the most brilliant people together. They will annoy eachother into oblivion. So it's about the art of building diverse teams and mixing with what's mentioned above, because nothing thrives in a vacuum.