All games have deadlines. Publishers have to schedule a game's release while juggling all the other games they're releasing, deciding on release months that will be more beneficial, when their competition is releasing, and schedule all of the non-development side of videogames (ie. marketing, advertising, ramp-up on social media and game websites, localization of text and voicing, packaging and manufacturing, global distribution, console certification, digital retail setup), and then they have to do the same thing on a smaller scale with DLC.
Because of all of this scheduling and the money sunk into these things, it's important that developers stick as closely to the agreed-upon schedules as possible. Yes, I said "agreed-upon." Publishers can't just dictate the schedule. The developer has to agree that it can meet that timeframe and schedule its own team as needed.
Why, then, do some games get delayed and some are "rushed"?
Delays happen all the time for a variety of reasons. Usually, the time can be made up by working overtime (or "crunch"). You really don't want to be the department responsible for the publisher having to waste a million dollars, or the time and hard work of dozens of people. But sometimes, if a studio absolutely can't meet the schedule as agreed upon, they can make a case to the publisher for an extension. It is not at all an easy decision to make, and no company makes it lightly. It involves many meetings where the publisher tries to convince the developer to either cut back on unneeded features or game scope, and the studio tries to convince the publisher that what they've got will be worth the extra time.
The publisher has already had regular updates from the studio, and at certain times, has already played the game, so hopefully the publisher already knows what kind of game the developer is making. There may also be some legal implications to delaying release, depending on what kind of delay it is. I knew this kind of meeting as the "go/no-go" meeting, where the developer and publisher decide the game is a go as scheduled or a no-go with some kind of delay.
That's delays, but what about rushing? Well, think about the last major project you worked on, like a term paper or a science fair or an important report or something like that. Each one had some kind of deadline, and no matter how well you managed your time, there was always some last minute things you just had to do to polish it up. It could be extra line-runs of a play, or fixing the formatting of your charts, or double-checking the accuracy of your data, or spellchecking.
Now, imagine that your instructor, professor, boss, director or whoever didn't care for the work you did, but instead of calling out specific faults or offering constructive criticism, he (or she) merely said "it looked like it was rushed" and gave you a low grade. Any attempt to get more specific answers resulted in variations on the "it was rushed" comment. That's what it's like in videogames.
There are absolutely instances where games were likely rushed (ie. not given nearly enough time to make the kind of game the publisher wanted, or the developer not changing the scope of their game when that go/no-go meeting came around). It can be argued that Dragon Age was a "rushed" game, as it wasn't given as much time as other BioWare games got. In fact, some people have pointed out that DA2 got a ridiculously short development cycle. Because of that short cycle, and the quality and scope of the game as compared to its immediate predecessor, "the game was rushed" could be a legitimate observation.
This is not the case with games that have average development cycles, such as ME2 or ME3. Whatever else you can say about those games, I don't think you could legitimately call them "rushed." They had about the same amount of time as previous games, the team was largely the same, and ME3 was the last game of a trilogy featuring the same protagonist as the first two.
TL;DR - "Rushed" is a very specific criticism that cannot be applied to just any game as a generic term for "I didn't like some things about it" or "it didn't meet my expectation". BioWare and EA both have to agree on the game's schedule. All giant projects go through massive last-minute freaking out. A change in schedule for a company dealing with as many things as EA does, can mean a lot of shuffling of resources, money, and personnel, so it's not an easy decision. I like pie.