ParSys Sprint 16 ("CES 2017") - Forecast

Participation Systems
#1

Sprint 16 - Anatomy

  • Sprint 16, known as “CES 2017”, runs from 09 JAN to 13 JAN 2017

Sprint 16 - Goals

  • Groundwork for ParSys properties on ParSys infrastructure
  • NDA Renewal
  • Mozillians.org modernization: Search Improvement Spike
  • Preparing the Discourse Story for 2017
  • Prepare Work Week

Sprint 16 - Details and Forecast

Context and North Star - ParSys Q1 Objectives

OKRs are still in draft. Prefixed in brackets, we list the current achievement confidence on a scale of 1 to 10.

  • (3) Q1 alignment with key stakeholders sets us [ParSys] up for success in 2017
  • (2) Mozillians.org LDAP integration (IAM Package C) is on track to become “the LDAP frontend” during Q2
  • (2) VMS/MozNet/Local Organizing successfully ships product increments to PROD demonstrating the effectiveness of a MoCo & MoFo co-staffed product team

Feedback and Questions

1 Like
#2

An amazing sprints, but I have an off-topic question who decide the sprint codename? Because they are amazing lol

#3

This was @pierros’ suggestion: During the planning meeting we open the techcrunch website and take the major headline as sprint name. It’s fun every week.

1 Like
#4

What is a “Search Improvement Spike”?

What Work Week? Mind sharing more information about that one?

#5

We use the term spike to indicate that we are aiming to generate insight instead of shipping product.
If you want to know about the search improvements we actually plan, may I point you at this Taiga story? Feel free to comment on it here (not sure if Taiga allows for anonymous commenting).

It is a week of work happening with IAM (mostly IT) folks and VMS (mostly MoFo) folks and ParSys people in two weeks in Berlin.
On the VMS side it’s mostly about Clubs and even more specifically, identifying and scoping shared software related needs between programs.

Hope that helps? Is the second answer containing too much jargon? If yes, please call me out on it.

Best regards,
Henrik

2 Likes