Application Deployment vs Task Sequence for MS Office 2013

Afternoon All,

I'm in the process of Deploying MS Office 2013 onto our fleet of machines using SCCM 2012

1. Our current fleet has MS Office 2010 installed
2. I have created a custom .MSP file for my MS Office 2013

I'm currently just deploying MS Office 2013 by just selecting device collections and it seems to work (besides removing sharepoint workspace 2010)

I have been trying to streamline the process to clean up MS Office 2010 - I have been told to create a custom task sequence and set it as below

1. Use Office 2010 Application package set as uninstall

2. Use Office 2013 Application package set to install

They say this makes for a more clean process as it's two individual tasks being completed.

Just want to see how others went from MS Office 2010 to MS Office 2013 using SCCM 2012