Presentation from SAP Inside Track 2018 in Walldorf.
This is about the learnings and insights from my work on SAP Community in 2017, where we focused on improving the overall User Experience for our community members
Coefficient of Thermal Expansion and their Importance.pptx
UX Focus at SAP Community
1. Oliver Kohl, SAP IT Services
@oliver
o.kohl@sap.com
For SAP Inside Track Walldorf in January 2018 - #sitWDF
UX Focus at SAP Community
2. This is about the learnings and insights
from my work on SAP Community in
2017, where we focused on improving
the overall User Experience for our
community members
3. Head of CxP Engineering
Technical Owner SAP Community
& SAP People Profile
SAP Community Area PO
SDN Registration in 2005
SAP Mentor in 2008
Joined SAP in 2009
5. How?
• Regular Scrum ceremonies done via online meetings
• Cross functional, distributed teams covering dev, QA,
DevOps, performance engineering
• Requirements defined in Epics and User Stories
• 2 weeks delivery cycle with optional ad hoc prod push
Why?
• High visibility of progress with daily QA deployments
• Quick adoption to changes in business requirements
• Early identification of problems
• Low overhead of bureaucratic meetings
• Predictable delivery of functional software
9. Find answers, ask questions, and connect with our community
of SAP professionals from around the world. Our
community changes the way thousands of SAP users work
every day.
10.
11. Enhancements of 2017
January: FollowedTags Filters
February: SuggestedTags
March: Activity Stream Enhancements
April: Homepage & Browse Community Redesign
May: New 1DX Header Navigation and Actions Menu
June: Profile Enhancements
August:Archive Classification
September:At Mentioning
October: Content Browser in Profile
December: NewTag Picker, Email Notifications for new Content, Profile Linking
SAP Community Updates
SAP Community Release Notes
SAP Community Roadmap
Sources:
Who is building SAP Community?
3 Scrum teams
Cross functional Dev/QA/DevOps/Performance
Distributed across Wdf + Berlin + Minsk
Organically grown from 1 Scrum team in 2012
How we are building and delivering products
Continuous reflection and improvements
What aspects of UX are viewed at in this presentation?
Approaching it procedural from engineering perspective
They are often frameworks
Work best with specific delivery models (Important for context of presentation)
Why? Because new SC launched end of 2016 with bad usability
SC hookline
Will all SC members please stand up
Pitchforks!
designer driving the application UX
Single application integrating data from SC
Demand from business requirements, user research and end user feedback
Most used approach (see OSS)
Designed from new technical capabilities
Examples: Tag Picker - Using HANA search capabilities
Examples: at mentioning
End user validation with SAC and others
End user testing
At Mention Member In User Generated Content
Necessary often for full UX redesign of complex scenarios
Few possibilities for quick improvements comming out of gained insights
New approach for ideation and demand generation
Design for agile delivery methodologies like Scrum
Strong focus on Personas and their specific needs
Showtime
It is really easy to screw it up
It is also not that hard to fix it
But it costs a huge amount of time
So get it right from the get go, instead of having to fix it afterwards
Pick a UX approach that fits your delivery style
Bring it into the culture of your teams