2011 January 3 update

From UG

(Difference between revisions)
Jump to: navigation, search
(→New Rules for Dev Sprint)
(→Allocation per module for Jan 2011)
 
Line 65: Line 65:
* [[:Category:OpsMisc]]  / Tracie  / Alex OR Andrei(Roma)
* [[:Category:OpsMisc]]  / Tracie  / Alex OR Andrei(Roma)
* [[:Category:Acc]]      / Tracie  / Alex OR Andrei(Roma)
* [[:Category:Acc]]      / Tracie  / Alex OR Andrei(Roma)
-
 
+
* [[:Category:AccRep]]      / Tracie  / Alex OR Andrei(Roma)
* [[:Category:Misc]]      / various
* [[:Category:Misc]]      / various

Current revision as of 21:40, 3 January 2011


Contents

[edit] Changes in Jan 2011

[edit] BASA Sprint

  • Managed by Tira
  • It is a monthly Sprint for Product Team (BA/SA work)
  • see BASA Sprint mantis project
    • View Issues should have these columns: 
Project	BASAspr#	Status	T	p.BA	p.SA	p.Dev	%BA	%SA	comp	  	  	ID	Summary
  • new related mantis fields:
    • BASAspr#
    •  %BA
    •  %SA

[edit] New Rules for Dev Sprint

  • Managed by Alex for now
  • Interface to Product Team processes and BASA Sprint managed by Tira
  • 1) normal sprint should has 4 full weeks of development starting on Monday and ending on Fri
    • it is OK to have 1-2 national holidays or days off to be a part of a Sprint, if more consider adding one additional week to Sprint
  • 2) Staging/Dev Est week is not considered part of the Sprint. During this week:
  • 3) Dev Sprint:
    • Dev Sprint Plan (approved by CT Board) submitted by Product Team Lead to Dev Team Lead (to Alex for now)
    • ideally starts on Mon next week after staging
    • starts only after Sprint Plan is signed by both Product and Dev team leads

[edit] Allocation per module for Jan 2011

NOTE: Roma is again dedicated QA

(Module / BA / SA(QA)):


  • Category:OpsAdmin / ? / Alex OR Andrei (Roma)
  • Inventory / ? / Alex OR Andrei (Roma)



Retrieved from "https://wiki.jaguarfreight.com/2011_January_3_update"
Personal tools