Your SlideShare is downloading. ×
Ausspc 2011 operational frameworks and deployment
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Opening slide please include
  • Transcript

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