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 DCFebruary 10, 2011

2. Who Am I?Marie-Michelle Strah, PhDTwitter: @cyberslateEmail: michelle AT lifeincapslockDOT comBlog: http://lifeincapslock.comLinkedin: www.linkedin.com/in/drstrahSharePoint Solutions Architect and Practice Lead, BroadPoint Technologies www.broadpoint.netWomen in SharePoint DCwww.meetup.com/womeninspdcWomen in SharePointwww.womeninsharepoint.org

3. “Getting your head around the SharePoint beast”Developers: Mark Rackleyhttp://www.sharepointhillbilly.comArchitecture/Security: Adam Buenz, MVPhttp://www.sharepointsecurity.comProject Management: Dux Raymond Sy, MVPhttp://sp.meetdux.com

4. RANT! RANT! RANT!

5. Building Blocks for Success (Internal)SharePoint TeamArchitect (s)PMBusiness AnalystInformation ArchitectDeveloper (s) and flavorsAdmins, admins, admins…Branding/design experts (UI/UX)Security, Reporting, BDC/BCS, Search, Performance…Third PartyClient Side Resources

6. Building Blocks for Success (Service Delivery)Executive Buy InScope, scope, scopeRequirements, requirements, requirementsTeam members who didn’t know they were SharePoint team members:Sales, sales, salesMarketing, marketing, marketingProposal and capture management

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

8. Professional Services Matrix – SharePoint/XRM Execution GapProductPlatformProgrammatic SpecializedProcedure-Based Solution-BasedDiscrete/Structured Open/Unstructured Domain-Specific EnterpriseExecution-Intensive Diagnosis-Intensive Low Client Risk High Client RiskHigh Fee Sensitivity High FeesShorter Term Longer Term/ExtendableEfficiency (Standardization) Expertise (Customization)

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

10. Crossing the divide10 Best Practices for Building SharePoint Solutions (2009)http://msdn.microsoft.com/en-us/magazine/dd458798.aspx1. Know When to Cross the DivideAn 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 BoxCustomization and configurationCustom CodeThird Party Add OnChallenge and Opportunity: Creative, Flexible, Adaptable

12. Plan for Change ManagementWaterfall/AgileProduct ImplementationMental Models“Closed” ShopsChuck Norris andChange Management…

13. Organic Model: SDLC “Cycle” for SharePointPROGRAM MGT

14. - Project Mgt

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

16. Agile Methodologies and SharePointAdapt the adaptableIterative frameworkLessons learnedUser stories and user adoption:FeedbackFocus GroupHelp Desk Web Part is Your Friend!

17. Case Study: SDLC “Cycle” for SharePoint

18. Questions and DiscussionThank you for your time!Marie-Michelle Strah, PhDTwitter: @cyberslateEmail: michelle AT lifeincapslock DOT comBlog: http://lifeincapslock.comLinkedin: www.linkedin.com/in/drstrah