B11

From UG

(Difference between revisions)
Jump to: navigation, search
(march6)
(March 7)
Line 94: Line 94:
== March 7 ==
== March 7 ==
-
Last 6+ months experience demonstrated limits of BAs and need for SA to interface with MOs directly at early stages of tasks and then drive all tasks except those with small architectural impact.
+
* Last 6+ months experience demonstrated limits of BAs and need for SA to interface with MOs directly at early stages of task development and then drive all tasks except those with small architectural impact.
-
BAs could be used for many other important activities:
+
* BAs could be used for many other important activities:
-
* support
+
** support
-
* user guides
+
** user guides
-
* BR docs
+
** BR docs
-
* coordination
+
** coordination
-
* etc
+
** etc
 +
 
 +
* NY BASA team must engage in massive verbal discussions at early stages of M/XL/L tasks development (writing RFSA here and emailing it will not work!)
 +
 
 +
* Kiev Dev team must submit proposal of a solution verbally or in writing and after implementation explain again how they implemented
 +
 
 +
* Architect must review ALL tasks at early stages (with MOs) and then again after spec before development. Must initiate / participate in joint design meetings
 +
 
 +
* MOs plans in Word docs!

Revision as of 04:58, 7 March 2011


Contents

jan01 - jan31

march1

  • 1 New Strategic decision about "Holistic approach to IT and Web systems" approved by Simon - see notes11#itn1
  • 2 Airstatus / EUAN team (I am completely out, Tira is a lead to deliver)
  • 3 Rates module and SA team development - my focus for the next several months

More:

...


march2

Added these wikis: itn 1,2,3,4; cs 1,2


march3

  • added bp1, bp2
  • new process for Support
  • new proccess for BAs - self assign tasks/projects one at a time
  • new approach to components - create more of them and smaller (Log, Help are new components)

march4

march6

Overview of current projects for Simon

Medium and large tasks

Denise

Tira

Tracie

  • 0002690: Rates Database (tariff and contract management system with additional functionalities)
    • Description
Main Features:
* management of tariffs and contracts (client and vendor sides)	
* "Quotations" web portal	
* Automated population of charge table in "sales invoices"
* Automated calculation of "estimated P&L"
* Etc	
http://ct.jaguarfreight.com/wiki/2690_rfsa 
    • Size: XXL
    • Impact: XXL
    • Phase: BA
  • 0002648: [EU Advanced Notice] Implement this
    • Description: Add component to support a new regulation enforced by EU (European Union) Customs. It will require information to be sent via EDI to some airlines prior to departure.
    • Size: L
    • Impact: L
    • Phase: SA
  • 0002782: [Air Status EDI] Version 2.0
    • Description: Implement a service to automate air status updates.
    • Size: L
    • Impact: L
    • Phase: SA
  • [SA] 0002653: (Acc Report: Misc) add feature to show total VAT charges separately
    • Description: Accounting report should breakout the VAT charges from the total of the invoice. The report should show the total VAT, Total invoiced amount without VAT, and then grand total.
    • Size: M
    • Impact: S
    • Phase: SA
  • 0002766: (Acc Report: Misc) Add a special view to accounting report to show estimation
    • Description: Adding to acc>reports>profit/loss for multiple CT's. Add columns to the output to show estimation totals in comparison to the actual totals.
    • Size: M
    • Impact: M
    • Phase: SA
  • [SA] 0002761: (Acc: SI&II) add payment instructions to be printed onto the Sales Invoices
    • Description: If the Sales invoice is from the London office, the sales instructions need to be specific as to the final currency of the billing and printed on the invoice the attached instructions.
    • Size: M
    • Impact: M
    • Phase: SA
  • [SA] 0002762: (Acc: SI&II) add a small letter “v” next to the items that have been charged with a VAT (on the invoice)
    • Description -- see summary
    • Size: S
    • Impact: S
    • Phase: SA

Alex

I was heavily involved in every project of size M+; strategy; management; IT support coordination.

March 7

  • Last 6+ months experience demonstrated limits of BAs and need for SA to interface with MOs directly at early stages of task development and then drive all tasks except those with small architectural impact.
  • BAs could be used for many other important activities:
    • support
    • user guides
    • BR docs
    • coordination
    • etc
  • NY BASA team must engage in massive verbal discussions at early stages of M/XL/L tasks development (writing RFSA here and emailing it will not work!)
  • Kiev Dev team must submit proposal of a solution verbally or in writing and after implementation explain again how they implemented
  • Architect must review ALL tasks at early stages (with MOs) and then again after spec before development. Must initiate / participate in joint design meetings
  • MOs plans in Word docs!
Personal tools