Best Practices in Gathering Requirements for SharePoint Projects
13 likes7,103 views
The document outlines best practices for gathering requirements for SharePoint projects, emphasizing the importance of a well-defined business case and the key components of the requirements gathering process. It highlights the significance of requirements traceability for defining return on investment (ROI) in SharePoint projects. The content also covers elicitation, analysis, validation of requirements, and producing a requirements document.
1 of 34
Downloaded 1,147 times
Ad
Recommended
How to Write Amazing Functional Analysis Documents for your SharePoint Projects
How to Write Amazing Functional Analysis Documents for your SharePoint Projects GSoft The document provides an overview of a presentation on how to write functional analysis documents for SharePoint projects. It discusses defining requirements, prioritizing requirements, and a 9-step methodology for functional analysis when using SharePoint. The methodology includes steps like visualizing requirements, describing information types, defining relationships between data, determining data storage and flows, and defining data access points and behaviors. The presentation provides examples and tips for effectively analyzing requirements and functionality for SharePoint solutions.
The importance of a Business Analyst on SharePoint Projects
The importance of a Business Analyst on SharePoint ProjectsMichal Pisarek The document discusses the pivotal role of SharePoint analysts in successful SharePoint implementations, emphasizing the need for business alignment and understanding user requirements. It outlines common challenges faced in SharePoint projects, including stakeholder involvement, organizational readiness, and the importance of effective change management. The document also highlights various tools and techniques that can aid in facilitating collaborative sessions and gathering insights for SharePoint solutions.
How to Best Gather Requirements for SharePoint Projects
How to Best Gather Requirements for SharePoint ProjectsDux Raymond Sy This document discusses best practices for gathering requirements for SharePoint projects. It outlines the requirements gathering process, including eliciting requirements, analyzing requirements, validating requirements, and documenting requirements in a requirements document. It emphasizes defining business needs, mapping needs to user and system requirements, and creating traceability between requirements.
SPFest Chicago - Practical Tools and Techniques for the SharePoint Business A...
SPFest Chicago - Practical Tools and Techniques for the SharePoint Business A...Richard Harbridge This document summarizes a presentation on practical tools and techniques for SharePoint business analysts and information architects. The presentation covers several topics:
1. Why SharePoint BA/IA can be difficult due to the large and complex nature of SharePoint and differing stakeholder needs.
2. The importance of identifying objectives and prioritizing them based on value and difficulty. Objectives should be specific, measurable, achievable, relevant and time-bound.
3. Best practices for SharePoint projects such as using an iterative approach, prototyping solutions, and gathering feedback continuously.
4. Tools and techniques for visualizing and communicating SharePoint concepts such as mind mapping, card sorting, and wireframing
SharePoint Saturday South Florida - Future Proofing Your SharePoint Strategy
SharePoint Saturday South Florida - Future Proofing Your SharePoint StrategyRichard Harbridge The document discusses strategies for future-proofing a SharePoint implementation. It emphasizes having a comprehensive SharePoint strategy that includes individual strategies for areas like governance, security, development and more. It stresses the importance of executive support, clear objectives, governance structures and processes, and addressing the needs of both IT and the business. The presentation provides examples of governance deliverables and considerations for each area of the strategy to help organizations scale their SharePoint use over time.
Best Practices - The Seven Most Important Success Factors
Best Practices - The Seven Most Important Success FactorsRichard Harbridge The document discusses the seven most important non-technical factors for SharePoint success: understanding requirements and limitations, accurate effort estimation, achieving buy-in, determining return on investment, governance, user adoption, and planning for new work. It emphasizes understanding business needs, communicating vision, using metrics, collaborative teams, an iterative approach, and managing capabilities. Success requires understanding both technical and non-technical issues to avoid common reasons for project failure.
Demystifying SharePoint Governance and User Adoption
Demystifying SharePoint Governance and User AdoptionWes Preston The document outlines the importance of governance and user adoption within SharePoint, emphasizing that these concepts should not be intimidating for organizations. It provides insights on effective planning, implementation, and ongoing management strategies that evolve as the organization matures and user needs are addressed. Key takeaways include the need for communication, user involvement in solution development, and continuous support to ensure successful user adoption.
SharePoint Lists: Used, Abused and Underappreciated
SharePoint Lists: Used, Abused and UnderappreciatedWes Preston The document discusses best practices for utilizing SharePoint lists effectively, emphasizing the importance of user training to enhance productivity. It covers tips for building and displaying lists, managing intake requests, and avoiding common mistakes such as poor file naming conventions. Additionally, it highlights the evolution of these practices from SharePoint 2007 to 2010 and encourages the implementation of structured training and governance.
Share Australia - The Steps To Effective SharePoint Governance
Share Australia - The Steps To Effective SharePoint GovernanceRichard Harbridge The document discusses the steps for effective SharePoint governance. It recommends establishing 5 governance teams - a business strategy team, solutions/technical strategy team, and 3 tactical teams. Each team has a defined role and responsibilities. Effective governance requires defining objectives, policies, standards and ongoing processes. Governance ensures organizations maximize the benefits of SharePoint while mitigating risks.
Understanding SharePoint Roles
Understanding SharePoint RolesWes Preston Roles are necessary for successful SharePoint implementations and evolve over time. Initially, core roles include the executive champion to provide buy-in, the platform owner to oversee priorities, and an IT pro to manage servers. As implementations mature, additional roles emerge like developers for customizations, business analysts to understand needs, and site collection administrators to decentralize responsibilities. Scenarios like an intranet require roles like designers for branding, and governance committees to determine policies.
Best Practices in Gathering Requirements for SharePoint Projects
Best Practices in Gathering Requirements for SharePoint ProjectsDux Raymond Sy The document outlines best practices for gathering requirements for SharePoint projects. It discusses the importance of having a well-defined business case to start the requirements gathering process and identifies the key components of requirements gathering as elicitation, analysis, validation, and documentation. The presentation teaches that gathering requirements properly is essential for defining the return on investment of SharePoint projects.
2013 SharePoint Fest DC - Build a SharePoint Intake/Request List
2013 SharePoint Fest DC - Build a SharePoint Intake/Request ListWes Preston This document provides an overview of how to build a SharePoint intake/request list to manage various business requests. It discusses setting up the list with appropriate columns, using content types and workflow to customize new/edit forms, creating views for different roles, and basic post-build metrics and improvements. The example used is a site request list for managing requests for new SharePoint sites, but the approach can be adapted for various business processes.
SharePoint Saturday - SharePoint Success
SharePoint Saturday - SharePoint SuccessRichard Harbridge The presentation by Richard Harbridge at SharePoint Saturday 2009 focuses on effectively managing and implementing SharePoint projects, highlighting the importance of buy-in, governance, and user adoption. Key points include establishing a clear vision, maintaining momentum, and understanding the cost of ownership and expected returns on investment. Harbridge emphasizes an iterative approach to implementation, effective communication, and the necessity for user training to ensure successful adoption.
SharePoint Fest Denver - Everything You Need To Know About SharePoint Social ...
SharePoint Fest Denver - Everything You Need To Know About SharePoint Social ...Richard Harbridge This document discusses SharePoint's social capabilities. It begins with an introduction by Richard Harbridge and then discusses how SharePoint's social features can lower costs, surface knowledge, and increase employee engagement. Examples of social features that are explored include wikis, blogs, discussions, My Sites, user profiles, pictures, activities, tags, notes, ratings, and people search. The presentation emphasizes how these social features can be leveraged across SharePoint, not just in communities, and provides demonstrations of wikis, blogs, profiles, and people search.
Build Customise Or Buy? Share South Africa
Build Customise Or Buy? Share South AfricaRichard Harbridge The document is a presentation about when to build custom SharePoint solutions, buy third party products, or extend SharePoint capabilities. It discusses how decisions are difficult with SharePoint due to its large ecosystem. It provides examples of scenarios around migrations and permissions management and discusses questions to consider when evaluating options. The presentation aims to help attendees understand the build vs buy decision-making process.
SharePoint Summit Toronto - Practical Information Architecture Tools and Tech...
SharePoint Summit Toronto - Practical Information Architecture Tools and Tech...Richard Harbridge This document provides an overview of a presentation on practical tools and techniques for SharePoint information architects. The presentation covers why SharePoint information architecture is difficult due to its large scale and complex people aspects. It discusses using an iterative approach to define problems and build solutions. The presentation aims to share ideas and tools to help attendees improve communication and gain knowledge to use with confidence. It outlines covering topics like visualizing and communicating SharePoint concepts, making IA decisions, and tips and tricks, as well as a case study approach.
Richard Harbridge: 7 SharePoint Success Factors
Richard Harbridge: 7 SharePoint Success FactorsSharePoint Saturday NY The document discusses seven non-technical factors for SharePoint success: understanding requirements and limitations, accurate estimation, achieving buy-in, determining return on investment, implementing governance, supporting users iteratively, and planning for new work. It emphasizes understanding business needs, sharing expectations, using metrics, collaborative teamwork, communication, and managing capabilities.
SharePoint Live - Steps to Effective Governance
SharePoint Live - Steps to Effective GovernanceRichard Harbridge The document discusses establishing effective governance for SharePoint. It recommends forming 5 governance teams: a Business Strategy Team, Solutions/Technical Strategy Team, and 3 Tactical Teams. The roles and responsibilities of each team are described. The Business and Solutions/Technical Strategy Teams would define objectives and priorities and map solutions to objectives. The Tactical Teams would focus on operations, development, and support activities needed to execute the strategic direction set by the other teams. Effective governance is presented as key to ensuring SharePoint investments are successful and deliver business value.
SharePoint Saturday New Hampshire - The Seven Most Important SharePoint Succe...
SharePoint Saturday New Hampshire - The Seven Most Important SharePoint Succe...Richard Harbridge The document discusses factors for successful SharePoint implementations. It emphasizes the importance of understanding requirements, limitations of the software, and accurately estimating effort. It also stresses achieving buy-in from IT and decision makers by focusing on cost reduction and adding business value. Additionally, the document recommends prioritizing initiatives based on estimated value and difficulty, and measuring both financial and non-financial return on investment. Finally, it outlines effective governance through cross-functional teams focused on strategy, operations, development, and support.
Tackling Adoption Like A Service With SharePoint & Office 365 (SPTechCon)
Tackling Adoption Like A Service With SharePoint & Office 365 (SPTechCon)Richard Harbridge The document presents a framework for enhancing adoption of Microsoft 365 and Office 365 through a service-oriented model rather than project-based initiatives. It emphasizes continuous engagement, measurement, and the creation of champions within organizations to foster a digital center of excellence. Recommendations include developing organized plans for champion selection, user satisfaction surveys, and targeted training while aligning adoption efforts with business objectives.
Succeeding With SharePoint In Seven Steps - Share Atlanta
Succeeding With SharePoint In Seven Steps - Share AtlantaRichard Harbridge Joe implements SharePoint in his company using a seven step approach: 1) Understand business needs, 2) Share alignment and expectations, 3) Measure to improve return, 4) Use governance and teamwork, 5) Take an iterative approach, 6) Promote user adoption, and 7) Manage capabilities and priorities. Key aspects include mapping needs to technology, managing perceptions of stakeholders, prioritizing initiatives, establishing governance processes, and supporting users. Following these steps helps the SharePoint implementation grow over time by expanding functionality and gaining more user dependency. Ongoing management of capabilities and user support is important to maintain success.
Creating your Company's Roadmap to SharePoint Success
Creating your Company's Roadmap to SharePoint SuccessC/D/H Technology Consultants This document discusses creating a roadmap for a company's SharePoint success. It recommends developing a roadmap that defines business priorities, related SharePoint projects to implement initiatives, and an architectural plan. The roadmap approach involves understanding the current state, meeting with stakeholders, defining business goals and projects. Benefits include aligning SharePoint with business needs and defining governance, technology requirements, and a measure of success. The document provides examples of roadmaps and outcomes organizations have achieved.
Career In I.T. as a Business Analyst
Career In I.T. as a Business Analyst Ren Parikh The document outlines a program for starting a career in IT as a business analyst, detailing the prerequisites, training offered, and job opportunities available in various industries. It emphasizes the importance of requirement gathering to avoid project failures and highlights the training methods used, such as classroom sessions and practical exercises. The program includes support for resume preparation, interview preparation, and job placement through a network of recruiters.
SharePoint Fest Denver - The Seven Most Important SharePoint Success Factors
SharePoint Fest Denver - The Seven Most Important SharePoint Success FactorsRichard Harbridge The document discusses best practices for implementing SharePoint successfully. It recommends taking an iterative approach, establishing governance through cross-functional teams, carefully planning support, and managing expectations around the time required. The overall message is that SharePoint implementations require non-technical buy-in, clear objectives, governance, support structures, and an incremental rollout approach to achieve the desired business outcomes.
Future-Proofing Your SharePoint Strategy - Bridgeway Customer Connect
Future-Proofing Your SharePoint Strategy - Bridgeway Customer ConnectRichard Harbridge The document discusses how to future-proof a SharePoint strategy. It recommends achieving a shared understanding of objectives, remaining focused on achieving objectives, and planning for SharePoint challenges and risks. Specifically, it advises defining SMART objectives, prioritizing objectives based on value and difficulty, implementing with the objectives in mind, continuously checking progress towards objectives, and developing strategies for various aspects of the SharePoint implementation like governance, infrastructure, adoption, and integration. The overall message is that implementing SharePoint without a clear strategy can lead to problems, while having a comprehensive strategy can help ensure long-term success.
How to Plan and Manage SharePoint Projects #hkspc
How to Plan and Manage SharePoint Projects #hkspcDux Raymond Sy This document outlines key steps for effectively planning, executing, and controlling SharePoint projects. It discusses establishing success criteria by defining goals and priorities. It emphasizes collaboratively engineering solutions by educating executives and stakeholders on SharePoint's business value. The document also covers developing relevant project plans by defining objectives, work breakdown structures, schedules, and staffing needs. It concludes with guidance on executing and controlling projects through tracking progress, analyzing status, and managing changes.
Understanding SharePoint Online
Understanding SharePoint Online Baltimore SharePoint (BSPUG) The document discusses the transition to SharePoint Online, highlighting the advantages and considerations of cloud-based solutions compared to on-premise deployments. It outlines deployment options, the push towards cloud computing, and the total cost of ownership for various SharePoint configurations. Additionally, it includes case studies to illustrate the practical application of SharePoint in different organizational contexts.
Migrating Your Intranet to SharePoint Online
Migrating Your Intranet to SharePoint OnlinePerficient, Inc. The document discusses the migration of intranets to SharePoint Online, highlighting its benefits, features, and governance requirements. It addresses the differences between SharePoint Online and on-premises versions, migration options, and the importance of a structured governance plan for effective system management. Key topics include user profiles, security, compliance, and the roles of various stakeholders in the administration of SharePoint Online.
15 tips for bullet proof requirements analysis on SharePoint projects
15 tips for bullet proof requirements analysis on SharePoint projectsDocFluix, LLC The document outlines essential techniques for conducting effective requirements analysis and documentation for SharePoint projects, particularly in waterfall methodologies. It emphasizes the importance of clear business versus technical requirements, the cost implications of changes in project scope, and provides guidelines for creating user stories, mockups, and workflow diagrams. Additionally, it highlights the need for thorough documentation of both in-scope and out-of-scope requirements, as well as non-functional requirements to ensure project success.
How to Best Develop Requirements for SharePoint Projects
How to Best Develop Requirements for SharePoint ProjectsDux Raymond Sy The document discusses best practices for developing requirements for SharePoint projects. It emphasizes eliciting requirements through discussions with stakeholders to understand their needs rather than just gathering facts. It also stresses the importance of analyzing requirements to clarify them and ensure the proposed solution will meet the goals, rather than getting paralyzed by over-analysis. Requirements should then be documented in writing for validation.
More Related Content
What's hot (20)
Share Australia - The Steps To Effective SharePoint Governance
Share Australia - The Steps To Effective SharePoint GovernanceRichard Harbridge The document discusses the steps for effective SharePoint governance. It recommends establishing 5 governance teams - a business strategy team, solutions/technical strategy team, and 3 tactical teams. Each team has a defined role and responsibilities. Effective governance requires defining objectives, policies, standards and ongoing processes. Governance ensures organizations maximize the benefits of SharePoint while mitigating risks.
Understanding SharePoint Roles
Understanding SharePoint RolesWes Preston Roles are necessary for successful SharePoint implementations and evolve over time. Initially, core roles include the executive champion to provide buy-in, the platform owner to oversee priorities, and an IT pro to manage servers. As implementations mature, additional roles emerge like developers for customizations, business analysts to understand needs, and site collection administrators to decentralize responsibilities. Scenarios like an intranet require roles like designers for branding, and governance committees to determine policies.
Best Practices in Gathering Requirements for SharePoint Projects
Best Practices in Gathering Requirements for SharePoint ProjectsDux Raymond Sy The document outlines best practices for gathering requirements for SharePoint projects. It discusses the importance of having a well-defined business case to start the requirements gathering process and identifies the key components of requirements gathering as elicitation, analysis, validation, and documentation. The presentation teaches that gathering requirements properly is essential for defining the return on investment of SharePoint projects.
2013 SharePoint Fest DC - Build a SharePoint Intake/Request List
2013 SharePoint Fest DC - Build a SharePoint Intake/Request ListWes Preston This document provides an overview of how to build a SharePoint intake/request list to manage various business requests. It discusses setting up the list with appropriate columns, using content types and workflow to customize new/edit forms, creating views for different roles, and basic post-build metrics and improvements. The example used is a site request list for managing requests for new SharePoint sites, but the approach can be adapted for various business processes.
SharePoint Saturday - SharePoint Success
SharePoint Saturday - SharePoint SuccessRichard Harbridge The presentation by Richard Harbridge at SharePoint Saturday 2009 focuses on effectively managing and implementing SharePoint projects, highlighting the importance of buy-in, governance, and user adoption. Key points include establishing a clear vision, maintaining momentum, and understanding the cost of ownership and expected returns on investment. Harbridge emphasizes an iterative approach to implementation, effective communication, and the necessity for user training to ensure successful adoption.
SharePoint Fest Denver - Everything You Need To Know About SharePoint Social ...
SharePoint Fest Denver - Everything You Need To Know About SharePoint Social ...Richard Harbridge This document discusses SharePoint's social capabilities. It begins with an introduction by Richard Harbridge and then discusses how SharePoint's social features can lower costs, surface knowledge, and increase employee engagement. Examples of social features that are explored include wikis, blogs, discussions, My Sites, user profiles, pictures, activities, tags, notes, ratings, and people search. The presentation emphasizes how these social features can be leveraged across SharePoint, not just in communities, and provides demonstrations of wikis, blogs, profiles, and people search.
Build Customise Or Buy? Share South Africa
Build Customise Or Buy? Share South AfricaRichard Harbridge The document is a presentation about when to build custom SharePoint solutions, buy third party products, or extend SharePoint capabilities. It discusses how decisions are difficult with SharePoint due to its large ecosystem. It provides examples of scenarios around migrations and permissions management and discusses questions to consider when evaluating options. The presentation aims to help attendees understand the build vs buy decision-making process.
SharePoint Summit Toronto - Practical Information Architecture Tools and Tech...
SharePoint Summit Toronto - Practical Information Architecture Tools and Tech...Richard Harbridge This document provides an overview of a presentation on practical tools and techniques for SharePoint information architects. The presentation covers why SharePoint information architecture is difficult due to its large scale and complex people aspects. It discusses using an iterative approach to define problems and build solutions. The presentation aims to share ideas and tools to help attendees improve communication and gain knowledge to use with confidence. It outlines covering topics like visualizing and communicating SharePoint concepts, making IA decisions, and tips and tricks, as well as a case study approach.
Richard Harbridge: 7 SharePoint Success Factors
Richard Harbridge: 7 SharePoint Success FactorsSharePoint Saturday NY The document discusses seven non-technical factors for SharePoint success: understanding requirements and limitations, accurate estimation, achieving buy-in, determining return on investment, implementing governance, supporting users iteratively, and planning for new work. It emphasizes understanding business needs, sharing expectations, using metrics, collaborative teamwork, communication, and managing capabilities.
SharePoint Live - Steps to Effective Governance
SharePoint Live - Steps to Effective GovernanceRichard Harbridge The document discusses establishing effective governance for SharePoint. It recommends forming 5 governance teams: a Business Strategy Team, Solutions/Technical Strategy Team, and 3 Tactical Teams. The roles and responsibilities of each team are described. The Business and Solutions/Technical Strategy Teams would define objectives and priorities and map solutions to objectives. The Tactical Teams would focus on operations, development, and support activities needed to execute the strategic direction set by the other teams. Effective governance is presented as key to ensuring SharePoint investments are successful and deliver business value.
SharePoint Saturday New Hampshire - The Seven Most Important SharePoint Succe...
SharePoint Saturday New Hampshire - The Seven Most Important SharePoint Succe...Richard Harbridge The document discusses factors for successful SharePoint implementations. It emphasizes the importance of understanding requirements, limitations of the software, and accurately estimating effort. It also stresses achieving buy-in from IT and decision makers by focusing on cost reduction and adding business value. Additionally, the document recommends prioritizing initiatives based on estimated value and difficulty, and measuring both financial and non-financial return on investment. Finally, it outlines effective governance through cross-functional teams focused on strategy, operations, development, and support.
Tackling Adoption Like A Service With SharePoint & Office 365 (SPTechCon)
Tackling Adoption Like A Service With SharePoint & Office 365 (SPTechCon)Richard Harbridge The document presents a framework for enhancing adoption of Microsoft 365 and Office 365 through a service-oriented model rather than project-based initiatives. It emphasizes continuous engagement, measurement, and the creation of champions within organizations to foster a digital center of excellence. Recommendations include developing organized plans for champion selection, user satisfaction surveys, and targeted training while aligning adoption efforts with business objectives.
Succeeding With SharePoint In Seven Steps - Share Atlanta
Succeeding With SharePoint In Seven Steps - Share AtlantaRichard Harbridge Joe implements SharePoint in his company using a seven step approach: 1) Understand business needs, 2) Share alignment and expectations, 3) Measure to improve return, 4) Use governance and teamwork, 5) Take an iterative approach, 6) Promote user adoption, and 7) Manage capabilities and priorities. Key aspects include mapping needs to technology, managing perceptions of stakeholders, prioritizing initiatives, establishing governance processes, and supporting users. Following these steps helps the SharePoint implementation grow over time by expanding functionality and gaining more user dependency. Ongoing management of capabilities and user support is important to maintain success.
Creating your Company's Roadmap to SharePoint Success
Creating your Company's Roadmap to SharePoint SuccessC/D/H Technology Consultants This document discusses creating a roadmap for a company's SharePoint success. It recommends developing a roadmap that defines business priorities, related SharePoint projects to implement initiatives, and an architectural plan. The roadmap approach involves understanding the current state, meeting with stakeholders, defining business goals and projects. Benefits include aligning SharePoint with business needs and defining governance, technology requirements, and a measure of success. The document provides examples of roadmaps and outcomes organizations have achieved.
Career In I.T. as a Business Analyst
Career In I.T. as a Business Analyst Ren Parikh The document outlines a program for starting a career in IT as a business analyst, detailing the prerequisites, training offered, and job opportunities available in various industries. It emphasizes the importance of requirement gathering to avoid project failures and highlights the training methods used, such as classroom sessions and practical exercises. The program includes support for resume preparation, interview preparation, and job placement through a network of recruiters.
SharePoint Fest Denver - The Seven Most Important SharePoint Success Factors
SharePoint Fest Denver - The Seven Most Important SharePoint Success FactorsRichard Harbridge The document discusses best practices for implementing SharePoint successfully. It recommends taking an iterative approach, establishing governance through cross-functional teams, carefully planning support, and managing expectations around the time required. The overall message is that SharePoint implementations require non-technical buy-in, clear objectives, governance, support structures, and an incremental rollout approach to achieve the desired business outcomes.
Future-Proofing Your SharePoint Strategy - Bridgeway Customer Connect
Future-Proofing Your SharePoint Strategy - Bridgeway Customer ConnectRichard Harbridge The document discusses how to future-proof a SharePoint strategy. It recommends achieving a shared understanding of objectives, remaining focused on achieving objectives, and planning for SharePoint challenges and risks. Specifically, it advises defining SMART objectives, prioritizing objectives based on value and difficulty, implementing with the objectives in mind, continuously checking progress towards objectives, and developing strategies for various aspects of the SharePoint implementation like governance, infrastructure, adoption, and integration. The overall message is that implementing SharePoint without a clear strategy can lead to problems, while having a comprehensive strategy can help ensure long-term success.
How to Plan and Manage SharePoint Projects #hkspc
How to Plan and Manage SharePoint Projects #hkspcDux Raymond Sy This document outlines key steps for effectively planning, executing, and controlling SharePoint projects. It discusses establishing success criteria by defining goals and priorities. It emphasizes collaboratively engineering solutions by educating executives and stakeholders on SharePoint's business value. The document also covers developing relevant project plans by defining objectives, work breakdown structures, schedules, and staffing needs. It concludes with guidance on executing and controlling projects through tracking progress, analyzing status, and managing changes.
Understanding SharePoint Online
Understanding SharePoint Online Baltimore SharePoint (BSPUG) The document discusses the transition to SharePoint Online, highlighting the advantages and considerations of cloud-based solutions compared to on-premise deployments. It outlines deployment options, the push towards cloud computing, and the total cost of ownership for various SharePoint configurations. Additionally, it includes case studies to illustrate the practical application of SharePoint in different organizational contexts.
Migrating Your Intranet to SharePoint Online
Migrating Your Intranet to SharePoint OnlinePerficient, Inc. The document discusses the migration of intranets to SharePoint Online, highlighting its benefits, features, and governance requirements. It addresses the differences between SharePoint Online and on-premises versions, migration options, and the importance of a structured governance plan for effective system management. Key topics include user profiles, security, compliance, and the roles of various stakeholders in the administration of SharePoint Online.
Viewers also liked (16)
15 tips for bullet proof requirements analysis on SharePoint projects
15 tips for bullet proof requirements analysis on SharePoint projectsDocFluix, LLC The document outlines essential techniques for conducting effective requirements analysis and documentation for SharePoint projects, particularly in waterfall methodologies. It emphasizes the importance of clear business versus technical requirements, the cost implications of changes in project scope, and provides guidelines for creating user stories, mockups, and workflow diagrams. Additionally, it highlights the need for thorough documentation of both in-scope and out-of-scope requirements, as well as non-functional requirements to ensure project success.
How to Best Develop Requirements for SharePoint Projects
How to Best Develop Requirements for SharePoint ProjectsDux Raymond Sy The document discusses best practices for developing requirements for SharePoint projects. It emphasizes eliciting requirements through discussions with stakeholders to understand their needs rather than just gathering facts. It also stresses the importance of analyzing requirements to clarify them and ensure the proposed solution will meet the goals, rather than getting paralyzed by over-analysis. Requirements should then be documented in writing for validation.
Practical Tools and Techniques for the SharePoint Business Analyst and ShareP...
Practical Tools and Techniques for the SharePoint Business Analyst and ShareP...Richard Harbridge The document appears to be notes from a presentation or workshop about information architecture and SharePoint. Some of the key points covered include:
- The difficulties of SharePoint BA/IA work and how SharePoint has grown very large and complex over time.
- The importance of identifying objectives and priorities for SharePoint projects using techniques like paired comparison matrices.
- An iterative approach to SharePoint projects is recommended to allow for adjustments over time.
- Visualization tools for communicating IA concepts like mind mapping and card sorting exercises are discussed.
Gathering user requirements for SharePoint projects can be fun
Gathering user requirements for SharePoint projects can be funAlan Marshall The document discusses the use of innovation games in gathering requirements for SharePoint projects, emphasizing the benefits of these games over traditional methods like questionnaires. It outlines various games such as 'Desert Island,' 'Show and Tell,' and 'Prune the Tree,' highlighting how they facilitate collaboration and uncover user needs. The document concludes by advocating for the use of these engaging techniques to identify new ideas and effectively gather requirements.
Business requirements gathering and analysis
Business requirements gathering and analysisMena M. Eissa This document outlines a workshop led by Mena Mostafa on business requirements gathering and analysis, emphasizing its importance in project management for software development. It covers techniques, challenges, and roles associated with business analysts, along with the relationship between business and functional requirements. The workshop aims to provide participants with practical insights and tools for successful requirements management to ensure project success.
6 basic steps of software development process
6 basic steps of software development processRiant Soft The document outlines the six basic stages of the software development life cycle: 1) Requirement gathering and analysis, 2) System analysis, 3) System design, 4) Coding, 5) Testing, and 6) Implementation. It describes each stage in the process, from gathering requirements from stakeholders to implementing the final tested software. An effective software development life cycle ensures quality and correctness through rigorous testing and design at each stage of building the software.
Forms and Workflow: Putting the Right Work in the Right Place presented by Mi...
Forms and Workflow: Putting the Right Work in the Right Place presented by Mi...European SharePoint Conference Mike FitzMaurice discusses the importance of forms and workflows in application development, emphasizing that the form is merely the user interface, not the workflow or data management itself. He highlights issues with form-only applications, such as hidden and disconnected logic, and advocates for more efficient workflows that can handle tasks with greater audibility and simplicity. The presentation concludes by stating that effective workflow management can improve data handling and communication across various formats.
How to Develop Quality Requirements for SharePoint Projects #ILTA13
How to Develop Quality Requirements for SharePoint Projects #ILTA13Dux Raymond Sy The document discusses developing quality requirements for SharePoint projects. It outlines a 4 step iterative process: 1) elicit requirements by determining what information is needed and where to find it, 2) map requirements to business, user, and system levels, 3) make sense of requirements by profiling users, modeling stated requirements, and identifying real requirements, and 4) confirm and prioritize requirements before generating a requirements document. The goals are to build solutions based on business needs and increase productivity.
SharePoint 2013 – Building a Project Management solution in six steps - Geoff...
SharePoint 2013 – Building a Project Management solution in six steps - Geoff...SPC Adriatics Geoff hosts a great session was in a SharePoint look at Project Management tools at Information Worker level. By doing this, a Project Management solution could be created whereby solving collaboration and information challenges. This session will describe how project team efforts and project information can be centralised and managed using SharePoint 2013 using built in features only, and without the immediate requirement of Microsoft Project 2013, in order to help solve Delivery Manager issues concerning planning progress, reporting progress and auditing progress. You will take away great action points in proving how versatile SharePoint is in delivering using built in features how SharePoint can provision a Project Management solution.
The full demo is available on this link:
http://www.sharepointgeoff.com/sharepoint-2013-building-a-project-management-solution-using-built-in-features-session/
Best Practices in Developing Requirements for SharePoint Projects
Best Practices in Developing Requirements for SharePoint ProjectsDux Raymond Sy The document discusses best practices for developing requirements for SharePoint projects. It emphasizes the importance of having a well-defined business case to guide requirements gathering. The key components of requirements gathering are elicitation, analysis, validation, and documentation. Requirements traceability is also important to define return on investment for SharePoint projects.
Being agile with SharePoint
Being agile with SharePointEndUserSharePoint The document discusses agile software development using SharePoint, highlighting the importance of customer engagement and team commitment. It outlines a case study involving the Fédération des médecins omnipraticiens du Québec, detailing project specifications and the Scrum process through various sprints. Key challenges include unit testing and the need for management buy-in, underscoring when agile methodologies are effective or not.
Business Analyst Interview cheat sheets
Business Analyst Interview cheat sheetsMohamed Elgendy Chapter 5 of the interview cheat sheets discusses business process modeling. It highlights essential techniques and methodologies used by 3D business analysts to effectively analyze and improve business processes. The chapter serves as a resource for preparing for interviews in the field.
Microsoft SharePoint im Projektmanagement
Microsoft SharePoint im Projektmanagementinnocate solutions GmbH Das Dokument beschreibt die Funktionen und Anwendungen von SharePoint 2010 im Projektmanagement, einschließlich Dokumentenverwaltung, Listenverwaltung und Kommunikation. Es betont die Vorteile von SharePoint, wie die Erstellung komplexer Anwendungen ohne Administrationszugriff, die Optimierung der Suche und die Möglichkeit zur formellen und informellen Zusammenarbeit. Zudem werden die Vor- und Nachteile der Hosting-Optionen innerhalb des Unternehmens und online diskutiert.
Cloud ERP vs. On-Premise ERP: Dissecting the Controversy
Cloud ERP vs. On-Premise ERP: Dissecting the ControversyIES The document explores the ongoing debate between cloud-based ERP and on-premise ERP systems, highlighting the benefits and drawbacks of each. Cloud ERP offers flexibility, lower upfront costs, and automatic updates, while on-premise ERP provides greater customization and control but requires significant maintenance and higher initial investment. As businesses increasingly seek efficiency, many are considering hybrid models that combine both systems to capitalize on their respective advantages.
ERP - Improve organization efficiency
ERP - Improve organization efficiencyabhiprad The document discusses enterprise resource planning (ERP) systems and SAP, a popular ERP software. It notes that companies often have many disconnected software systems for different departments that make sharing information difficult. An ERP system integrates these systems to provide a single source of information. SAP is highlighted as the most widely used global ERP due to its comprehensive functionality, scalability, and proven track record of successful implementations. However, the document cautions that SAP projects can fail due to issues like improper implementation strategy, change management problems, or inadequate resources and expertise.
Automating Business Processes with SharePoint
Automating Business Processes with SharePointGus Fraser The document presents a presentation on automating business processes, highlighting key topics such as SharePoint 2010 and 2013 workflows, Nintex for workflow creation, and integration with Microsoft CRM. It outlines the benefits of automation including cost reduction and improved efficiency, along with examples of simple and complex workflows. The document concludes with a discussion of case studies demonstrating the application of these automation tools in real-world scenarios.
Forms and Workflow: Putting the Right Work in the Right Place presented by Mi...
Forms and Workflow: Putting the Right Work in the Right Place presented by Mi...European SharePoint Conference
Ad
Similar to Best Practices in Gathering Requirements for SharePoint Projects (20)
Best Practices in Gathering Requirements for SharePoint Projects
Best Practices in Gathering Requirements for SharePoint ProjectsDux Raymond Sy The presentation discusses best practices for gathering requirements in SharePoint projects, emphasizing the importance of a well-defined business case and requirements traceability for ensuring return on investment. Key components of the requirements gathering process include elicitation, analysis, validation, and documentation. Attendees will learn how to differentiate between requirements and informal statements while understanding the structured approach to capturing user and system needs.
How To Best Develop SharePoint Requirements #SPSNOLA
How To Best Develop SharePoint Requirements #SPSNOLADux Raymond Sy The document provides an overview of best practices for developing requirements for SharePoint projects. It discusses the importance of having a well-defined business case to guide requirements gathering. The key steps in requirements development are requirements elicitation, analysis, validation, and documentation. Elicitation involves gathering information from stakeholders, analysis makes sense of that information, validation allows users to confirm requirements, and documentation formally communicates the requirements in a requirements document. The document emphasizes that requirements should be written as clear, measurable statements to facilitate the project.
How to Best Develop Requirements for SharePoint Projects @ #SPSATL
How to Best Develop Requirements for SharePoint Projects @ #SPSATLDux Raymond Sy The document provides guidance on developing requirements for SharePoint projects. It discusses the importance of having a well-defined business case to guide requirements gathering. The key aspects of gathering requirements are elicitation, analysis, validation, and documentation. Elicitation involves researching user needs, while analysis makes sense of the information. Validation allows users to confirm and prioritize real requirements. The final requirements document formally communicates overall characteristics and functionality. Writing clear, measurable requirement statements is also covered.
SPTechCon Best Practices in Gathering Requirements for SharePoint Projects
SPTechCon Best Practices in Gathering Requirements for SharePoint ProjectsDux Raymond Sy This document discusses best practices for gathering requirements for SharePoint projects. It outlines the key components of the requirements gathering process, including eliciting requirements, analyzing requirements, validating requirements, and documenting requirements in a formal requirements document. Emphasis is placed on writing clear requirement statements and producing traceability between requirements and project deliverables to help define ROI.
How to Best Develop Requirements for SharePoint Projects
How to Best Develop Requirements for SharePoint ProjectsDux Raymond Sy The document discusses how to best develop requirements for SharePoint projects. It explains that requirements define the business needs and that elicitation, analysis, validation, and documentation are key parts of the requirements development process. Requirements should be mapped to use cases and written clearly in a requirements document to guide the project.
How to Best Gather Requirements for SharePoint Projects
How to Best Gather Requirements for SharePoint ProjectsDux Raymond Sy The document outlines best practices for gathering requirements for SharePoint projects. It discusses defining clear business needs to initiate the requirements gathering process. The key steps in requirements development include elicitation, analysis, validation, and documentation. Elicitation involves researching and talking to stakeholders to understand needs, while analysis makes sense of the gathered information. Validation allows users to confirm and prioritize real requirements. Finally, documenting requirements formally communicates the desired characteristics and functionality of the project.
How to Best Develop Requirements for SharePoint Projects
How to Best Develop Requirements for SharePoint Projects Dux Raymond Sy The document discusses best practices for developing requirements for SharePoint projects. It explains that requirements involve eliciting information from stakeholders, analyzing this information without becoming paralyzed, and documenting requirements in a formal requirements document. The document provides tips for mapping requirements, validating requirements, and writing concise requirement statements to guide project development.
How to Best Develop Requirements for SharePoint Projects
How to Best Develop Requirements for SharePoint ProjectsDux Raymond Sy This document discusses how to best develop requirements for SharePoint projects. It provides an example of defining business needs by describing a scenario in finance of consolidating Excel files into a single management report. It also shows how to map business, user, and system requirements and describes the iterative process of requirements development which includes elicitation, analysis, validation, and documentation. The document aims to help people better understand and tackle challenges with requirements for SharePoint projects.
How to Best Develop Requirements for SharePoint Projects
How to Best Develop Requirements for SharePoint ProjectsDux Raymond Sy The document discusses best practices for developing requirements for SharePoint projects. It explains that requirements involve eliciting stakeholder needs, analyzing them, and documenting them in a requirements specification. The key aspects covered include defining the business need, eliciting requirements through interviews rather than just gathering wishes, analyzing requirements without getting paralyzed, validating requirements, and writing requirements clearly and objectively.
How to Best Manage SharePoint Projects @ SUGDC
How to Best Manage SharePoint Projects @ SUGDCDux Raymond Sy This document outlines the key steps to effectively plan, execute, and control SharePoint projects. It discusses establishing success criteria through collaborative requirements gathering. It emphasizes developing a relevant project plan by defining objectives, work breakdown structure, schedule, and staffing. Finally, it covers tracking progress through monitoring, analyzing status, correcting schedules, and managing changes. The presenter advocates establishing rules of engagement, educating business stakeholders, prioritizing features, and properly defining deliverables for SharePoint project success.
How to Best Develop Requirements for SharePoint Projects
How to Best Develop Requirements for SharePoint ProjectsDux Raymond Sy The document discusses best practices for developing requirements for SharePoint projects. It explains that requirements involve eliciting user needs through interviews rather than just gathering information. Requirements analysis maps user needs to technical requirements without getting paralyzed. The development process involves writing requirements in a document, validating them, and mapping them to solutions. The goal is to build the right solutions by clearly defining business needs and user requirements.
requirement gathering
requirement gatheringSaeedMat The document provides an overview of the requirements gathering process in business analytics, highlighting its importance in defining project goals, increasing client satisfaction, and preventing issues like scope creep. It details the stages involved, including stakeholder identification, requirement elicitation, documentation, and prioritization, using various techniques such as interviews, surveys, and workshops. Key takeaways emphasize the need for clear communication and proper documentation to ensure project success and meet client expectations.
Business Requirements development
Business Requirements development Mark Opanasiuk The document outlines the development of business requirements, detailing classifications, development stages, and the importance of a Business Requirements Document (BRD). It emphasizes understanding stakeholder needs, the distinction between business and functional requirements, as well as effective elicitation techniques to minimize errors in requirement gathering. Key challenges, best practices, and common faults are also discussed to ensure successful project outcomes.
LavaCon 15- Shifting the Paradigm of Requirements Gathering.pptx
LavaCon 15- Shifting the Paradigm of Requirements Gathering.pptxMichelle Caldwell, PSM, SSGB This document describes a class on shifting the paradigm of requirements gathering. The class teaches using collaborative play to build better solution requirements through fun and innovative activities. Attendees will learn how to introduce new concepts for creating a clear vision, facilitate more effective requirements sessions, identify common problems, and use new templates and techniques like the "rainbow method" to refine requirements. The class is led by Michelle Caldwell, a SharePoint expert with over 16 years of experience delivering business solutions.
How to Effectively Manage SharePoint Projects
How to Effectively Manage SharePoint ProjectsDux Raymond Sy The document outlines a presentation on effectively managing SharePoint projects. It discusses establishing success criteria, defining objectives, identifying requirements, developing a relevant project plan, and executing and controlling the project. The presentation encourages attendees to focus on planning and managing expectations, not just the technology. It provides contact information for the presenter, Dux Raymond Sy, for any additional questions.
Requirements management by Dr Matthew Bell
Requirements management by Dr Matthew BellAssociation for Project Management The document discusses requirements management and provides guidance on defining requirements effectively. It covers determining stakeholders and scope, structuring requirements hierarchically, ensuring requirements are unambiguous and verifiable. Principles of requirements management include engaging stakeholders, capturing needs not solutions, and using requirements to set expectations and acceptance criteria. Effective requirements management is presented as key to developing the right solution and managing projects successfully.
SharePoint as an Enterprise Platform
SharePoint as an Enterprise PlatformDux Raymond Sy The presentation by Dux Raymond Sy covers essential components for successfully implementing SharePoint as an enterprise platform, emphasizing the importance of executive buy-in, organizational readiness, and iterative solution releases. It outlines strategies for engaging businesses, addressing pain points, and prioritizing deployment efforts. The session aims to raise awareness about SharePoint's value and provides a roadmap for effective implementation.
Requirements Management
Requirements ManagementMohamed Mobarak The document discusses requirements management (RM) best practices. It describes the goals of RM as eliciting stakeholder needs to develop clear requirements and administrating requirements tracking. It then outlines the key stages of RM - planning, elicitation, analysis, development, validation, acceptance, and administration. For each stage, it describes objectives, entry/exit criteria, activities, and techniques used. It emphasizes the importance of RM for reducing costs and defects.
The Requirements - An Initial Overview
The Requirements - An Initial OverviewKumail Raza The document outlines the essential aspects of requirements gathering in business analysis, detailing types of requirements including business, user, and system requirements. It emphasizes the challenges of eliciting requirements from stakeholders and highlights various techniques such as interviews, workshops, and observations used for effective communication. Additionally, it covers the importance of requirements management, prioritization, and the need to clarify terminology within project teams to prevent misunderstandings.
SharePoint Saturday UK 2012 - Have pride in your SharePoint business requirem...
SharePoint Saturday UK 2012 - Have pride in your SharePoint business requirem...Antony Clay The document discusses challenges faced in SharePoint projects, particularly focusing on the inadequacy of gathering and understanding stakeholder requirements. It highlights common project failure factors, such as lack of user input and unclear objectives, while emphasizing the need for effective communication and collaboration among stakeholders. Practical takeaways are suggested to improve project success and stakeholder satisfaction.
Ad
More from Dux Raymond Sy (20)
Geek to Chic: Build Your Brand & Elevate Your Career in 5 Steps
Geek to Chic: Build Your Brand & Elevate Your Career in 5 StepsDux Raymond Sy The document outlines five key steps to building a personal brand and advancing one's career, emphasizing authenticity, audience awareness, and consistent value delivery. It encourages networking and engaging with peers while also highlighting the importance of empathy and understanding individual experiences. The content is geared towards personal growth and effective communication in professional settings.
Trailblazing through your own purpose-driven career
Trailblazing through your own purpose-driven careerDux Raymond Sy The document outlines steps to cultivate a purpose-driven career, emphasizing the importance of personal values and community connections. It encourages individuals to identify their passions, fill gaps in their skills, and document their journey. Key suggestions include creating a personal plan, being proactive, and actively engaging in both online and offline environments.
Practicing Kindness in Tech: 5 Steps to Build a Culture of Giving Back and He...
Practicing Kindness in Tech: 5 Steps to Build a Culture of Giving Back and He...Dux Raymond Sy The document outlines five steps to foster a culture of kindness in the tech community, emphasizing the benefits of being kind and the importance of community involvement. It encourages individuals to volunteer their expertise, engage their companies, and promote kindness while being inclusive and authentic. Key concepts include identifying organizational values, showcasing impacts, and leveraging personal stories to inspire others.
From Geek to Chic: Build Your Brand & Elevate Your Career in 5 Steps
From Geek to Chic: Build Your Brand & Elevate Your Career in 5 StepsDux Raymond Sy This document outlines a 5-step process for building a personal brand and elevating one's career: 1) Focus on strengths and be authentic. 2) Understand your target audience. 3) Provide consistent and valuable content on social media and at events. 4) Expand your network by engaging with industry peers. 5) Connect with others in a empathetic way by finding common ground. The overall message is that developing an authentic and meaningful personal brand takes focused effort but can help one stand out and advance their career.
#HumansofIT with Tech Superpowers: How Heathrow's Security Officer Launched 1...
#HumansofIT with Tech Superpowers: How Heathrow's Security Officer Launched 1...Dux Raymond Sy The document discusses Heathrow's security officer who successfully launched 12 PowerApps, highlighting the power of Microsoft’s low-code platform for both citizen and professional developers. It emphasizes the integration of services like Power BI, Power Automate, and AI Builder to enhance app development and streamline processes. Additionally, it promotes the Humans of IT community, encouraging developers to harness technology for personal and professional growth.
How to Get Your Organizations To Start Using Microsoft Teams
How to Get Your Organizations To Start Using Microsoft TeamsDux Raymond Sy The document outlines a case for change regarding the adoption of Microsoft Teams, emphasizing the need for sustainable behavior change in collaboration. It details six effective adoption strategies, which include establishing a framework, ensuring operational governance, demonstrating quick wins, and delivering continuous learning. Resources and examples to support these strategies are also provided, aiming to enhance user experience and business outcomes.
Work-Life Integration: 7 Effective Ways to Achieve Healthy Balance
Work-Life Integration: 7 Effective Ways to Achieve Healthy BalanceDux Raymond Sy Work-life integration is a concept that emphasizes the synergy between various life domains such as work, family, and personal well-being. It encourages authenticity, integrity, and creativity to enhance productivity and reduce distractions. By prioritizing tasks and setting deadlines, individuals can create more value during the workday.
Public Speaking Excellence: How to be a #RockstarPresenter in 5 Steps
Public Speaking Excellence: How to be a #RockstarPresenter in 5 StepsDux Raymond Sy This document provides tips for effective public speaking. It discusses the roles of a presenter as persuading, motivating, and informing audiences. It then outlines a 5-step process for being a rockstar presenter, including developing a catchy abstract, using repetition to reinforce learning, conducting dry runs, minimizing speech issues, and summarizing with a call to action. Presentation content should stick to what's important and use visual highlights and repetition to aid retention.
How to be a #RockstarPresenter in 5 Steps
How to be a #RockstarPresenter in 5 StepsDux Raymond Sy This document provides a 5-step guide to being a rockstar presenter. The steps include developing a catchy abstract, understanding your role as presenter which can include coach, host, learning manager or company representative, using formulas to describe content, using analogies and examples to aid retention, including learning activities like questions and demos, and summarizing while providing a call to action and evaluation. The presentation aims to provide insiders views and best practices from successful CRM partners to help experienced CRM partners improve their sales efforts.
5 Steps to Build an FAQ Knowledge base with SharePoint Communication Sites
5 Steps to Build an FAQ Knowledge base with SharePoint Communication SitesDux Raymond Sy This document discusses how to create a knowledge base using a communication site in SharePoint. It recommends following 5 steps: 1) define success criteria for the knowledge base, 2) establish a framework, 3) identify relevant components to include like documents, blogs and videos, 4) create and populate the site with organized content, and 5) drive sustainable adoption by keeping content consistent and sharing the site. The goal is to build a self-service library of information that can be efficiently delivered and maintained by multiple contributors.
Accelerate Your #ModernWorkplace Success with #Microsoft365
Accelerate Your #ModernWorkplace Success with #Microsoft365 Dux Raymond Sy 1) The document discusses how Microsoft 365 can accelerate modern workplace success by providing a complete, intelligent solution to empower employees to work creatively and securely together.
2) It highlights key capabilities of Microsoft 365 like Office 365, Windows 10, Enterprise Mobility + Security, and how Teams acts as a hub to facilitate team collaboration across the Office apps, services, and Microsoft Graph.
3) The document provides guidance on using the different Microsoft 365 tools effectively based on factors like audience, time sensitivity, and collaboration needs.
#MSTechSummit Frankfurt: Collaborate using #MicrosoftTeams, the hub for teamw...
#MSTechSummit Frankfurt: Collaborate using #MicrosoftTeams, the hub for teamw...Dux Raymond Sy The document discusses the evolving digital workplace trends influenced by generational preferences, highlighting tools like Office 365 that enhance collaboration. It outlines features of Office 365 groups, including security and integrated experiences for effective teamwork, as well as the roles of various applications like Teams and SharePoint. Additionally, it provides insights on using Microsoft Teams for project management and enhancing communication through guest access and multiple integrations.
Overview of SharePoint Server 2016 and Office 365 Hybrid Scenarios
Overview of SharePoint Server 2016 and Office 365 Hybrid ScenariosDux Raymond Sy The document outlines strategies for compliance and security in data management, specifically regarding SharePoint and Office 365. It emphasizes the importance of a data governance framework, risk assessment, and a structured approach to migrating content while ensuring compliance. Additionally, it refers to various resources and sessions for further learning on managing SharePoint migration projects.
Accelerate CItizen Engagement @ the Speed of Now
Accelerate CItizen Engagement @ the Speed of NowDux Raymond Sy The document discusses the challenges government entities face today, including cybersecurity, citizen engagement, and collaboration across sectors. It emphasizes the importance of responsiveness to citizens, utilizing real-time data insights, and empowering citizens through mobile apps for reporting and service requests. Strategies for improving service delivery and accountability are highlighted, alongside the need for transparency and effective communication with the public.
Hybrid SharePoint: Ask the Experts
Hybrid SharePoint: Ask the ExpertsDux Raymond Sy The document discusses research findings on the hybrid SharePoint market, focusing on customer preferences for hybrid solutions over full cloud migration. It highlights the challenges organizations face in transitioning to the cloud, such as security, customization difficulties, and the technical implications of maintaining a hybrid environment. The document also outlines recommendations for Microsoft and users, emphasizing the importance of strategic partnerships and optimizing hybrid solutions for better user engagement and management.
Microsoft Teams is Here!
Microsoft Teams is Here!Dux Raymond Sy The document outlines a webinar introducing Microsoft Teams, emphasizing the role of modern collaboration styles and technologies across generational preferences in the workforce. Experts discuss various communication methods tailored to audience size, tone, and urgency, alongside showcasing the features of Microsoft Teams as a collaboration platform. It also addresses questions from the community regarding future developments and best practices for using Teams effectively.
Understanding Office 365 Groups: Ask The Experts
Understanding Office 365 Groups: Ask The ExpertsDux Raymond Sy This document outlines a webinar focused on Office 365 Groups, featuring experts from AvePoint, Hyperfish, and Microsoft. It discusses the collaborative capabilities of Office 365, emphasizing security, compliance, and the integration of various tools for effective teamwork across distributed environments. Additionally, it highlights challenges faced by users and offers resources for best practices and management of Office 365 Groups.
Webinar: Microsoft Teams is Here! Presented by Avanade, AvePoint and Microsoft.
Webinar: Microsoft Teams is Here! Presented by Avanade, AvePoint and Microsoft.Dux Raymond Sy The document outlines a webinar focused on Microsoft Teams, emphasizing its role as a chat-based workspace within Office 365. It discusses the platform's features, collaboration capabilities, generational preferences in communication styles, and the importance of security and compliance. The webinar also highlights Avanade's experience with Microsoft Teams, providing insights into effective collaboration practices across various organizational cultures.
Drive Business Value with Winning Data Governance and Compliance Strategies
Drive Business Value with Winning Data Governance and Compliance StrategiesDux Raymond Sy The document outlines strategies for effective data governance and compliance, emphasizing the importance of identifying and addressing data challenges. It discusses the utilization of a proper data governance framework to manage various types of data, including sensitive or regulated information, while ensuring accountability and security. The content also highlights the necessity of establishing clear policies, ownership, and classification for data management within organizations.
5 time-saving techniques that can elevate your social media engagement #wpc15
5 time-saving techniques that can elevate your social media engagement #wpc15Dux Raymond Sy This document provides tips for businesses to maximize their return on investment from social media marketing. It recommends identifying goals like engagement, brand building or sales. It then suggests leveraging management tools to schedule relevant posts at appropriate times and maximize sharing through mobile apps, photos and videos. Finally, it lists some popular social media management tools and encourages connecting on social media.
Recently uploaded (20)
AI vs Human Writing: Can You Tell the Difference?
AI vs Human Writing: Can You Tell the Difference?Shashi Sathyanarayana, Ph.D This slide illustrates a side-by-side comparison between human-written, AI-written, and ambiguous content. It highlights subtle cues that help readers assess authenticity, raising essential questions about the future of communication, trust, and thought leadership in the age of generative AI.
Quantum AI: Where Impossible Becomes Probable
Quantum AI: Where Impossible Becomes ProbableSaikat Basu Imagine combining the "brains" of Artificial Intelligence (AI) with the "super muscles" of Quantum Computing. That's Quantum AI!
It's a new field that uses the mind-bending rules of quantum physics to make AI even more powerful.
Using the SQLExecutor for Data Quality Management: aka One man's love for the...
Using the SQLExecutor for Data Quality Management: aka One man's love for the...Safe Software The SQLExecutor is one of FME’s most powerful and flexible transformers. Pivvot maintains a robust internal metadata hierarchy used to support ingestion and curation of thousands of external data sources that must be managed for quality before entering our platform. By using the SQLExecutor, Pivvot can efficiently detect problems and perform analysis before data is extracted from our staging environment, removing the need for rollbacks or cycles waisted on a failed job. This presentation will walk through three distinct examples of how Pivvot uses the SQLExecutor to engage its metadata hierarchy and integrate with its Data Quality Management workflows efficiently and within the source postgres database. Spatial Validation –Validating spatial prerequisites before entering a production environment. Reference Data Validation - Dynamically validate domain-ed columns across any table and multiple columns per table. Practical De-duplication - Removing identical or near-identical well point locations from two distinct source datasets in the same table.
GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now.pdf
GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now.pdfPriyanka Aash GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now
cnc-processing-centers-centateq-p-110-en.pdf
cnc-processing-centers-centateq-p-110-en.pdfAmirStern2 מרכז עיבודים תעשייתי בעל 3/4/5 צירים, עד 22 החלפות כלים עם כל אפשרויות העיבוד הדרושות. בעל שטח עבודה גדול ומחשב נוח וקל להפעלה בשפה העברית/רוסית/אנגלית/ספרדית/ערבית ועוד..
מסוגל לבצע פעולות עיבוד שונות המתאימות לענפים שונים: קידוח אנכי, אופקי, ניסור, וכרסום אנכי.
OWASP Barcelona 2025 Threat Model Library
OWASP Barcelona 2025 Threat Model LibraryPetraVukmirovic Threat Model Library Launch at OWASP Barcelona 2025
https://owasp.org/www-project-threat-model-library/
Salesforce Summer '25 Release Frenchgathering.pptx.pdf
Salesforce Summer '25 Release Frenchgathering.pptx.pdfyosra Saidani Salesforce Summer '25 Release Frenchgathering.pptx.pdf
Quantum AI Discoveries: Fractal Patterns Consciousness and Cyclical Universes
Quantum AI Discoveries: Fractal Patterns Consciousness and Cyclical UniversesSaikat Basu Embark on a cosmic journey exploring the intersection of quantum
computing, consciousness, and ancient wisdom. Together we'll uncover the
recursive patterns that bind our reality.
Lessons Learned from Developing Secure AI Workflows.pdf
Lessons Learned from Developing Secure AI Workflows.pdfPriyanka Aash Lessons Learned from Developing Secure AI Workflows
UserCon Belgium: Honey, VMware increased my bill
UserCon Belgium: Honey, VMware increased my billstijn40 VMware’s pricing changes have forced organizations to rethink their datacenter cost management strategies. While FinOps is commonly associated with cloud environments, the FinOps Foundation has recently expanded its framework to include Scopes—and Datacenter is now officially part of the equation. In this session, we’ll map the FinOps Framework to a VMware-based datacenter, focusing on cost visibility, optimization, and automation. You’ll learn how to track costs more effectively, rightsize workloads, optimize licensing, and drive efficiency—all without migrating to the cloud. We’ll also explore how to align IT teams, finance, and leadership around cost-aware decision-making for on-prem environments. If your VMware bill keeps increasing and you need a new approach to cost management, this session is for you!
Connecting Data and Intelligence: The Role of FME in Machine Learning
Connecting Data and Intelligence: The Role of FME in Machine LearningSafe Software In this presentation, we want to explore powerful data integration and preparation for Machine Learning. FME is known for its ability to manipulate and transform geospatial data, connecting diverse data sources into efficient and automated workflows. By integrating FME with Machine Learning techniques, it is possible to transform raw data into valuable insights faster and more accurately, enabling intelligent analysis and data-driven decision making.
Raman Bhaumik - Passionate Tech Enthusiast
Raman Bhaumik - Passionate Tech EnthusiastRaman Bhaumik A Junior Software Developer with a flair for innovation, Raman Bhaumik excels in delivering scalable web solutions. With three years of experience and a solid foundation in Java, Python, JavaScript, and SQL, she has streamlined task tracking by 20% and improved application stability.
"Scaling in space and time with Temporal", Andriy Lupa.pdf
"Scaling in space and time with Temporal", Andriy Lupa.pdfFwdays Design patterns like Event Sourcing and Event Streaming have long become standards for building real-time analytics systems. However, when the system load becomes nonlinear with fast and often unpredictable spikes, it's crucial to respond quickly in order not to lose real-time operating itself.
In this talk, I’ll share my experience implementing and using a tool like Temporal.io. We'll explore the evolution of our system for maintaining real-time report generation and discuss how we use Temporal both for short-lived pipelines and long-running background tasks.
Coordinated Disclosure for ML - What's Different and What's the Same.pdf
Coordinated Disclosure for ML - What's Different and What's the Same.pdfPriyanka Aash Coordinated Disclosure for ML - What's Different and What's the Same
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdf
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdfPriyanka Aash Oh, the Possibilities - Balancing Innovation and Risk with Generative AI
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...Josef Weingand IBM LTO10
EIS-Webinar-Engineering-Retail-Infrastructure-06-16-2025.pdf
EIS-Webinar-Engineering-Retail-Infrastructure-06-16-2025.pdfEarley Information Science As AI reshapes expectations in retail and B2B commerce, organizations are recognizing a critical reality: meaningful AI outcomes depend on well-structured, adaptable infrastructure. In this session, Seth Earley is joined by Phil Ryan - AI strategist, search technologist, and founder of Glass Leopard Technologies - for a candid conversation on what it truly means to engineer systems for scale, agility, and intelligence.
Phil draws on more than two decades of experience leading search and AI initiatives for enterprise organizations. Together, he and Seth explore the challenges businesses face when legacy architectures limit personalization, agility, and real-time decisioning - and what needs to change to support agentic technologies and next-best-action capabilities.
Key themes from the webinar include:
Composability as a prerequisite for AI - Why modular, loosely coupled systems are essential for adapting to rapid innovation and evolving business needs
Search and relevance as foundational to AI - How techniques honed-in enterprise search have laid the groundwork for more responsive and intelligent customer experiences
From MDM and CDP to agentic systems - How data platforms are evolving to support richer customer context and dynamic orchestration
Engineering for business alignment - Why successful AI programs require architectural decisions grounded in measurable outcomes
The conversation is practical and forward-looking, connecting deep technical understanding with real-world business needs. Whether you’re modernizing your commerce stack or exploring how AI can enhance product discovery, personalization, or customer journeys, this session provides a clear-eyed view of the capabilities, constraints, and priorities that matter most.
PyCon SG 25 - Firecracker Made Easy with Python.pdf
PyCon SG 25 - Firecracker Made Easy with Python.pdfMuhammad Yuga Nugraha Explore the ease of managing Firecracker microVM with the firecracker-python. In this session, I will introduce the basics of Firecracker microVM and demonstrate how this custom SDK facilitates microVM operations easily. We will delve into the design and development process behind the SDK, providing a behind-the-scenes look at its creation and features. While traditional Firecracker SDKs were primarily available in Go, this module brings a simplicity of Python to the table.
Best Practices in Gathering Requirements for SharePoint Projects
- 1. Best Practices in Gathering Requirements for SharePoint Projects Dux Raymond Sy, PMP UMBC Training Center June 18, 2009 7.00pm
- 2. What Does This Mean? 8 5 4 9 1 7 6 3 2 0
- 3. What Does This Mean? SharePoint
- 4. Presentation Objectives In this presentation, you will learn the best practices in gathering requirements for SharePoint Projects In addition, you will be able to identify: Why having a well defined business case is necessary to effectively initiate requirements gathering The key components of requirements gathering process Why requirements traceability is paramount in defining ROI in SharePoint projects
- 5. Dux Raymond Sy, PMP Managing Partner, Innovative-E, Inc. Author, “SharePoint for Project Management” by O’Reilly Media Contract Author & Instructor, Learning Tree International For more information, connect with Dux E-Mail: [email protected] LinkedIn: meetdux.com/li Blog: meetdux.com Twitter: twitter.com/meetdux
- 6. Agenda What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper Summary
- 7. Why are Requirements So Difficult?
- 8. Write the Requirements for
- 9. What is a Requirement? A requirement is something wanted or needed Formally documented and written statements Capabilities needed to solve a problem Conditions of a delivered system, services, product, or process Constraints on the system, service, product, or process Requirements are not Verbal, informal statements or conversations in the hallways Solutions that state how to solve the problem or meet the objectives Characteristics of other systems, services, products, or processes Project budgets, plans, or implementation details
- 10. What’s So Special About SharePoint?
- 12. Example: Defining SharePoint Requirements Business requirements SharePoint shall increase user productivity by 15 percent User requirements The user shall be able to retrieve search results within five seconds of submitting a search request System requirements SharePoint search shall support a maximum of 10,000 simultaneous search requests
- 13. Key Components of Requirements Gathering 1. Requirements Elicitation 2. Analyzing Requirements 3. Validating Requirements 4. Documenting Requirements
- 14. Agenda What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper Summary
- 15. How Many Squares Do You See?
- 16. What is Requirements Elicitation? Elicitation: gathering and understanding what stakeholders and users need Done at both an organizational (business) and a more detailed user level Elicitation is a human-based activity Determine requirements sources Decide how to gather information Involves research, reading, talking, and observing Business-level context and framework How the end users do their jobs What would help them do their jobs better Within the scope of our system, product, or process
- 17. Elicitation Process 1. What do I need to know? 2. Where do I get this information? 3. Get the information 4. Organize what you know 5. Do I have enough information?
- 18. Goal is to Build a SharePoint Solution How would you like to drive a Lamborghini Diablo? BTW, you just learned how to ride a bike yesterday
- 19. Agenda What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper Summary
- 20. What is Requirements Analysis? Requirements analysis takes elicited information and makes sense of it
- 21. Analysis Process 1. Profile Users 2. Model stated requirements 3. Gap analysis 4. Identify the real requirements
- 22. Example: Process Flow Diagram
- 23. Agenda What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper Summary
- 24. What is Requirements Validation? Requirements validation allows the user(s) to confirm and prioritize the real requirements Essential to identify what it will take to deploy SharePoint Resources Time Skillsets
- 25. Example: SharePoint Project Schedule
- 26. Agenda What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper Summary
- 27. Generate a Requirements Document Formally communicates Overall quantitative and qualitative characteristics Functionality of the desired end result or outcome Should include Requirement Statements Process Diagrams Traceability Matrix
- 28. What Makes a Great Requirement? Content + Structure = Readability
- 29. Writing Requirement Statements <Subject> shall be able to <capability> within <criterion> <Subject> shall be able to <capability> Where criterion is assumed to be 100 percent of the stated capability
- 30. Example: Defining SharePoint Requirements Business requirements SharePoint shall increase user productivity by 15 percent User requirements The user shall be able to retrieve search results within five seconds of submitting a search request System requirements SharePoint search shall support a maximum of 10,000 simultaneous search requests
- 31. Agenda What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper Summary
- 32. Questions? E-Mail: [email protected] LinkedIn: meetdux.com/li Blog: meetdux.com Twitter: twitter.com/meetdux
- 33. Summary You have learned the best practices in gathering requirements for SharePoint Projects In addition, you are able to identify: Why having a well defined business case is necessary to effectively initiate requirements gathering The key components of requirements gathering process Why requirements traceability is paramount in defining ROI in SharePoint projects
- 34. Thank You!