2. Microsoft Office Solution Accelerator for Six Sigma – A Case Study in Project Server Customization Brian Smith Program Manager Information Worker New Markets Microsoft Corporation

3. What are we going to Learn Today What is Six Sigma How we can expose project data to the Project Guide How we can expose external data through Project Center How we can work with WSS templates Pulling it all together with InfoPath

4. What is Six Sigma? A rigorous approach to solving problems and improving processes by leveraging facts and data Can be viewed from multiple perspectives PhilosophyMeasureMethodology

5. Six Sigma Measure Sigma Defects per million Cost of Poor Quality 6 sigma 3.4 <10% of sales World Class 5 sigma 230 10 to 15% 4 sigma 6,200 15 to 20% Industry average 3 sigma 67,000 20 to 30% 2 sigma 310,000 30 to 40% Noncompetitive 1 sigma 700,000

6. Six Sigma Measure

7. Six Sigma Methodology Standardized data driven approach to problem solving Process and input focus Variance reduction and process optimization Eliminating the opportunity for defects to occur

8. DMAIC Roadmap A X X X X X X X X X X X Analyze Inputs Screen Inputs X ToolsetStatistical Y=X 1..X 2 I Process Changes Improved “Y” USL 4812160 LSL X 1..X 2 D Problem Statement CTQ “Y” C Lock down X’s Sustain The Gain! X 1..X 2

9. What is the Microsoft Office Solution Accelerator for Six Sigma? A solution built on top of Microsoft Office Project that aids the management, control and reporting of Six Sigma project programs A case study of how to extend Project to solve a specific business problem

10. Components of the Accelerator Dynamic Project Guide Financial tracking application Extension to Windows SharePoint Services integration InfoPath Project Selection form Microsoft Office Data Assistant for PowerPoint

11. Dynamic Project Guide Project Data Service access to task content Navigation Document access Context sensitive help Uses.NET application rather than static XML file

12. Screen Shot of Project Guide

13. Project Guide

14. Financials Hosting Office Web Components in Project Professional and Project Web Access Accessing project related data through Project Center views

15. Financials

16. Project Center Accessing External Data

17. So how does Project Center see our data? Data table for Financials One or more views to filter the data Final view linked to Project Stored Procedure

18. Project Center Reporting & Selection How does the Project Center view get its data? Columns are specified in the MSP_WEB_VIEW_FIELDS These will then be available to be added to Project Center views The display text is specified in MSP_WEB_CONVERSIONS The data is found from the result of the stored procedure MSP_WEB_SP_SEC_GetPortfolioViewRSBasedOnFiel dList

19. MSP_WEB_VIEW_FIELDS table The table holds the references to all the fields available within Project Center views A full reference can be found in pjsvrdb.htm on the Project Server CD (in the docs directory) Key fields to note:- WFIELD_NAME_OLEDB The name of the field used in the Microsoft Project OLE DB provider WFIELD_NAME_SQL The name of the field in the Microsoft Project Server database (in the stored procedure in a few slides time) WFIELD_NAME_CONV_VALUE Refers to the CONV_VALUE field in the MSP_WEB_CONVERSIONS table, which provides the localized description of the field Continued….

20. MSP_WEB_VIEW_FIELDS table WFIELD_TEXTCONV_TYPE The type of field 1 String 4 Date 5 Percent (for example, 5%) 9 Cost (for example, $5.00)11Cost rate (for example, $5/hr) 12 Units 15 Plain number Only numeric values will be “rolled-up” in the views!

21. MSP_WEB_CONVERSION table This table holds the localized string values referred to in the previous table STRING_TYPE_ID STRING_TYPE_ID Refers to a valid STRING_TYPE_ID in the MSP_WEB_STRING_TYPES table CONV_VALUE The ID value of the string (link to previous table) LANG_ID The ID of the language in which the conversion text is displayed, for example: 1033 is the language ID for English, the default language for the database CONV_STRING The text value of the string

22. MSP_WEB_SP_SEC_ GetPortfolioViewRSBasedOnFieldList This stored procedure gets the data from the database for the Project Center views The procedure is listed in the notes field for reference, including in bold our addition to link to our view table

23. In summary… We add rows to the Project center tables We amend the stored procedure to also link to our summary data view We create the Financial view to have the per project data we want We use multiple views for ease of following the flow – it could be one

24. Project and Windows SharePoint Services Integration Project Specific WSS sites Create sites that match the project template – complete with content Front end or back end templates Object Link Provider Map content of site to tasks within project

25. STSADM Your friend on the command line How do I load templates? stsadm.exe -o addtemplates -f -title "Six Sigma template" -description “Description goes here" What templates do I have loaded? stsadm –o enumtemplates What is the “name” that the createsite method expects? _GLOBAL_#1 or something similar

26. Project and WSS

27. InfoPath – Pulling it all together. Collect project ideas Rank based on customizable criteria Create project and collaboration site based on templates

28. InfoPath Project Selection

29. Call to action! Take all or some of these scenarios to extend the use of Project and Windows SharePoint Services

30. Source Code The source code for the Microsoft Office Solution Accelerator for Six Sigma will be made available to partners on request Training session – date to be advised Limited support – 90 days post training

31. © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.