My background is business-first, hacker-second, and I mainly read everything on HN to pick up little places not to fuck up when architecting a software business.
The benefit of NoSQL's ease of dropping/adding schema...that's going to be one of the better ones.
The use of NoSQL is for very specific scenarios, don't make the mistake of thinking it's a good object store replacement. As a business guy this is definitely not a decision you should be making, let your team use what they're happy with, they'll get a lot more done that way.
I refer to this as the database making you eat your vegetables.
"I just want to change this tiny thing, what could possibly go wrong?"
"Nein!" shouts the database. "It will violate this and that and the other rule you told me to enforce!"
"Stupid database, always getting in my way. I'm going to install MongoDB/Redis/Couch ..."
12 months later: "Hang on ... which version of the code were these 40,000 records entered under? Does that integer field refer to the protocol 2 or protocol 3 headers? Why is there some XML in the email field?"
The benefit of NoSQL's ease of dropping/adding schema...that's going to be one of the better ones.