2011 May Sprint

From UG

Revision as of 09:12, 26 June 2011

Info

Sprint Info
Start: May 30 Mon
Staging: July 4 Mon
Prod: July 7 Thu
Days in Kiev 25 
Days in NY: 24
Holidays: 1 (Troica)
PTO:

Mantises:

• 0002963: [* Dev Sprint-2011-05 (May)] http://ct.jaguarfreight.com/mantis/view.php?id=2963
• developer's plans: 2883, 2885, 2886, 2887

Dev Plan

See mantis.

Dev Sprint updates

Notes

Major projects as defined for CT2 Board of Directors

• 1. Dashboard Reports/KPIs
  • in Development stage
  • Phase 1 to be delivered:
    • Cost Per Pound external KPI
    • Past Due Arrivals internal KPI
    • possibly proof of concept/limited functionality for one more KPI (Average Times)

• 2. Rates DB
  • in Development stage
  • Phase 1 to be delivered. Includes:
    • Database structure (core)
    • Rates editor/viewer (simple version)

• 3. International Portal
  • in Development stage
  • Phase 1 to be delivered. Includes:
    • Database structure (core)
    • Extended shipper role (covers additional MOTs Air and Ocean)

• 4. Smartphone Application
  • in Business Analysis stage
    • Detailed Business requirements to be delivered

Release schedule:

• July 7
• August 18

Business processes defined in this Sprint

WU Backlog

This is a new project added as a last phase. We need this to separate tasks that came to WU from current Sprint from tasks that are waiting for WU since previous Sprints

Change from UAT to UAT/RN

Phase UAT was renamed into UAT/RN to reflect the fact that during that phase BAs are also responsible to create RN (Release note) for every mantis to be released.

Release Notes

Release Note (for specific mantis or feature) is a summary (1-3 paragraphs) of info to be included into Release Notes and explains to end user what is this feature/bugfix/tweak/etc is about. This was requested by Simon.

See new format for RN here:

RN is to be posted into mantis note (see example below). This will be collected by Support Engineer, assembled into RN and passed to Sprint Manager for review and Sys Admin to include into "New Release" message at the time of release.

RN:
---
.... Write text here ....
.... Write text here ....
.... Write text here ....

Rel Notes example: Release Notes v2.17 May June

Proto phase and proto field

This is a new phase added for new components build without detailed designs. Before sending finalized feature to QA developer he will submit prototype to BA.

This task is to be assigned be assigned to QA with proto mantis field set to Y.

QA is to deploy this and to move to Proto folder and assign to BA.

See also diagram.

Completed tasks is to be deployed to Demo server by QA daily

TBD

Pre-Implementation and Post-Implementation Notes

In cases when design is not well defined Pre-Implementation Notes have to be posted into mantis before coding.

Post-Implementation Notes should be submitted as required before Proto and QA. Possible reasons: additional info is required to be able to do Proto and QA (info is missing or some changes have been introduced).

Example (note 0009982 from 0003041: [Rates DB] (MOT Air) (ph1) Implement Contract Upload feature):

Pre-Implem Notes
----------------
Upload procedure:
1.	User selects a menu item Acc/Rate Contracts/Rate Contract’s Upload
2.	There will be preliminary form which user should fill before chosing the file with Rate 
Contract
3.	In this form user should indicate
  a.	Name of contract
  b.	Airline or JaguarVendor for which the contract will be uploaded
  c.	Comments for this contract (optionally)
  d.	ChargeCode for this contract (one)
  e.	Included ChargeCodes for this contract (multiply)
4.	After filling this form user clicks button “Chose Contract Rate file” choses file and clicks
button “Upload”
5.	System will automatically update RateDatabase according to this file 
6.	First level of automatically updating Database will be only for one format of RateContracts 
files

Example from 0002412: [Internal Dash Reps] 1) Create "past due arrivals" DR 2) Add ability to define DR for specific group of users:

Post-Implem Notes
----------------
1) "past due arrivals" Dash Rep (DR) was created
* This rep has level 1 that consists of label and counter (num of CTs).
* Counter is a hyperlink
* click on hyperlink should open xls with past due arrivals report (existing report)
2) Add ability to define DR for specific group of users
Scheduled Reps panel will have added functionality to assign one or many Dash Reports to specific  
users
.
WARNING!
1) All dash reports assigned to user will show up in ONE panel on Internal Dashboard (Homepage)
2) Only one (past due) will work the rest of them are not fully functional

WU notes

"WU notes" is a type of mantis note that contains information that:

• was missing in spec and needs to be added during WU phase (type: add) OR
• should replace some existing info in spec (type: replace) OR
• should be deleted from spec (type: delete)

It could be posted by QA or UAT engineers who discovered gaps in specs or Implementation notes at the time of testing.

Example from 0002412: [Internal Dash Reps] 1) Create "past due arrivals" DR 2) Add ability to define DR for specific group of users:

WU Notes
--------
Warning: Counter updates one time per hour but click on hyperlink opens xls
 result with real time information (number of shipments would differ from
counter on level one).

This info will be found by engineer who is responsible by Wiki Updates and and applied to spec in WU phase.

UAT to WU transition

BA:

• completes UAT
• posts RN note
• sets task as "completed"

Sprint Manager/Architect:

• reviews
• posts note indicating wiki article where to post WU for this task and what subcomponent mantis to link to (if this is not straightforward)
• moves to WU folder
• assigns to who will do WU