MSF (Microsoft Solution Framework)
Download as PPT, PDF1 like3,590 views
The document discusses the Microsoft Solutions Framework (MSF) team model. It outlines common problems that can occur in teams such as projects being late, over budget, or not meeting requirements. It then presents the MSF team model which focuses on principles like clear communication, customer focus, empowering team members, and establishing shared accountability. The model advocates for interdisciplinary teams, co-located work, and total team participation in design. It describes different role clusters within the model and ways to scale teams up or down based on factors like size and complexity.
MSF (Microsoft Solution Framework)
- 1. MSF (Microsoft Solutions Framework) Team Model Deniz KILINÇ Volkan ABUR
- 2. Problems, problems, problems... “ This thing is unpredictable – we keep discovering new problems” “ It’s just too difficult to use” “ We couldn’t get the information we needed to do our work” “ We were unaware of how the work of other team members affected our work” “ The project was late and over budget” “ What was built really isn’t what we needed” “ It doesn’t meet our expectations – we’re not happy” “ We didn’t understand clearly what we were supposed to do” “ We can’t get it to operate well in our environment”
- 3. 2W, 1H (What, Who, How) Establish good communications Goals to Success Deliver within project constraints Build to specifications Release with issues identified and addressed Deploy smoothly and prepare well for ongoing operations Enhance user effectiveness “ The project was late and over budget ” “ What was built really isn’t what we needed ” “ This thing is unpredictable – we keep discovering new problems ” “ We can’t get it to operate well in our environment ” “ It’s just too difficult to use ” Problems Satisfy customers Owner “ It doesn’t meet our expectations – we’re not happy ” ? ? ? ? ? ? “ Needed information is not shared timely to all who need it ” ?
- 4. MSF Team Model Clear Communication Delivering the solution within project constraints Satisfied customers Enhanced user effectiveness Smooth deployment and ongoing operations Approval for release only after all quality issues are identified and addressed Building to specification Development Test Release Management User Experience Product Management Program Management
- 5. MSF Team Model Hierarchy No hierarchy between project members Everyone is equal
- 6. Project sponsors Customers (business sponsors) End users Operations ... External Stakeholders
- 7. Work toward a shared vision Focus on business value Stay agile, expect change Empower team members Foster open communications Establish clear accountability, shared responsibility Team Model – Principles
- 8. Team of peers Customer-focused mindset Product mindset Zero defect mindset Willingness to learn Team Model – Key Concepts
- 9. Use small, interdisciplinary teams Enable teams to work together at a single site Create a soultion design through total team participation Team Model – Proven Practices
- 10. Team Model – Role Clusters Communication Development Test Release Management User Experience Product Management Program Management
- 11. Functional areas Responsibilities Tasks Program management Project management Drive overall solution design Manage functional specification Maintain traceability map Liaise with other project teams on interoperability issues Solution architecture Example Role cluster (role)
- 12. Functional Areas of Role Clusters Business value Marketing Customer advocacy Product planning Project management Solution architecture Process assurance Administrative services Test planning Test engineering Test reporting Infrastructure Support Operations Logistics Commercial release management Accessibility Internationalization User advocacy Training/support material Usability research and testing User interface design Technology consulting Implementation architecture and design Application development Infrastructure development Development Test Release Management User Experience Product Management Program Management
- 13. Extended Team Operations and Support Groups Technology Focus Business Focus Users Project Sponsor Customer Technology Architects and Steering Committees Help Desk Project Team Development Test Release Management Program Management User Experience Product Management
- 14. Use factors such as complexity, size, risk, and skills for scaling Divide large teams into smaller teams, which have lower process, management, and communication overhead and allow faster implementation Designate team leads for sub-teams Use core team to manage overall project Core team is composed of team leads and program management Core team coordinates and synchronizes sub-teams Ways to Scale Up Teams
- 15. Lead and Feature Teams Desktop Feature Team Program Management User Experience Development Test Lead Team File and Print Feature Team Program Management User Experience Development Test Messaging Feature Team Program Management User Experience Development Test
- 16. Combining Roles for Small Teams Roles may be combined, but some combinations pose risks P Possible U Unlikely N Not Recommended Product Management Program Management Development Test User Experience Release Management Product Management Program Management Development Test User Experience Release Management N N N N N N N N N N N N P P P P P P P P P P U U U U U U U U
- 17. Small Team Example Release Management User Experience Product Management Test Program Management Development