I'm unfortunately ill and busy at work (Brisbane flu cases up 50%), which has combined into an unpleasant malaise meaning I skipped a post yesterday. But that's the past, right? Let's pretend that never happened. Here is a good link for your edification. It's Charles Stross talking about writing a novel using Scrivener.
People generally love Scrivener. Although I own a copy and use it for structuring short fiction, I don't particularly love it. It's basically a bag of tools and notebooks, and you can do anything you want. I prefer some more structure and less options, but that's just a personal preference. I tried to structure all my characters for a novel manuscript in a meaningful way (I'm a programmer, so I love meta data), but Scrivener just didn't do it the way I wanted. Yes, I'm sure there's a secret way that approximates my needs, but in general, Scrivener chooses to give you the tools to manage stuff however you like.
Also, it's a terrible Word Processor (note: it's not a Word Processor, so that's hardly Scrivener's fault). I always paste the entire contents into Word when I've finished and do my final formatting.
Stross's article introduces the product thus:
Some of you probably know about Scrivener, the writer's tool from Literature and Latte. (If you don't, the short explanation is that it isn't a word processor, it's an integrated development environment for books. It's cross-platform (although initially developed for Mac OS X —versions for Windows and Linux are available, and it's being ported to iOS and Android), modestly priced, and has more features than you can wave a bundle of sticks at, mostly oriented around managing, tagging, editing, and reorganizing collections of information including rich text files.)
His review of his own novel writing experience is thorough, listing pros and cons as it relates to his workflow, and worth reading if you are in the market for writing software or even if you already own Scrivener.