ASN 20 Captains journal

From UG

(Difference between revisions)
Jump to: navigation, search
(→Aug 27 Mon)
(→Aug 27 Mon)
Line 26: Line 26:
=== Aug 27 Mon ===
=== Aug 27 Mon ===
 +
 +
Today Simon, Marc and I discussed 3 very different solutions.
 +
 +
Agreed on one that should be flexible enough but also fairly simple to implement.
<pre>
<pre>
Line 61: Line 65:
Regards, Alex
Regards, Alex
 +
</pre>
 +
 +
=== Sep 4 Tue ===
 +
<pre>
 +
Marc/Kostya,
 +
 +
Here is how I see our plans/schedule based on today’s input.
 +
 +
I will put together ONE solution that should address all concerns/incorporate all new ideas and latest requirements (such as multiple 3PLs, etc).
 +
 +
Please note that ASN coding started last week. One dev (AK) is fully allocated to this project.
 +
 +
THIS week:
 +
 +
Tue, Sep 4 – will try to complete core spec
 +
Wed, Sep 5 – will discuss with Kostya including core tasks breakdown; change spec to address his possible concerns/ideas
 +
Thur, Sep 6 – will present spec that Kostya / Alex agreed on to Marc
 +
Fri, Sep 7 – will address possible Marc’s concerns; Marc/Alex will present to Simon final spec; will get his feedback/sign off
 +
 +
NEXT week:
 +
 +
Mon, Sep 10 – will change spec to address possible Simon feedback/concerns; prepare detailed work breakdown structure/Mantis tasks
 +
Tue, Sep 11 – discuss with Kostya detailed work breakdown/mantis tasks; Kostya assigns developers
 +
Wed, Sep 12 – developers estimate tasks; additional devs Kostya/Sasha/Misha? will join AK in coding ASN 20 (UP TO 3.5 devs ALLOCATED TO THIS PROJECT)
 +
Thur, Sep 13 – I present spec/tasks to Perry so he can update/adjust his Master Proj Plan
 +
Fri, Sep 14 - add implementation details for some noncore tasks/modules/functionality; devs will clarify estimations
 +
 +
Plan above assumes that we will not discover any major issues with current vision/approach.
 +
 +
Please comment.
</pre>
</pre>

Revision as of 22:19, 4 September 2012


Year 2012

Contents

About

Written by SA responsible for project (Alex). To reflect and learn.

Aug

Aug 10 Fri

  • requested 1 more week to add to construction
  • Crash and Baseline proj plans were sent to Simon
    • both allocate 4 weeks for coding
  • completed Solution wiki; printing, reading, minor edits

Aug 15 Wed

Final spec review meeting w/ Marc.

Many changes at the core and some at the edge.

On Fri review w/ Simon.

Aug 27 Mon

Today Simon, Marc and I discussed 3 very different solutions.

Agreed on one that should be flexible enough but also fairly simple to implement. 

All,

This is ASN 2.0 project status update.

1) Architecture.

Today ASN 20 dev team continued discussing various architecture options that would satisfy requirements. 

I think we finally have a vision that might work. We will continue analysis/clarifying details tomorrow.

I will document and send final Architecture/Design spec to Simon and Marc for approval once they are ready 
(estimate: end of this week/early next week).

2) Coding.

We also reviewed all Misc tasks and confirmed that 5 out of 6 (except #3.6) could be pushed into coding ASAP before new Architecture is finalized. See list of these tasks below:

3 Misc tasks
3.1 Add Clone User feature
3.2 Add create GRP action to Virtual Group
3.3 Merge Com and EQuery
3.4 Flag CT feature
3.5 Flexible Shipments List
3.6 "Forward" approved shipment info to 3rd party (ON HOLD)

I will finalize specs, create mantis for all of them, confirm developer and get estimate. 

We can start coding them as early as Wednesday/Thursday I think.

Please let me know if you have any questions.

Regards, Alex

Sep 4 Tue 

Marc/Kostya,

Here is how I see our plans/schedule based on today’s input.

I will put together ONE solution that should address all concerns/incorporate all new ideas and latest requirements (such as multiple 3PLs, etc).

Please note that ASN coding started last week. One dev (AK) is fully allocated to this project.

THIS week:

Tue, Sep 4 – will try to complete core spec
Wed, Sep 5 – will discuss with Kostya including core tasks breakdown; change spec to address his possible concerns/ideas
Thur, Sep 6 – will present spec that Kostya / Alex agreed on to Marc
Fri, Sep 7 – will address possible Marc’s concerns; Marc/Alex will present to Simon final spec; will get his feedback/sign off

NEXT week:

Mon, Sep 10 – will change spec to address possible Simon feedback/concerns; prepare detailed work breakdown structure/Mantis tasks
Tue, Sep 11 – discuss with Kostya detailed work breakdown/mantis tasks; Kostya assigns developers
Wed, Sep 12 – developers estimate tasks; additional devs Kostya/Sasha/Misha? will join AK in coding ASN 20 (UP TO 3.5 devs ALLOCATED TO THIS PROJECT)
Thur, Sep 13 – I present spec/tasks to Perry so he can update/adjust his Master Proj Plan
Fri, Sep 14 - add implementation details for some noncore tasks/modules/functionality; devs will clarify estimations

Plan above assumes that we will not discover any major issues with current vision/approach.

Please comment.
Retrieved from "https://wiki.jaguarfreight.com/ASN_20_Captains_journal"
Personal tools