The document discusses using SharePoint to surface the right information to employees, improve collaboration and connectivity both within the workspace and remotely, and increase business performance by enabling informed decision making. It also references different business sizes that could utilize SharePoint, versions of SharePoint, and potential roles that might be involved in a SharePoint implementation including developers, end users, IT professionals, and project managers. The document poses questions to the audience and suggests SharePoint can help connect and empower users through seamless interfaces and concise office integration providing access to information from anywhere.

1. @rizinsights | #SPTechCon | #sptreqs

5. Surface Information Connect Teams Improve Performance
• Right information to right people • Increase employee connectedness • Increase business velocity
• Secure data management with and interactivity • Decrease business risk with
built-in controls • Workspace and mobile connectivity informed decisions
• Customizable dashboards • Collaboration • Reduce cost by using a single
platform

6. A. Small (50 employees)
B. Medium business (500 employees)
C. Large/Enterprise (more than 500
employees)
A. SharePoint 2003
B. SharePoint 2007
C. SharePoint 2010
D. SharePoint 2013

7. Developer End User IT Pro SharePoint Project
Analyst Manager
Other?

8. Requirements analysis in systems engineering
and software engineering, encompasses those
tasks that go into determining the needs or
conditions to meet for a new or altered
product, taking account of the possibly
conflicting requirements of the various
stakeholders, such as beneficiaries or users. It
is an early stage in the more general activity of
requirements engineering which encompasses
all activities concerned with eliciting,
analyzing, documenting, validating and
managing software or system requirements.
- Wikipedia

9. Requirements analysis in systems engineering
and software engineering, encompasses those
tasks that go into determining the needs or
conditions to meet for a new or altered
product, taking account of the possibly
conflicting requirements of the various
stakeholders, such as beneficiaries or users. It
is an early stage in the more general activity of
requirements engineering which encompasses
all activities concerned with eliciting,
analyzing, documenting, validating and
managing software or system requirements.
- Wikipedia

10. Requirements Gathering

13. How Many Triangles?

14. Who Knows Baseball?
A bat and a ball cost $1.10 in total. The bat costs $1 more than the ball.
How much does the ball cost?
x = cost of ball
cost of bat = x + 1
total cost = 1.10 = x + (x + 1) = 2x + 1
2x = 0.10
x = 0.05

15. Audience Participation

16. Draw This

19. The
Requirements
Madness

23. What? How? Who?
Why?
Where? When?
New
Mission Competencies
Capabilities
Business
Vision Strategies
Process
Project
Objectives Goals
Management

24. Remember this…

25. Things that are wanted or needed
Documented standards 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

26. Verbal, informal statements or conversations in
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

27. Remember the BUS

28. Remember the BUS
• Organizational Focus
Business • Business Needs
• Strategic Objectives
User
• Focused on the individual
• There’s no I in team
• But there is in Raise! System
• Hardware
• Operating System
• Software/Hardware Requirements

29. B
MUST
27%
U
S

30. Put on a Show

31. SharePoint High School
Tell them what
you’re going to say
SAY IT
Tell them what you said

32. What are they building?

33. Implementation
Components Definitive
Goals
This is our Strategy

36. How can I Connect and Empower
Seamless User
Interface
Concise Office
Integration
Access
Information
Anywhere

40. People Work
Finance Assets

50. Pretty Pictures

51. Don’t Be Fooled

52. Things are Happening

53. …Balance

54. Q&A

56. SharePoint Saturday – Philly, February 22
SPTechCon 2013 – San Francisco, March 3-6
SharePoint Fest – Denver, March 18-20
Document Strategy Forum – CT, April 30-May 2
SharePoint Summit – Toronto, May 12-15
SharePoint Saturday – Toronto, July 20
SharePoint Saturday – New York, July 27
SPTechCon 2013 – Boston, August 12-15