CMS Best Practices


CMS Best Practices - Rackcdn.comhttps://b6b45000d3362c7b69f8-0a7250d8bde19e2e09b93fa07c907bb0.ssl.cf5.rackcdn...

8 downloads 197 Views 723KB Size

CMS Best Practices Jody Roberts

• • • • • •

Agenda The Big Picture: Community CMS Best Practices Library Best Practice taxonomy Resources Feedback channels Q&A

Community

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

The Big Picture is the COMMUNITY To understand great best practices, understand your Community.

• Generates content, knowledge and best practices – Through discussion and interaction – Online Forums, Practitioner Forums

• • • •

Shares/Uses best practices Drives and improves product direction Helps itself and the vendor learn and grow To create a community, there must be users and a motivation for them to interact

COMMUNITY = Best Practices? • The best Best Practices are not written by the Vendor, they are written by the COMMUNITY (and maybe compiled by the vendor) – even if the Vendor disagrees Vendor=theory, Community=practice “In theory there is no difference between theory and practice, but in practice, there is a difference.” – French proverb

Best Practices are a Natural Result of Community Start- Better Alignment with customer needs = Better R&D Better R&D = Better Product

Software Quality Acceleration (Vendor) - Increased quality of feedback to vendor - Vendor understands market better

Next Generation of Practitioners Experience Acceleration (Practitioner)

Accelerated Time-to-Value

Maturation Acceleration Champion-building and (more Customer Best practices are natural results Champions, of community created more quickly)

Community Connections Established (Experts  Experts) (Experts  New) (New  Experts) Knowledge Sharing (Practitioner)

Document the Problem-Solving (Best Practices)

Street Cred “…answers “I would like to express my utmost “Quickly browsed questions appreciation to the amazing work through the docs…and before they’re done…around the CMS BP program and its I must say that this asked.” deliverables!” stuff is excellent!” The content is excellent…So well done! “Reading these documents is giving us (the field) the confidence that we're not only selling “…I basically utilized the key bullets tools but actually understand the whole from those presentations to frame methodology to successfully implement them.“ (for my planned audience) what I feel are best practices for discovery and due-diligence.” “I…downloaded the CMS Best Practices lib. Rev2 after reading your post at IT Service “…Really like the content. Using to Management Blog. The library is awesome, I create own on-boarding processes have been looking such a document for and templates. Will have some months…By the guidance of the library and HP feedback for you once we start I am sure we will be successful in the using. “ project…Thank you very much. I hope we will be in touch, in our CMS journey.”

Practitioner’s Forum – 2010 EMA Radar Report Survey* quotes customers : the practitioner’s forum is a distinguishing competence for HP – Gartner’s CMS committee shares many members – Knowledge sharing ROI – often a quick solution exists • Solutions re-used as available, no process effort/delay!

– practitioner: “I didn’t have to spend hours emailing logs and proving to support that I had a solvable problem, the guy just told me the answer.” • Fast, direct ROI for new customers in critical implementation phases! • Accelerated discussions on advanced topics between experts! • Time to discuss the nuances and subtle details of deep use cases

– Networking with peers and HP contacts – Easier to maintain alignment with HP strategy

– Field content distribution / HP Live Net

The Isolated Practitioner Even the best practitioner, in isolation, can only achieve half-speed

Application

Learning

Practitioner + Community Multiple practitioners, in multiple shops, collectively learn many times faster… Acceleration Maturity Software Quality

Application

Sharing

Learning

“Community sharing benefits/accelerates the individual practitioner.” “With two equally-qualified practitioners, the one with community support will get farther, faster than the one on their own.”

CMS Best Practice Library

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

CMS Best Practices Library • • • • • • • •

HP Live Net (Jody’s CMS BP Library) Represents about 10 years of practice Done and redone in PM, PMM, and RnD Three sections – Strategy, Deployment, Integrations Built on UCMDB/DDM v8 and v9, pre SPM Lots of obsolete content Some timeless and useful content PFS (My group) Currently creating a new version

CMS BP Structure Three kinds of Best Practices: - Strategy and Design-oriented - Product and technically-oriented - Deployment and Operational-oriented Product-oriented best practices should go towards the product documentation. Strategy should go towards the Reference Architecture.

Deployment and Operation should go towards the Reference Implementation.

CMS Strategy and Design (on 1 slide) • Plan for Data Quality from the Start • Build a COP (Consumer/Owner/Provider) model • Start With the Consumer and Use Case Always • Map the lifecycles of all CIs • Use the best practices • Build a CMS not a CMDB • Data modeling should follow a strategy • Technology-independent “Map-Making”

CMS Product Practices • How to build correct TQLs – product doc now • How to build GREAT TQLs – best practice now, product doc later • “How to create models and perspectives” – product doc now • “How to use models and perspectives to efficiently manage consumption of multiple users of the same data “– best practice now, product doc later • “In situation X, best use setting Y.” “Map reading”

• • • • • •

CMS Deployment and Operation

Many of these are hidden or undocumented Many service providers consider this IP Competitive monetary differentiation space Plan for Data Quality from the Start Plan to Throw One Away Do things in terms of the Strategic Best Practices – Don’t: “focus on discovery”, “implement a provider rationalization and onboarding process”. – Don’t “turn on aging”, “implement the SACM CI Life Cycle” or whatever. • Document Everything.

Lessons Learned and Resources

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Lessons Learned • Collect best practices constantly • Best Practices should be ongoing, not a project to produce a document and done • Generate and circulate knowledge constantly • Boils down to individual contributors

Resources CMS https://hpln.hp.com/group/configuration-management DDM https://hpln.hp.com/group/discovery-and-dependencymapping UCMDB https://hpln.hp.com/group/universal-cmdb UD https://hpln.hp.com/group/universal-discovery CMS Best Practices library rev 2a: https://hpln.hp.com/node/1630/attachment CMS Best Practices FAQ: https://hpln.hp.com/node/1631/attachment CMS/UCMDB/DDM Practitioner Forum Info: https://hpln.hp.com/node/1632/attachment

Thank you

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Q&A

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Backup Slides

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Software Community Elements Customer

Customers Initiatives Stakeholders and Sponsors

Initiatives

Individual Practitioners

Partners

Community

Best Practices Practitioner’s forum (direct interaction) s Discussion Forums (indirect interaction) Product (contract / foundation)

Initiatives SIGs

CABs

Vendor

Vendor Customer Support

Product Management

Product Development