Data/Platform/General sprint info - Revision history

Thomas Huelbert: gahhhhhhh link

2016-08-02T21:52:28Z

gahhhhhhh link

← Older revision		Revision as of 21:52, 2 August 2016
Line 46:		Line 46:

	Sprint status:		Sprint status:
	* [https://wiki.mozilla.org/Data/Platform/General_sprint_info/aug1\| week_of_august_1]		* [https://wiki.mozilla.org/Data/Platform/General_sprint_info/aug1 week_of_august_1]

Thomas Huelbert: fixed link

2016-08-02T21:51:42Z

fixed link

← Older revision		Revision as of 21:51, 2 August 2016
Line 46:		Line 46:

	Sprint status:		Sprint status:
	* [[https://wiki.mozilla.org/Data/Platform/General_sprint_info/aug1 \| ~~week of august 1]~~]		* [https://wiki.mozilla.org/Data/Platform/General_sprint_info/aug1\| week_of_august_1]

Thomas Huelbert: link

2016-08-02T21:49:54Z

link

← Older revision		Revision as of 21:49, 2 August 2016
Line 44:		Line 44:
	** devOps - thuelbert (thuelbert@mozilla.com) or :kparlante		** devOps - thuelbert (thuelbert@mozilla.com) or :kparlante
	* Remember other groups may be dependent on our work and using priority to track when its done. As a result, its important for the ticket to reflect when it will be worked on.		* Remember other groups may be dependent on our work and using priority to track when its done. As a result, its important for the ticket to reflect when it will be worked on.

			Sprint status:
			* [[https://wiki.mozilla.org/Data/Platform/General_sprint_info/aug1 \| week of august 1]]

Gfritzsche: /* Notes */ Name fix

2016-07-14T12:46:16Z

Notes: Name fix

← Older revision		Revision as of 12:46, 14 July 2016
Line 41:		Line 41:
	* need to be added to a triage/grooming or sprint packing meeting?		* need to be added to a triage/grooming or sprint packing meeting?
	** Pipeline - contact :thuelbert (thuelbert@mozilla.com), Rob Miller (:RaFromBRC) or :kparlante		** Pipeline - contact :thuelbert (thuelbert@mozilla.com), Rob Miller (:RaFromBRC) or :kparlante
	** mobile or desktop client - thuelbert (thuelbert@mozilla.com) or :~~gfritsche~~		** mobile or desktop client - thuelbert (thuelbert@mozilla.com) or :gfritzsche
	** devOps - thuelbert (thuelbert@mozilla.com) or :kparlante		** devOps - thuelbert (thuelbert@mozilla.com) or :kparlante
	* Remember other groups may be dependent on our work and using priority to track when its done. As a result, its important for the ticket to reflect when it will be worked on.		* Remember other groups may be dependent on our work and using priority to track when its done. As a result, its important for the ticket to reflect when it will be worked on.

Thomas Huelbert: /* How we use bugzilla */ text

2016-07-13T20:33:58Z

How we use bugzilla: text

← Older revision		Revision as of 20:33, 13 July 2016
Line 27:		Line 27:
	Priority flags:		Priority flags:
	* P1 means current sprint (these are commitments - do not roll something to a P1 unless you believe you can get to it current sprint)		* P1 means current sprint (these are commitments - do not roll something to a P1 unless you believe you can get to it current sprint)
	* P2 means next sprint (also the pile to pull off if you have extra time and all your p1's are complete)		* P2 means next sprint/this quarter (also the pile to pull off if you have extra time and all your p1's are complete)
	* P3 is next quarter		* P3 is next quarter
	* P4 is quarter after that		* P4 is quarter after that

Thomas Huelbert: /* Notes */ MOAR INFO

2016-07-06T22:59:00Z

Notes: MOAR INFO

← Older revision		Revision as of 22:59, 6 July 2016
Line 43:		Line 43:
	** mobile or desktop client - thuelbert (thuelbert@mozilla.com) or :gfritsche		** mobile or desktop client - thuelbert (thuelbert@mozilla.com) or :gfritsche
	** devOps - thuelbert (thuelbert@mozilla.com) or :kparlante		** devOps - thuelbert (thuelbert@mozilla.com) or :kparlante
			* Remember other groups may be dependent on our work and using priority to track when its done. As a result, its important for the ticket to reflect when it will be worked on.

Thomas Huelbert: /* How we use bugzilla */ notes

2016-07-06T22:52:50Z

How we use bugzilla: notes

← Older revision		Revision as of 22:52, 6 July 2016
Line 26:		Line 26:
	===== How we use bugzilla =====		===== How we use bugzilla =====
	Priority flags:		Priority flags:
	* P1 means current sprint		* P1 means current sprint (these are commitments - do not roll something to a P1 unless you believe you can get to it current sprint)
	* P2 means next sprint (also the pile to pull off if you have extra time and all your p1's are complete)		* P2 means next sprint (also the pile to pull off if you have extra time and all your p1's are complete)
	* P3 is next quarter		* P3 is next quarter

Thomas Huelbert: /* Who this affects */ MOAR infos

2016-06-21T23:24:21Z

Who this affects: MOAR infos

← Older revision		Revision as of 23:24, 21 June 2016
Line 3:		Line 3:

	=== Who this affects ===		=== Who this affects ===
	~~Client team~~, ~~Pipeline and DevOps.~~		Teams working on Fx Data Platform: measurement, quality engineering, devops

			We currently run 2 sprints:
			* Desktop telemetry / Mobile telemetry
			* Atmo / pipeline / devops

	=== Breaking down the process ===		=== Breaking down the process ===

Thomas Huelbert: new page better title

2016-06-21T23:12:36Z

new page better title

New page

== Firefox data platform sprint information ==
The purpose of this doc is to detail the sprint process used by the greater Firefox data team - which includes client, pipeline and devOps engineering.

=== Who this affects ===
Client team, Pipeline and DevOps.

=== Breaking down the process ===
* Our sprints are 2 weeks blocks of work, start on a monday and end on a friday (see sprint calendar here)
* Packing a sprint requires a groomed backlog
* Packing a sprint requires engineers on the team to understand their own capacity.
* Use IRC to communicate challenges or dependencies on other teams/engineers (we are not currently doing a daily stand up)

==== Grooming and packing ====
* Teams meet to groom backlog weekly
* Teams meet biweekly to pack sprint

===== what do I need to do in order to prepare for sprint packing? =====
understand your capacity
* how many days do you wish to pack/commit to the sprint versus how much time you want to reserve for interrupts, mentorship, meetings etc?
** for example: Jane is going to commit to 6 days of packed items, and will reserve 4 days for mentoring, interrupts and meetings. However - during the sprint, there were fewer interrupts than expected (hahahahaha). As a result, after finishing her committed P1’s, she grabbed a few P2’s off the stack and does those as well.

===== How we use bugzilla =====
Priority flags:
* P1 means current sprint
* P2 means next sprint (also the pile to pull off if you have extra time and all your p1's are complete)
* P3 is next quarter
* P4 is quarter after that
* P5 z_later

===== Sizing (Points) =====
* small is < 1 day (1 point)
* medium 1-3 days (2 points)
* large = > 3 days (3 points) NOTE: it may make sense to break down large items into more actionable chunks - we'd like to avoid a scenario where the same bug spans multiple sprints (this does not apply to meta bugs)

===== Notes =====
* Over commit to a sprint? Talk to your team/make it known you won't be able to hit your commitments
* need to be added to a triage/grooming or sprint packing meeting?
** Pipeline - contact :thuelbert (thuelbert@mozilla.com), Rob Miller (:RaFromBRC) or :kparlante
** mobile or desktop client - thuelbert (thuelbert@mozilla.com) or :gfritsche
** devOps - thuelbert (thuelbert@mozilla.com) or :kparlante