Back
Dev

Office 365 Developer Podcast: Episode 031 on Application Lifecycle Management with Vesa Juvonen

Share on Facebook Share on Twitter Share on Linkedin Share via OneNote Share via Email Print

In episode 31, Jeremy Thake speaks to Vesa Juvonen about Application Lifecycle Management (ALM) with Office 365 Development. Vesa shares what they have been doing with the Office 365 Patterns & Practices initiative with regard to ALM as well as what his core customers that he works with are doing. He also talks about different options for dev/test/prod environments for Office 365 too.

Download the podcast.

Weekly updates

Show notes

Got questions or comments about the show? Join the O365 Dev Podcast on the Office 365 Technical Network.

The podcast RSS has been submitted to all the stores and marketplaces but takes time, please add directly with the RSS http://feeds.feedburner.com/Office365DeveloperPodcast.

About Vesa Juvonen

Vesa Juvonen is a senior program manager with the SharePoint Customer Experience team in product group. Prior to being a member of the CXP team, Vesa was a principal consultant with Microsoft Services for eight years before moving to product group. Vesa was also SharePoint MCM (Microsoft Certified Master) instructor for the life cycle of the program and is considered an industry expert on the use of the app model and more specifically on the transformation from farm solutions to the app model.

Vesa leads the team which created the Office 365 Developer PnP (Pattern and Practice) project (formerly known as OfficeAMS) to help customers transition into the new app model. Vesa is also a frequent speaker at SharePoint conference and events.

About the host

An image of Jeremy Thake, a newly appointed tTechnical pProduct mManager at Microsoft responsible for the Visual Studio Developer story for Office 365 developmentJeremy is a newly appointed technical product manager at Microsoft responsible for the Visual Studio Developer story for Office 365 development. Previously he worked at AvePoint Inc., a large ISV, as the chief architect shipping two apps to the Office Store. He has been heavily involved in the SharePoint community since 2006 and was awarded the SharePoint MVP award four years in a row before retiring the title to move to Microsoft.

You can find Jeremy blogging at www.jeremythake.com and tweeting at @jthake.

Useful links

Top

Join the conversation

2 comments
  1. Lots of good info, but the suggestion to use multiple tenants, did not address the problem that each tenant will be updated independently on different schedules and therefore may have different features and code bases. How can use this approach when the prod tenant may have features/bug fixes that don’t exist in the dev or test tenants?

Comments are closed.