SQL Server's Maintenance plan wizard is unusuable in a serious environment because it doesn't handle new databases or transaction log backups nicely.

On most production SQL servers, some databases have truncate log on checkpoint, turned on, others have them turned off. A complete backup procedure needs back up transaction logs hourly or more frequently. So it needs to look at every database, identify the log settings, and decide whether or not to back up the log.

For nightly backups, the procedure needs to backup the logs first, then do a full database backup.

And of course, the backup procedure needs to handle rotation of backup media (file or tape), ensuring that N days of backups are on-hand, but everything gets copied to tape automatically.

And it needs to log errors and send alerts when anything in the whole preocess goes amiss.

Nedless to say, I write my own scripts.