This document summarizes a presentation on developing a SharePoint solution using an iterative SDLC approach. It discusses building the necessary team roles, requirements gathering, different service delivery models for customizing SharePoint, and adapting agile methodologies. Change management is also highlighted as critical, including adopting organic development cycles and gathering user feedback. The presentation provides a case study example of applying this iterative SDLC cycle for a successful SharePoint implementation.

1. Case Study for a SharePoint SDLC SharePoint User Group of Washington DC & Women in SharePoint DC February 10, 2011

2. Who Am I? Marie-Michelle Strah, PhD Twitter: @cyberslate Email: michelle AT lifeincapslockDOT com Blog: http://lifeincapslock.com Linkedin: www.linkedin.com/in/drstrah SharePoint Solutions Architect and Practice Lead, BroadPoint Technologies www.broadpoint.net Women in SharePoint DC www.meetup.com/womeninspdc Women in SharePoint www.womeninsharepoint.org

3. “Getting your head around the SharePoint beast” Developers: Mark Rackley http://www.sharepointhillbilly.com Architecture/Security: Adam Buenz, MVP http://www.sharepointsecurity.com Project Management: Dux Raymond Sy, MVP http://sp.meetdux.com

4. RANT! RANT! RANT!

5. Building Blocks for Success (Internal) SharePoint Team Architect (s) PM Business Analyst Information Architect Developer (s) and flavors Admins, admins, admins… Branding/design experts (UI/UX) Security, Reporting, BDC/BCS, Search, Performance… Third Party Client Side Resources

6. Building Blocks for Success (Service Delivery) Executive Buy In Scope, scope, scope Requirements, requirements, requirements Team members who didn’t know they were SharePoint team members: Sales, sales, sales Marketing, marketing, marketing Proposal and capture management

7. Service Delivery Model CMMIwww.sei.cmu.edu – federally funded research center Carnegie Mellon

8. Professional Services Matrix – SharePoint/XRM Execution Gap ProductPlatform Programmatic Specialized Procedure-Based Solution-Based Discrete/Structured Open/Unstructured Domain-Specific Enterprise Execution-Intensive Diagnosis-Intensive Low Client Risk High Client Risk High Fee Sensitivity High Fees Shorter Term Longer Term/Extendable Efficiency (Standardization) Expertise (Customization)

9. Product or a Platform? Inherited models Both/and Best of… Leverage native capabilities and custom application development - IaaP

10. Crossing the divide 10 Best Practices for Building SharePoint Solutions (2009) http://msdn.microsoft.com/en-us/magazine/dd458798.aspx 1. Know When to Cross the Divide An issue that arises early in a SharePoint development project is how best to interact with other systems. Because SharePoint is a composite application platform, this question is one you will likely have to answer often. Viewing the SharePoint architecture from the Web application level is the easiest way to go about it. An instance of SharePoint contains multiple Web applications. If you are not familiar with SharePoint application architecture, you should review "Architectural Overview of Office SharePoint Server 2007."

11. Solution Delivery Spectrum (SharePoint “Ecosystem”) Out of the Box Customization and configuration Custom Code Third Party Add On Challenge and Opportunity: Creative, Flexible, Adaptable

12. Plan for Change Management Waterfall/Agile Product Implementation Mental Models “Closed” Shops Chuck Norris and Change Management…

14. - Project Mgt

15. - GovernanceSource: Gary Vaughn http://www.box.net/shared/9u2ik72t1z

16. Agile Methodologies and SharePoint Adapt the adaptable Iterative framework Lessons learned User stories and user adoption: Feedback Focus Group Help Desk Web Part is Your Friend!

17. Case Study: SDLC “Cycle” for SharePoint

18. Questions and Discussion Thank you for your time! Marie-Michelle Strah, PhD Twitter: @cyberslate Email: michelle AT lifeincapslock DOT com Blog: http://lifeincapslock.com Linkedin: www.linkedin.com/in/drstrah