ASN 20 Captains journal
From UG
Year 2012
Contents |
[edit] About
Written by SA responsible for project (Alex). To reflect and learn.
[edit] Aug
[edit] 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
[edit] Aug 15 Wed
Final spec review meeting w/ Marc.
Many changes at the core and some at the edge.
On Fri review w/ Simon.
[edit] 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
[edit] 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.
[edit] Sep 11 Tue
Perry, Kostya, Schedule and deadlines. I completed 90-95% of spec for ASN, divided scope into SOWs and assigned to resources as identified by Kostya. There are few changes from yesterday’s meeting with Marc/Simon. Will add them as a separate tasks this week. This should not have negative impact. Major next deliverable is a demo of Shipper/Planner ASN 20 functionalities scheduled for Arden on Oct 16. We need to deliver demo to Marc/Simon prior to that. I would say latest Oct 11. Ideally earlier than that because we promised to show this to another prospective client ASAP. But because we do not have much time it would probably be just a bonus if we do that. Today is Sept 11. So we have about one month. A bit less actually. Note that we deliver in our dev environment as a demo. No date for release to prod yet. Please minimize impact of upcoming Release to this project. As discussed with Perry today, only Misha will be available for ASN later (next week Monday). Everyone else (Kostya, Sasha, AK) should be able to dedicate 100% to ASN from tomorrow (except that AK will be needed for DQ for few hours tomorrow). At the same time some urgent DQ might require a bit of resources. Hopefully not too much. Certainly < 1 full dev total. As agreed DQ will be shared across the team. Dependencies. If each developer goes over SOWs in sequential order then this would minimize risk of dependencies. Lists of tasks are created in such a way that each dev would not have to worry too much where somebody else is with their tasks. Full list of dependencies I will create later this week. Please let me know if you have any questions. Let’s meet tomorrow/Thursday to go over this verbally as well.
