2011 May Sprint

From UG

(Difference between revisions)

Current revision as of 11:05, 22 July 2011

[edit] 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

(work in progress): Release Notes v2.17 May June

[edit] Dev Plan

See mantis.

[edit] Dev Sprint updates

[edit] Notes

[edit] Business processes defined/clarified and Important messages in this Sprint

[edit] Proto phase and proto field has been added

Proto is a new development phase added for new components built without detailed designs/specs.

Prior to sending finalized feature to QA developer in this case will have one or more rounds of prototype reviews with Business Analyst. This is a "Proto(typing) phase" and during this phase task should be in "Proto" mantis folder.

This type of task is to be flagged with proto mantis field set to Y by developer.

QA engineer is to deploy this task to Demo server and to move it to Proto folder and assign to BA.

[edit] Completed by developers tasks is to be deployed to Demo server by QA engineer daily

There is a new daily process that QA engineer should follow daily to deploy to Demo server completed (committed) by all developers tasks:

- find all completed by developers tasks in Dev, DevPull, Proto, QA folders
- deploy new version of code to demo site
- move to appropriate folder as required and assign to BA or QA engineers as appropriate
- do it once a day at least

Previously this job was done by one of the developers.

[edit] Pre-Implementation, Post-Implementation and WU Notes

Pre-Implementation and Post-Implementation Notes must be posted by developers under the following circumstances.

When implementation is not well defined (or not defined at all) in spec written by BA then Pre-Implementation Notes must be posted into mantis before coding by developer.

Post-Implementation Notes must be submitted after coding and before Proto and QA phase if spec or previous notes provide not enough info regarding what was coded and deployed.

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

Pre-Implem Note
----------------
Upload contract feature will be added:
1.	User selects a menu item "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

Post-Implem Note
----------------
- go to Acc > Rate Contracts > Rate Contract’s Upload
- to test use erate sheet.xls in 0002894

WU notes is a type of mantis note that contains some additional important missing information about component that will be needed in Proto, QA, UAT, WU phases. Example:

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

It could be posted by QA or UAT engineers or developers or anyone who discovered gaps in specs or Implementation notes.

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 included in Support Guide in WU phase.

[edit] Release Notes to be created by BAs at UAT phase

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 Note (for specific mantis or feature) will be included into Sprint Release Notes and explains to end user what is this feature/bugfix/tweak/etc about. It could be just plain text or it could contain screen shots.

Below is "plain text" example for 0002931: [KPI] (External KPIs) Cost per pound (Level 2). Add more options.

Rel Notes
---------
Two additional options has been added as a choice for Axis X to this report: a "Consignees" and 
"Shippers" (Suppliers). Both options support line or a pie chart visualization.

In some cases mantis summary could be decsriptive enough and RN is not needed.

[edit] UAT to WU transition and WU Backlog

BA:

completes UAT
posts RN note
sets task as "completed"

After that:

Sprint Manager/Architect:

reviews
assigns Rel Num
includes RN into Sprint Release Notes
moves to WU folder
assigns to who will do WU
(optional) posts note indicating wiki article where to post WU for this task and what subcomponent mantis to link to (if this is not straightforward)

[edit] 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. Sprint Manager is to move tasks to this folder.

[edit] Weekly BAPM update meetings

Once a week I will have 1-1.5 hour voice over Skype individual update meetings with every BAPM:
- Tracie: Tuesday 10:00-11:30am EST
- Denise: Wednesday 10:00-11:30am EST
- Tira: Thursday 10:00-11:30am EST

Weekly Reports. I am thinking now in what format I need them

Once a week I have to report to Jaguar Executive/CT2 Board and President about our progress. Please note that this is of course will be based largely on your reports. I will have to update the President on each key project as well team performance.

[edit] BAPM is responsible for success or failure of a project/task

Once again I would like to remind that:

each Sprint we have 4-7 key concurrent projects
BA/PM is personally responsible for failure or success which means they need to be proactive, have up to date plans, regular meetings with a project team, etc
you can escalate serious issues to Sprint Manager but daily work and decision making is on you
feel free to invite Sprint Manager/Architect to be part of your weekly project meetings (sometimes)

