The motto of this presentation was "When the business says make it work". We looked at a real example of an organization, NTMA, that implemented SharePoint within a highly regulated environment, their business challenges and how having a proper ALM Process and Tools (TFS) helped.
(Genuine) Escort Service Lucknow | Starting ₹,5K To @25k with A/C 🧑🏽❤️🧑🏻 89...
SharePoint: Application Lifecycle Management
1. SharePoint: Application Lifecycle Management
Date 25th June 2014
Derek Finnerty, Gerry Moloney, Alex Ferreira
www.storm.ie
www.storm.ie
2. • Customer Story: NTMA
www.storm.ie
• Business Challenges
• Technical & Platform Challenges
• Solution Approach
• Learnings
• Application Lifecycle Management
• TFS, SharePoint and Managed Releases
• Using the tools
• Development Frameworks (Vortex)
• Code Quality Assurance
• Learnings
Agenda
Use of SharePoint in highly regulated environment
3. Business Challenges
• Business to manage own environment
• Integrate with their chosen 3rd party tools
• Scalable for large number sites/data
• Auditability
www.storm.ie
4. ALM Process
• Leverage the TFS Platform
• Iterative approach
• Progressive analysis, decomposition,
estimation and iteration planning
• Full end to end traceability
www.storm.ie
5. Platform Challenges
• Maintenance and Governance
• Configuration
• Soft and Hard limits of SharePoint
• Restrictions that 3rd party tools impose
www.storm.ie
6. Steps to resolution
• Utilising the right tools
• Development of a framework
• Code quality assurance
• Release Management
– Quality Gates
– Testing
www.storm.ie
7. Solution Approach
• “Governance Engine” to manage configuration
• Template based approach
• CRUD (Create, Read, Update, Deprecate)
• Migration
• Build Vs Buy
www.storm.ie
8. Focal Points
• Tailor the process to the organization
• Leverage the framework
• Master the tools
• Improve code quality assurance
www.storm.ie
9. www.storm.ie
Foundation
(Class Library)
• Base
•Upgrade Actions
• Extensions
Features
(WSPs)
• Server
• UI
•Apps
Automation
(PowerShell)
• Reusable scripts
• XML configuration
• Release module
10. Lessons Learned
• “There are known knowns. These are things
we know that we know. There are known
unknowns. That is to say, there are things that
we know we don't know. But there are also
unknown unknowns. There are things we don't
know we don't know.” – Donald Rumsfeld
www.storm.ie
11. Lessons Learned
• Standardisation
• Understand the SharePoint boundaries
– Utilisation & Creation of Document ID’s
• Trust the toolset (TFS)
• Follow the process
www.storm.ie
Editor's Notes
Derek Presents
Derek Presents
Gerry Presents
# Source Code / Manage Work using TFS Work Items
# Features -> Requirements -> Tasks // -> Test Cases -> Bugs
# Always in touch with the business goals! Technical tasks are not an end goal.
# TFS Work Item Queries / Check-Ins associated with Tasks
# Show the business as fast as possible (“fail early”) / TFS adoption same principle
Gerry Presents
# Tools: TFS (already mentioned) / Visual Studio 2013 / MS Test Manager
# Drilling deep into SharePoint: SharePoint Manager, ILSpy, ULS Viewer (verbose logs) + test, test, test…
# NTMA: Upgrade Actions / SharePoint OM Extensions / PowerShell scripts
# Goals: faster release cycles (asked by the business), i.e. more value, faster!
# Hot to get there: automated and repeatable deployments; stronger process managing a release; quality gates
# TFS Build Server / SPCAF / Tasks’ duration <= 4 hours
Gerry Presents
Framework: keep momentum, stay relevant, immediate gains
Release Management software: release path, automated tracking of progress, formal approvers & auditing
SPCAF: Relevance tuning exercise, Custom rule set
Storm: customers have similar challenges / repeating pattern of successful solutions / faster & more flexible implementation