The document outlines an agile approach to software development called Sentri Agile Development which emphasizes working solutions delivered in frequent small releases through iterative cycles, applies proven engineering practices, and aims to efficiently manage change while ensuring early success and customer satisfaction through rapid delivery of prioritized features. Key aspects include multi-disciplinary teams, visible increments to deployed solutions each sprint, and ongoing communication rather than heavy documentation.

1. Overview

2. Meet changing Manage IT costs
business needs and complexity
Drive insight from complexity Integrate line-of-business systems
Work with customers and partners Provide scale agility
Embrace Millennial work styles Enable innovation
Comply with regulations Protect intellectual property

3. Business Collaboration Platform

4. Rich User
Experience
Anywhere Access
Single Platform

6. Informal
Knowledge
Social
Connections
Participation
Anywhere

8. User-centric
Flexibility and
Compliance
Management
Efficiency

12. Local copy saved for
offline access
Synchronizing only Editing conflict
updated sections resolved by merge
(deltas) engine

13. Better Answers,
Faster
Knowledge
Amplification
Enterprise
Deployment

16. Data interaction
Decision Making
Organizational
Effectiveness

17. SharePoint Insights

18. SharePoint Insights

19. User-Driven
Solutions
Data
Connectivity
Solution
Deployment

21. My Artists
Artist Tracker > Artists
Contracts
Artist Name Address City State
Artist
Artist Name: Mandible
Deathrattle
Artists Concourse
Jay Hamlin Trio
Down on the Bayou
Andrew Datars Quartet
Agent:
Concourse
Stuck in the Mud
Jay Hamlin Trio
Tastes like chicken
Down on the Bayou
Mandible
Concourse

22. Scale with
Governance
Deployment
Flexibility
IT Productivity

24. •
•
•
−
−
−
−
•
•
•
•
•
•
−
−
• ©2009 Microsoft, Microsoft Dynamics, the Office logo, and Your potential. Our passion. are trademarks of the Microsoft group of companies. The information herein is for informational purposes only and
represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on
the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR
STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

25. Sentri applies an agile approach adapting the best features of SCRUM and Configuration to projects where early
success must be demonstrated yet requirements may not be fully known. The approach is lightweight and
manages development work through frequent and small releases. It emphasizes working solution as the
primary measure of progress.
The approach is founded on solid and proven software engineering best practices
• Test driven development, continuous integration, re-factoring, standards-based implementation, build on
object-oriented analysis and design and service oriented architectures.
Customer Benefits How Does Sentri Agile Development Work?
• Specifically designed to efficiently cope with • Small teams of highly skilled, multi-disciplined
change. Avoids high cost of change management Consultants.
and inflexible solutions in traditional approaches.
• A series of iterations (in the order of weeks not
Involves stakeholders in the evolution of the
months) where each sprint is a mini Configuration
solution.
Cycle.
• Customer satisfaction by rapid, continuous
• Visible, usable increments to deployed solution.
delivery of useful software.
• Value is placed on real-time and ongoing
• Focuses on producing prioritized, usable features.
communication as opposed to heavy weight
• Identifies and communicates problems early. documentation.
• Quality of resulting solution is greater than with • Usage of modern lightweight development tools to
traditional approaches. allow ‘quick’ change.
• Regimented opportunities for change
management to allow prioritization and focus on
delivery.

26. Functionality Intranet
Phase I II III
Collaboration
Real-Time Presence and Communication √
Social Networking Web Part √ √
Standard Site Templates √ √
Wikis √ √ √
Blogs √ √
People and Groups Lists √ √
Calendars √ √
Time Tracking √ √ √
Real-time Links and Technical Support (e.g. √ √
Live Link)
Email Integration √ √ √
SMS/MMS Integration √ √
Task Coordination and Project Activity √ √
Surveys √ √
DOA and P&L Collaboration √ √
Overview Dashboard √ √
Issue Tracking √ √ √

27. Functionality Intranet
Phase I II III
Portal
My Site Personal Site √ √
Content Syndication √
Privacy & Security √ √
Site Directory √ √
User Profiles and the Profile Store √ √
Audience Targeting √ √ √
Site Manager √
Mobile Device Support √ √
Portal Site Templates √
Portal Sites and Documents Roll-up Web Parts √ √ √
Colleagues and Memberships Web Parts √ √
Integration with MS OFFICE (Access, Excel, √ √ √
PowerPoint, and Word)
Integration with Outlook √ √ √
Demonstration Links √
Integration with Portal Designer Tools √ √

28. Functionality Intranet
Phase I II III
Search
User Interface √ √
Search Results √ √
Enterprise Content Sources √ √
Relevance √ √
Administration and Management √ √
Indexing Controls √ √
Security √ √ √
People Search √ √
Search & Replace √
Business Data Search √ √

29. Week X Week X Week X Week X Week X Week X
Project Implementation Implementation Implementation Production
Initiation, Planning Release 1 Release 2 Release 3 Release
Requirements Iteration1 Iteration 3 Iteration 6
Analysis Iteration 2 Iteration 4 Iteration 7
Iteration 5 Iteration 8
Requirements
Prioritization
Requirements Workshops
Audience / Users Needs Analysis
Initial iterations will be R2 iterations will be 3-3 R3 iterations will be 3-3
2-3 weeks in duration. ½ weeks in duration. ½ weeks in duration.
SharePoint Architecture It is important to
Fit / Gap analysis validate and get
feedback early and set
stage for adoption
Non-functional
success.
Requirements Analysis
Create Initial Update Initial Create near-production ready Create / Update
Infrastructure Infrastructure Infrastructure Production Infrastructure
• The project is organized in a series of releases focusing on delivering usable and prioritized
functionality incrementally through short iterative cycles
• Specific timeline and functionality will be created as part of project initiation and planning
• Project plan (timeline and functionality) for each iteration as well as release cycle will be
adjusted throughout, allowing user adoption and validation
Week X Week X Week X
QA QA QA
Phase I Phase II Phase III

30. •Schedule a detailed requirement analysis session/s
•Provide a high level understanding & a “Solution
approach document (includes business
goals/milestones, design, development, QA &
deployment process)”
•Provide a SOW based on our understanding,
effort estimation with pricing.