[edit] Review and refinement of existing methodology

[edit] PM and Estimation week

The purpose of this week is for PMs, BAs, Devs, QA to work together to review all requirements for new tasks, estimate them, create preliminary architecture/vision, project plans (this includes breakdown into smaller tasks/milestones with due dates), etc. If time permits it is also to implement some tasks from DevPull.

Results should be documented: project plans in xls form, pre-implementation notes and architecture in mantis notes or wiki or attached to mantis docs. Mantis is to be created for sub-tasks.

[edit] CT2 and Jaguar components and subcomponents

[edit] Components

Currently CT2 is divided by the following mutually exclusive components:

Acc
- Acc
- AccReps
- RatesDB

Client
- Client
- ClientEtc
- ClientReps

Ops
- Ops
- OpsAdmin
- OpsPdf
- OpsRep
- OpsTruck

Misc
- Misc
- IT/Systems

This is reflected in "comp" mantis field.

[edit] Subcomponents

Each CT2 component is divided by several sub components. Each sub-component has a mantis record. We used to call it "parent mantis". They all are located in "Subcomponents" mantis folder.

For example AccReps CT2 component consists of the following sub-components:

2250	(Acc Report: Acc Milestones)  
1938	(Acc Report: CTs With No Inv)
2303	(Acc Report: CTs With No Inv) 
2581	(Acc Report: Incomplete PI Report)  
650	(Acc Report: Misc)  
2175	(Acc Report: P and L)  
1942	(Acc Report: Search Inv)

[edit] History of sub component

By establishing child-parent relationship between each task defined for specific sub-component we preserve History record. For example this is a history of 1942 (Acc Report: Search Inv) :

#	status	assigned to	phase	Summary
1943	closed	demo	* Released	(Report:Search Inv) bug: There are no company offices listed on the “receiving office” drop down menu [Delete]
2585	closed	tracie	* Released	(Report:Search Inv) bug: Incorrect status of Purchase Invoice issued from CT with empty Commodity Table [Delete]
2598	new	kostya	3.0 Dev Est	(Report:Search Inv) bug: report works too long when performs search of ALL Purchase Invoices [Delete]
2960	new	tracie	2. BA Phase	[Acc 2011] (Acc Report:Search Inv) Add feature to run this report showing VAT charges separately [Delete]
2969	completed	tracie	d. UAT/RN	(Acc Report:Search Inv) Add a way to select show an additional currency for this report [Delete]

[edit] CT2 projects vs CT2 subcomponents

[edit] Misc

[edit] Major projects (as defined by Simon)

4 projects below are TOP Projects (as defined by Simon).

I committed to the following this Sprint (to Jaguar 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

2011 Release schedule:

July 7
August 18

[edit] IT Support letter

To: alljaguarny

Dear All,

Please read and follow IT Support guidelines defined below.

1) Send email to ihelp@jaguarfreight.com if you need help with:

CT2 system
Sugar CRM
www.jaguarfreight.com website

Please note that these types of issues are currently handled by Jaguar IT&Software Development group in Valley Stream, NY.

2) For all other IT related issues email itsupport@jaguarfreight.com or call 1-800-214-1874.

Please note that these types of issues are currently handled by TSI company (our IT partner).

3) In case of urgent requests such as lost internet connection, lost CT2 connection, etc please contact anyone from IT&Software Development group based in Valley Stream immediately and directly. If nobody from this group is available please call 1-800-214-1874.

4) Before sending IT request please:

re-start your system and see if this fixed a problem
make sure that your request provides all details and please attach a screenshot

5) Response time for non-emergency issues is 1-2 hours. Many routine IT issues will be handled remotely. On site visit will be scheduled when necessary.

6) IT Support is currently coordinated by Montira (montira@jaguarfreight.com). Please escalate any issues with support (such as quality of support, response times, etc) to her.

If you have any questions, concerns or suggestions regarding these guidelines please contact montira@jaguarfreight.com.

Thank you for your cooperation.

Best Regards, IT Dept, NY

[edit] Updates/Presentations for Simon's visit to Kiev