Release notes for the SSF Handbook
Updated August 20, 2019
What's new with this update
- Overhauled change management best practices
- Change management best practices for a Splunk deployment contains an overview of the change management (CM) process that governs changes to your Splunk environments. It contains guidelines and examples to reference as you define the change management scope, process, pathways, and identify the Responsibility assignment matrix (RACI) for your organization. It also includes a template to download and use for planning.
April 10, 2019
- Renamed service areas to 'functional areas'
- Not all Splunk deployments are set up as services. The word functional means 'designed to be practical and useful,' which better describes the different categories of best practices.
- Renamed foundation best practices to 'fundamental best practices'
- Fundamental best practices address how you conduct your Splunk implementation. The word fundamental means 'forming a necessary base or core,' which better describes the value of these basic operational best practices.
- Renamed the good, better, best maturity levels to 'standard, intermediate, advanced'
- Maturity level is based on business objectives. Standard, intermediate, advanced keeps the focus on the level of effort to achieve the results best suited for the situation.
March 26, 2019
- Renamed Center of Excellence (CoE) to Splunk Success Framework
- Simplified the service area names
- Platform management and support is now platform
- Program management and value realization is now program
- Use case and data lifecycle is now data
- User and team lifecycle is now people
- Changed charter to purpose
- Removed legacy graphics
- Renamed in-depth articles "best practices"
Welcome to the Splunk Success Framework
About the SSF fundamental best practices
This documentation applies to the following versions of Splunk® Success Framework: ssf