ParSys Sprint - IAM/CoSS Sprint 17 Review

(Henrik Mitsch) #1

Dear Stakeholders,

here we go with our regular update.


  • Lots of small and medium bug fixes and improvements for the Open Source Student Network (OSSN) site
  • Half of the IAM Project team got together in Berlin for a work week. Lots of progress on the complex integration path from Mozillians to CIS to Auth0 to the RP and anything along the chain I forgot to mention. Please have a look at the Review slides for more details. 

Community contributed Pull Requests


Release Notes


IAM/CoSS Sprint Review



OKR Confidence Levels

This is our first Q4 OKR confidence scoring. It is prefixed in brackets, the scale is 1 to 10.

O1: Prove that IAM enables seamless collaboration among Staff and Volunteers

  • (1) KR1: Technical proof that a user who stopped using a service loses access
  • (1) KR2: Technical proof that a user profile can be retrieved from CIS
  • (3) KR3: All accounts with privileged access have MFA’d logins enforced (NDA’ed Mozillians, Staff, etc)
  • (2) KR4: A G Suite team drive is shared with a Mozillians Group (on our TEST G Suite)
  • (2) KR5: All NDA’ed volunteers who use Slack login with Mozilla’s SSO

O2: CoSS defines its V2 strategy while continue to deliver immediate results

  • (1) KR1: Update CoSS roadmap based on 2018 partnership landscape
  • (1) KR2: CoSS Event Utility is being used by two programs
  • (1) KR3: CoSS Website Builder Utility allows admins to build their own webpages
  • (3) KR4: Discussion Utility surfaces relevant activity on the OSSN property

O3: Redefine ParSys within the operationalization of the Open Innovation Strategy

  • (2) KR1: Create a vision for horizontal product and systems engineering in 2018
  • (2) KR2: A horizon model plan to support Open Innovation’s work

O4: Coherent UX/UI for Lock, Dashboard,

  • (1) KR1: Coherent UX for (“Mozilla Accounts”)
  • (2) KR2: New Lock follows the UX design

O5: Consistent staff and volunteer profiles across Mozilla properties

  • (1) KR1: Phonebook replacement specification is signed off by Open Innovation, IT, Legal and the People Team
  • (1) KR2: Technical proof that LDAP user data is provisioned into CIS
  • (1) KR3: HRIS group data allows InfoSec team to access MozDef