Last week, I had the pleasure to attend the New York SharePoint User Group. The Topic was, Application Life Cycle Management (ALM), the speaker Jeremy Thake. I must tell you, before going to this event, I didn't know much about ALM, but I can say with confidence anyone in my shoes would benefit from Jeremy's talk. It's something special when you watch a presentation from a knowledgeable individual who is also an excellent speaker.
He began with defining ALM as the continuous process of managing the life an application through governance development. He also referred to David Chapell's Document, Application Life Cycle Management as a Business Process.
He then informed the group that there are three aspects to ALM, and they are Governance, Deployment and Operations, but the key here is that Governance should happen all the way through. He also went into deep discussion about Coding, Testing and Tracking.
Jeremy's message was packaged with warning labels.
What were we warned about?
1. To package all custom code as a WSP
2. The importance of Source Control, Build Server (no test should be deployed without putting it on a build server to make sure that they are checking in everything that is required), and Team Foundation Server (TFS) (also running in Azure)
3. The SharePoint Designer danger of developing in production rather than a test environment
4. Always run SPDipsose Check
Jeremy, also took this talk to SharePoint Saturday Philly. You should be able to visit this site shortly and receive slides and possibly a recording of Jeremy's talk.
References
Jeremy Thake
Webcast: Introducing SharePoint 2010 (SP2010) Development to ALM (VS2010 and TFS 2010)
SharePoint ALM Resource Center
SharePoint Patterns & Practices Group (SPG)
SPDisposeCheckStatic Rules
He began with defining ALM as the continuous process of managing the life an application through governance development. He also referred to David Chapell's Document, Application Life Cycle Management as a Business Process.
He then informed the group that there are three aspects to ALM, and they are Governance, Deployment and Operations, but the key here is that Governance should happen all the way through. He also went into deep discussion about Coding, Testing and Tracking.
Jeremy's message was packaged with warning labels.
What were we warned about?
1. To package all custom code as a WSP
2. The importance of Source Control, Build Server (no test should be deployed without putting it on a build server to make sure that they are checking in everything that is required), and Team Foundation Server (TFS) (also running in Azure)
3. The SharePoint Designer danger of developing in production rather than a test environment
4. Always run SPDipsose Check
Jeremy, also took this talk to SharePoint Saturday Philly. You should be able to visit this site shortly and receive slides and possibly a recording of Jeremy's talk.
References
Jeremy Thake
Webcast: Introducing SharePoint 2010 (SP2010) Development to ALM (VS2010 and TFS 2010)
SharePoint ALM Resource Center
SharePoint Patterns & Practices Group (SPG)
SPDisposeCheckStatic Rules
No comments:
Post a Comment