Microsoft’s Best Practices For IT Solutions Success. Microsoft Solutions Framework Executive Overview. Kyle Korzenowski Product Planner Microsoft Business Solutions email@example.com. Agenda. IT Challenges and Opportunities MSF Overview Team Model Process Model Risk Management
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Microsoft Business Solutions
“When projects fail, it’s rarely technical.”
Jim Johnson, Chairman,
The Standish Group
~80% of risk/failure is due to non-technical factors.
A methodology applies specific directions to a known destination
A framework, like a compass, verifies progress and provides directional guidance
A framework is a methodology partner!
Microsoft Worldwide Products Groups
Twenty-five years of Microsoft experience
MSF evolution:Since 1993
Fast, Effective Process!
Project Management Discipline – Getting Results
Risk Management Discipline – Minimize Surprises
Readiness Management Discipline – Anticipate & Grow Skills
Team members share roles
Be sure all perspectives are represented
Avoid conflicts of interest
Scaling up: Feature and/or function teams
Feature teamsMultidisciplinary sub-teams organized around feature sets
Function teamsUnidisciplinary sub-teams organized by functional roleScaling Roles to Small and Large Projects
Function teams can also be employed.
Risk Management Document
Question:What’s a risk assessment? When should we consider doing them for a project?Risk Assessment
A Risk realized (100% probability) becomes an Issue.
Identifying, analyzing, and addressing risk proactively
To manage risk proactively
Anticipate problems vs. Fixing them when they occur
Address root causes vs. Addressing symptoms of the cause
Prevent and minimize risk vs. Reacting to consequencesthrough mitigation
Prepare for consequences vs. Reacting to a crisisto minimize impact
Use a known and vs. Using an ad-hoc processstructured process
Areas for consideration during risk assessment:
The three risk management goals are to:
The objective is to LEARN from the experience by facilitating a very open, blame-free discussion of project successes and mistakes.
IV. Stabilizing: “Release” Milestone
V. Deploying: “Deployment Complete” Milestone
I. Envisioning: “Vision Approved” Milestone
II. Planning: “Scope Complete” Milestone
III. Developing: “Scope Complete” Milestone
Endorsement process for:
Customers & Consultants
MSF Master Trainers
Online Resource Library
Online Community:Ask questions and share ideas with:
Community membersMSF Services & Support
Microsoft Solution Offerings, Products, and Services