How to deal with very large transaction logs in SQL Server
I would take the first transaction log backup by hand (not as a scheduled task) and during hours when a performance hit will be acceptable to your users.

Then take a second immediately so that the working area of the log file moves back to the start of the file.  

Then shrink the log file.

Then start your scheduled transaction log backups.