420 likes | 559 Views
Michael Blumenthal, Sr. Consultant at Magenic with over 16 years in IT consulting, offers insights into effectively managing SharePoint site requests. With a high demand for new sites from emerging teams and projects, it’s crucial to empower users while maintaining governance. This guide outlines a structured process to identify business and technical requirements, the roles and responsibilities of requestors, approvers, and site owners, and key aspects to consider in user experience and workflow tools. Achieve the right balance for sustainable governance and self-service.
E N D
Intelligent Site Request Automation Michael Blumenthal Magenic Technologies MichaelBl@Magenic.com
Who is Michael Blumenthal? • Sr. Consultant @ Magenic (MSFT Gold Partner) • 16+ years in IT Consulting • 9 years working with SharePoint • MCITP: SharePoint 2010; MCTS: WSS Dev • MCTS: MOSS Config & MCTS: WSS Config • MCAD, MCSE, MCDBA, CAPM, INETA Champ
You have a very high demand for new SharePoint sites. New teams and projects starting daily!
Conflict Self-Service vs. Governance
You want a process that empowers the users while providing control.
Identify your Business Requirements. Business + Technical + Example
There are three major roles. Business + Technical + Example People + Data + Flow
Identify Requestor Requirements. Business + Technical + Example People + Data + Flow Requestor Approver Owner
Identify the approvers. Business + Technical + Example People + Data + Flow RequestorApprover Owner
Identify the site owners. Business + Technical + Example People + Data + Flow Requestor Approver Owner
What site metadata do you need? Business+ Technical + Example People + Data + Flow
What’s the flow? Business+ Technical + Example People + Data + Flow
How many Decisions per Step? Business+ Technical + Example People + Data + Flow Decisions Next Roles Draw
Who’s Next? Business+ Technical + Example People + Data + Flow Decisions Next Roles Draw
People vs. Roles Business+ Technical + Example People + Data + Flow Decisions Next Roles Draw
Draw it out Business+ Technical + Example People + Data + Flow Decisions Next Roles Draw
Identify your Technical Requirements. Business + Technical+ Example
Tradeoffs: Cost vs Built In Tools Business + Technical+ Example Tools + UX EditionTradeoffs, Choices
Picking your workflow tools. Business + Technical+ Example Tools + UX Edition Tradeoffs, Choices
Understand the User Experience Business + Technical+ Example Tools + UX
Workflow isn’t just in a web browser. Business + Technical+ Example Licensing+ UX WF Alerts Bv.B
Using Alerts has implications. Business + Technical+ Example Licensing+ UX WF AlertsBv.B
Buy, Build, or mix? Business + Technical+ Example Licensing+ UX WF Alerts Bv.B
Put it all together! Business + Technical+ Example
One of my clients needed a Site Provisioning Solution. Business + Technical+ Example Reqs + Screens + Inside
People Business + Technical+ Example Reqs + Screens + Inside People + Data + Flow
Data Business + Technical+ Example Reqs + Screens + Inside People + Data + Flow
Flow Business + Technical+ Example Reqs + Screens + Inside People + Data + Flow
1 of 6 Business + Technical+ Example Reqs+ Screens + Inside . . . . . .
2 of 6 Business + Technical+ Example Reqs+ Screens + Inside . . . . . .
3 of 6 Business + Technical+ Example Reqs+ Screens + Inside . . . . . .
4 of 6 Business + Technical+ Example Reqs+ Screens + Inside . . . . . .
5 of 6 (top) Business + Technical+ Example Reqs+ Screens + Inside . . . . . .
5 of 6 (bottom) Business + Technical+ Example Reqs+ Screens + Inside . . . . . .
6 of 6 Business + Technical+ Example Reqs+ Screens + Inside . . . . . .
Conflict Self-Service vs. Governance
You want a process that empowers the users while providing control.
Resources BlumenthalIT.Net, MichaelBL@Magenic.com, @MichaelBL Magenic.com CSPUG.ORG, SharePointSaturday.Org/Chicago Msdn.microsoft.com Blogs.msdn.com SharePointReviews.com K2.com, Nintex.com
Enterprise SP Development Experts • SDPS Program Member Numerous Microsoft Competencies, including: PS: We’re hiring!