Ausspc 2011 operational frameworks and deployment


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Opening slide please include
  • Ausspc 2011 operational frameworks and deployment

    1. 1. Platinum<br />Gold <br />AUSTRALIA<br />SHAREPOINT<br />CONFERENCE<br />MARCH 8+9 2011<br />
    2. 2. Joel Oleson<br />@joeloleson<br />Quest Software<br />Operational Governance<br />
    3. 3. Agenda<br />Deployment Example: The Vasa<br />Why do we need Governance or Operations Frameworks?<br />Intro to ITIL<br />Intro to MOF v4<br />Intro to Agile Scrum Project Management Methodology<br />
    4. 4. The Story of the Vasa the Greatest Military Ship<br />
    5. 5. The Vasa – Deployment Nightmare!<br />Designed by HenrikHybertsson to be the mightiest warship in the world<br />Maiden voyage was designed to be propaganda for the Swedish king GustavusAdolphus<br />150 people on board<br />30-50 died in the disaster<br />Salvaged in 1961<br />Initial declared sank due to "imprudence and negligence“<br />Inquiries declared it was well built, but poorly proportioned<br />
    6. 6. Why Use Governance or Operations Frameworks?<br />“Governance and Management frameworks are designed to support and optimize the quality of the service…”<br />
    7. 7. ITIL – IT Infrastructure Library<br />“The fastest cars have the best brakes…”<br />
    8. 8. ITIL 5 Elements of Lifecycle<br />Strategy<br />Design<br />Transition <br />Operation<br />Continual Improvement<br />
    9. 9. Microsoft Operations Framework MOF v4<br />
    10. 10. Essential IT Service Management<br />Process, People, and Technology (PPT)<br />Strategy, Tactics and Operations (STO)<br />Separation of Duties (SoD)<br />Strategic Alignment Model Enhanced (SAME)<br />Deming’s Plan-Do-Check-Act Management Cycle (PDCA)<br />
    11. 11. Who, What, How & Why <br />
    12. 12. Key Service Management Questions<br />Who will secure sensitive information? <br />Who will assign users & permissions in SharePoint 2010? <br />Who will create and approve content for sites? <br />Who will be able to create new sites? <br />Who will be able to publish content to Web sites? <br />Who will be able to customize sites? <br />
    13. 13. Strategy to OperationsObjectives are translated into specific goals, directed and controlled<br />
    14. 14. Separation of Duties<br />
    15. 15. SharePoint Service Quality Controls<br />SharePoint 2010 farm structure farm and service topology<br />Minimum Performance level<br />Disaster Recovery - Recovery Time Objective, Recovery Point Objective<br />Information Architecture – Managed Metadata, Tagging, Content Structure, Web structure: Site vs. Site Collection, Site & Doc Templates<br />Taxonomy - Who are the owners, what are the content levels, what is the taxonomy<br />Subarea design. What kind of data flow, content control, and site structure will be used? Who is responsible for defining that? <br />
    16. 16. SharePoint Service Quality Controls<br />User and Security Group management<br />Quality Assurance & Test<br />Risk management <br />Contract management <br />Development Methodologies<br />Configuration management, including documentation <br />Business and Service Requirements – i.e. <br />
    17. 17. MOF Essential Phases<br />
    18. 18. What is the Next Milestone?<br />Milestones are constructed both to reassure the traveller that the proper path is being followed and to indicate distance travelled<br />
    19. 19. IT Service improvements<br />Since IT services are recognized as strategic business assets, organizations need to continually improve the contribution of IT services to business functions, in terms of better results at lower cost.<br />
    20. 20. Getting Agile with Scrum<br />Project Management Framework for handling rapidly changing requirements.<br />Scrum is an agile process for software development. <br />With Scrum, projects progress via a series of iterations called sprints. <br />Each sprint is typically 2-4 weeks long. <br />Scrum is ideally suited for projects with rapidly changing or highly emergent requirements.<br />
    21. 21. Questions<br />
    22. 22. Gold Sponsors<br />Silver Sponsors<br />Bronze Sponsors<br />