Dev News

From UG

Revision as of 15:46, 3 December 2009

2009 December

(!!!) SVN Migration has been re-scheduled for Fri, Dec 4 (8 am Kiev time)

SVN Migration is scheduled for Monday, Dec 7 (8 am Kiev time)

• Pls make sure you commit all your code before 8 am Kiev time (Noon Novosibirsk)
• SVN might not be available for 1-2 days

2009 November

SpecQA goal: complete all high/med tasks by Dec 15

Attn: Developers / Sys Analysts,

Tira and I agreed on this goal:

Complete all high/med tasks in SpecQA by Dec 15. This is to be able to create advanced plan for several months ahead. I would like to repeat that this is the most important task for the next 2 weeks (Of course this is AFTER we successfully release Dec 1).

Let me know if you have any questions.

Alex.

SpecQA and Future Planning

Attn: Developers / Sys Analysts,

We need to plan all Sprints in advance. In Sprint Plan we want to include only estimated and passed Spec QA tasks.

Next Sprints are:

• Sprint#1 (Dec 1-15)
• Sprint#2 (Dec 15-30)
• Sprint#3 (Jan 1-30)
• Sprint#4 (Feb 1-28)

The goal is to review, estimate enough tasks:

• for Sprint#1 by(on) Dec 1
• for Sprint#2 by Dec 15
• for Sprint#3,4 by Dec 30

Tasks must be reviewed / estimated in the order of priority. Urgent tasks first, then high, then med, etc.

All these tasks are assigned to specific developer and live in SpecQA mantis folder. As usual if you have questions set feedback/assigned to Sys Analyst. And if you finished then set task as completed and leave it in SpecQA folder.

Thx!

--Alex 19:25, 28 November 2009 (UTC)

Release to Staging has been moved AGAIN to earlier date: Fri, Nov 27

--Alex 21:02, 26 November 2009 (UTC)

Mantis folders re-organized

--Alex 22:31, 25 November 2009 (UTC)

I re-organized mantis folders. These are the folders that you should see: http://mantis.jaguarfreight.com/wiki/File:Mantis_projects.JPG

Tasks assigned to developers in SpecQA mantis folder (important!)

Developers are going to be assigned tasks in SpecQA. This is not for immediate coding! This is to QA the spec. Developers have to:

• set as accepted/started
• review task / read spec
• set emh
• set risk
• if there are questions - set to feedback, assign back to sys analyst (Alex or Tira)
• set as completed and leave it in specQA

After they pass your QA at some point they are going to appear in the Next Sprint folder which contains all tasks planned fro Next Sprint.

Release to Staging has been postponed until Monday, Nov 30

(Nov 24, Tue) from Alex

• We postponed because we want to test/fix all other reports as much as possible, not just List CTs/In Transit
• Priorities:
  • p1) In Transit / List CTs
  • p2) Main, Where Is, Daily
  • p3) 6 internal reports

• I assume we can test Staging in one day and if no critical bugs found - we release into Production on Tuesday, Dec 1

Reminder: Thursday/Fri are holidays in the USA this week

(Nov 24, Tue) Alex

December Sprint - radically new approach

(Nov 24, Tue) from Alex This time we are dead serious about long term planning:

• Sprints period will be 1 month not 1 week as before
• Release to production will be always done once a month (before th 1st of the month)
• All specs must be completed, estimated and pass QA
• It will be very important not to over promise
• Currently PM Team is reviewing all tasks with stakeholders and assigning urg/high/med/low priorities to each task. After that each task will be assigned tentatively one of the Sprints in Dec, Jan, Feb, Spring, Summer