Cybertrax 2.1 Client (project plan)

From UG

Revision as of 14:25, 20 July 2010 by Alex (Talk | contribs)
Jump to: navigation, search


Contents

About this doc

This wiki provides all Proj Management info for Cybertrax 2.1 Client project.

Intro

This project is very important therefore planning is critical.

Time vs Features vs Quality

Focus of this project is to deploy minimal set of core features ASAP. As a result feature set will be reduced to minimum and quality might be average (but must not fall below reasonable level)

Time allocated and Error margin 

Summary of time allocated:
 * only 1 week for analysis and requirements gathering
 * only 1 week for design
 * only 3 weeks for coding, testing, rollout/training planning
 * only 1 week for staging/release
-----------------
Total: 6 weeks
                 NOTE: This is an estimate. Error is -1 week/+2 weeks.

Project documentation

All information is gathered and structured in several wikis under Category:Cybertrax 2.1 Client

Current list of docs: 

Cybertrax 2.1 Client (Q and A)
Cybertrax 2.1 Client (data dictionary)	 
Cybertrax 2.1 Client (design)
Cybertrax 2.1 Client (glossary)
Cybertrax 2.1 Client (project plan)	 
Cybertrax 2.1 Client (requirements)
Cybertrax 2.1 Client (use cases)

Project communication

All communication is done through:

  • mantis
  • Skype
  • email (everyone must check min 2 times a day and reply or at least confirm e-mail received same day)
  • Q and A wiki article: Cybertrax 2.1 Client (Q and A)

All mantis tasks are under this parent: http://mantis.jaguarfreight.com/mantis/view.php?id=2077

Project broadcasts and forum

Project update meetings

  • who must attend: Andrei, Sasha, Alex, Denise, Tira
  • Tuesd, Thursd 10-11am
  • Skype chat
  • Coordinator on NY side / Host: Alex
  • Coordinator on Kiev side: Sasha

Project Team and responsibilities

  • Alex - Proj Manager and Solutions Architect; responsible for:
    • proj management/coordination
    • solution architecture/structure
    • helping everyone as required

Requirements and Documentation Team

  • Denise - Business Analyst, RFP Lead; responsible for:
    • gathering requirements and interfacing stackeholders/clients/module owners
    • documenting requirements (#RFP specs)
    • must help Sys Analysts to discover info
    • proof reading/editing docs (in terms of English lang)
  • Tira - Systems analyst, UI/UC Lead; responsible for:
    • creating solution based on requirements
    • documenting design
    • focus on creating user interface mockups, use cases (UC)
    • helping Denise in more technical aspects of requirements gathering/analysis
  • Andrei - Systems analyst, 3CS lead; responsible for:
    • creating solution based on requirements
    • documentation (managing #3CS specs)
    • focus on analysing all existing docs and making sure nothing is missing
    • face to face meetings with dev leads / developers about specs/design in some cases as required
    • answer questions from developers/ dev leads about specs

Implementation team

  • Kostya - Development Manager
  • Sasha - Lead developer
    • serving as a communication liaison between Implementation team (Kiev) and Requirements team (NY)
  • Andriy - Developer
  • Roma - QA and Support

Workflows

Specs workflow

  • Sys Arch (Alex) provides high level breakdown into components / wiki sections
  • BA (Denise) creating:
    • "(requirements) wiki", #RFP specs type
    • "business story" for (use case) wiki
  • SA1 (Tira) creates use cases (UI mockups+descr) based on "business story" and "(requirements) wiki"
  • SA1 (Tira) helps Denise with more technical parts of "(requirements) wiki"
  • Tira and Denise review/proof read each other work
  • Completed sections get passed to SA2 (Andrei). His goal is:
    • a) transform #RFP specs into #3CS specs:
      • asking questions (if something is incomplete/incorrect/unclear)
        • first reach out to Denise (business req questions) or Tira (if more technical question). If they for some reason can not answer then escalate to Sys Arch (use this option with care - SAs/BAs should be able to make your own decisions)
      • rewriting/restructuring spec as required
    • b) update them if new info comes in
    • c) assigns into Estimation
    • answer questions from Developers and Dev Leads (walk them through spec in face to face in some cases as required )
    • Note: #Black box design has additional specs of updating spec after Dev is completed
  • Sys Arch:
    • resolves escalations
    • reviews final specs (in some cases) and assigns into Estimation if it is good

Dev and QA workflow

As usual

Tasks

It is very important to find a good way to disect an monster into pieces to be able to digest it.

Requirements and Documentation tasks

  • 2126 Shipper functionality - Finalize specs/document
  • 2128 Planner functionality - Finalize specs/document
  • 2129 Jaguar functionality - Finalize specs/document
  • 2122 Misc functionality - Finalize specs/document

Support tasks

  • 0002140: (Client 2.1) Create User Guide, Rollout Schedule, Training Plan, Support plan

Implementation tasks

week 1

  • 2134 (Client 2.1) (implementation) Add Shipper, Planner roles to Non Jag User profile
  • 2135 (Client 2.1) Create all new DB fields

week 2

  • 2136 (Client 2.1) Code core Shipper functionality (create/edit/delete/list CTs)
  • 2137 (Client 2.1) Code core Planner functionality (authorize/list CTs)

week 3

  • 2138 (Client 2.1) Code all Jaguar functionality (new fields, constraints, Approval Report)
  • 2139 (Client 2.1) Code all misc functionality (notifications, etc)

Weekly Plan Phase One

Note: This plane has been approved!

Important Dates

  • 1st date for Release: Thur, July 15
  • 2nd date for Release: Thur, July 22

File:2010 summer calendar.JPG

week 1: June 7 Mon - June 11 Fri

Plan

  • meetings with clients
  • preliminary design sessions
  • end of the week targets:
  • requirements: 50% done
  • design: 30% done
  • documentation: 10% done
  • coding: 0% done
  • QA: 0% done

Actual

Completed as planned!

week 2: June 14 Mon - June 18 Fri

Plan

  • analyze requirements
  • invent design
  • write detailed documentation
  • Wed 2pm: send draft to Simon, Marc
  • Fri 4pm: send ver 1.0 to Bill
  • end of the week targets:
  • requirements: 80% done
  • design: 70% done
  • documentation: 60% done
  • coding: 5% done
  • QA: 0% done

Actual

Completed as planned!

week 3: June 21 Mon - June 25 Fri

Coding week #1

Plan

  • Mon/Tue tasks for every developer must be defined/assigned, start coding
  • Tue 10pm: Kiev/NY status update
  • Thur 10pm: Kiev/NY status update
  • end of the week targets :
    • specs:
      • 2126 Shipper functionality - Finalize specs/document
      • 2128 Planner functionality - Finalize specs/document
    • code:
      • complete [andriy] 2134 (Client 2.1) (implementation) Add Shipper, Planner roles to Non Jag User profile
      • complete [kostya] 2135 (Client 2.1) Create all new DB fields
      • start [sasha] 2136 (Client 2.1) Code core Shipper functionality (create/edit/delete/list CTs)
    • metrics:
    • code: 30% done
    • QA: 20% done

Actual

TBD

week 4: June 28 Mon - July 2 Fri

Coding week #2

Plan

  • continue coding and QA
  • start UC testing
  • Tue 10pm: Kiev/NY status update
  • Thur 10pm: Kiev/NY status update
  • end of the week targets
    • specs:
      • complete: 2129 Jaguar functionality - Finalize specs/document
      • complete: 2122 Misc functionality - Finalize specs/document
    • code:
      • complete: 2136 (Client 2.1) Code core Shipper functionality (create/edit/delete/list CTs)
      • start: 2137 (Client 2.1) Code core Planner functionality (authorize/list CTs)
    • metrics:
    • code: 60% done
    • QA: 40% done

Actual

TBD

week 5: July 5 Mon - July 9 Fri

Coding week #3

Plan

  • Tue 10pm: Kiev/NY status update
  • Thur 10pm: Kiev/NY status update
  • end of the week targets
    • specs:
      • complete: 0002140: (Client 2.1) Create User Guide, Rollout Schedule, Training Plan, Support plan
    • code:
      • completed 2137 (Client 2.1) Code core Planner functionality (authorize/list CTs)
      • completed 2138 (Client 2.1) Code all Jaguar functionality (new fields, constraints, Approval Report)
      • completed 2139 (Client 2.1) Code all misc functionality (notifications, etc)
    • metrics:
    • code: 100% done
    • QA: 100% done

Actual

TBD

week 6: July 12 Mon - July 16 Fri

Plan

  • QA on staging
  • Release
  • Training users
  • Mon 9am: release to Staging
  • Tue 10pm: Kiev/NY status update
  • Thur 10pm: Kiev/NY status update
  • Thur 7-8pm: release to Production

Actual

TBD

week 7: July 19 Mon - July 23 Fri

Plan

  • "2nd release date" in case we could not release previous week
  • Mon 9am: release to Staging
  • Tue 10pm: Kiev/NY status update
  • Thur 10pm: Kiev/NY status update
  • Thur 7-8pm: release to Production

Actual

TBD

Appendix. Two types of specs

Lets introduce the following.

RFP specs

All specs start as informal collection of information. At this stage they could be considered as a Request For Proposal. That is why this type of spec called "RFP type". .

3CS specs

Gradually specs should take shape and finally considered to comply to 3CS:

  • complete
  • correct
  • clear
  • structured

These type of specs we call "3CS specs".

Appendix. Two types of Design methodology

Lets introduce the following.

White box design

What we follow now in most cases:

  • Requirements doc completed
  • Sys analyst creates and documents Design based on Requirements doc
  • Design goes through review process
  • developer codes based on Design doc
  • QA tests based on Design doc

Black box design

Alternative approach:

  • Requirements doc completed
  • Developer codes based on Requirements doc (creating functional Prototype)
  • Sys analyst creates and documents Design based on Prototype
  • Design and Prototype go through review process
  • QA tests based on Design doc

Project log and Meeting Notes

Meeting Thursday Jul 15

Meeting Major Conclusions

  • proj is on schedule
  • Tira will be responsible for UAT
  • Denis gets pulled into another project and available on as needed basis
  • Roma: QA full time. If you have no new tasks pls try to come up with various use cases you did not test. Also pls post into mantis what specifically you tested. And do not forget to test all info in Data Dictionary wiki.

Chat Transcript 


[7/15/2010 2:32:33 PM] *** alex dobrovolsky added Alex Pivnyak ***
[7/15/2010 2:32:52 PM] *** alex dobrovolsky added Роман Лахно ***
[7/15/2010 2:32:57 PM] *** alex dobrovolsky added Montira Rattanavijit ***
[7/15/2010 2:33:41 PM] alex dobrovolsky: Hi guys! I created this group chat. Just waiting for Tira to join...
[7/15/2010 2:34:09 PM] Alex Pivnyak: Hi all
[7/15/2010 2:34:16 PM] Роман Лахно: hi
[7/15/2010 2:35:08 PM] alex dobrovolsky: Great, probably in 10-15 min we can start. Let me prepare agenda...
[7/15/2010 2:44:54 PM] alex dobrovolsky: Agenda:
• Proj Manager update (Alex)
a. Yesterday’s client demo
b. Denis completed her BA role, now on as needed basis; Tira – main point of contact
c. Current Release sched
• Dev Manager update (Sasha)
a. What tasks are still in Dev and when they will be completed
b. Any questions/issues
• QA update
a. Status of QA tasks
b. Any questions/issues
• Sys An update (Tira)
a. Status of spec (all up to date?)
b. Questions, issues
[7/15/2010 2:46:05 PM] alex dobrovolsky: Guys, pls meanwhile make sure all Mantises are up to dat - correct status/dfolder
[7/15/2010 2:48:36 PM] Alex Pivnyak: I just now sent 2 my completed tasks to Roma, so hi can start test it tomorrow morning
[7/15/2010 2:52:42 PM | Removed 2:52:48 PM] Alex Pivnyak: This message has been removed.
[7/15/2010 2:59:28 PM] Montira Rattanavijit: Hi all
[7/15/2010 2:59:34 PM] Роман Лахно: hi
[7/15/2010 3:02:47 PM] alex dobrovolsky: Ok, Let's start
[7/15/2010 3:03:11 PM] alex dobrovolsky: 1) PM's update
[7/15/2010 3:04:00 PM] alex dobrovolsky: a) Marc demonstrated system on Demo server to the Client and as he said "everything went very well"
[7/15/2010 3:04:18 PM] alex dobrovolsky: No additional details has benn provided.
[7/15/2010 3:04:47 PM] alex dobrovolsky: But I would like to thank everyone - we passed important milestone!
[7/15/2010 3:05:07 PM] Alex Pivnyak: thank you :)
[7/15/2010 3:05:13 PM] Montira Rattanavijit: Thank you
[7/15/2010 3:05:25 PM] Роман Лахно: and one from me ^) thank you )
[7/15/2010 3:05:55 PM] alex dobrovolsky: b)
[7/15/2010 3:07:49 PM] alex dobrovolsky: I consider that most of Biz Req has been completed for this so I am pooling he out this project into another "TMS EDI" project. She is still available on as needed project but Tira now becomes main resource here in NY for Client 2.1
[7/15/2010 3:08:34 PM] alex dobrovolsky: So pls coordinate daily Specs/QA  with her.
[7/15/2010 3:08:59 PM] alex dobrovolsky: c. current release sched:
[7/15/2010 3:09:10 PM] alex dobrovolsky: dev until end of next week
[7/15/2010 3:09:36 PM] alex dobrovolsky: staging Mon July 26
[7/15/2010 3:09:46 PM] Montira Rattanavijit: Noted.
[7/15/2010 3:09:48 PM] alex dobrovolsky: release Thur Jul 29
[7/15/2010 3:10:22 PM] alex dobrovolsky: OK, I finished my part. Any questions?
[7/15/2010 3:10:34 PM] Alex Pivnyak: no questions
[7/15/2010 3:10:39 PM] Montira Rattanavijit: no questions
[7/15/2010 3:10:44 PM] Роман Лахно: no
[7/15/2010 3:11:34 PM] Montira Rattanavijit: Thank you
[7/15/2010 3:12:11 PM] alex dobrovolsky: Just one more point - Tira will be responsible for UAT.
[7/15/2010 3:12:24 PM] alex dobrovolsky: Now, Sasha it is your turn.
[7/15/2010 3:12:37 PM] Alex Pivnyak: Ok.
[7/15/2010 3:15:06 PM] Alex Pivnyak: I planning to finish main part  core shipper-planner functionality bugs fixing  + [Client 2.1] (Misc Functionality) 6.1 - 6.6 except 6.4 NPA today - tomorrow. There are some minor issues left.  And start to develop (Misc Functionality) 6.4 New Pending Address (NPA) Feature
[7/15/2010 3:16:06 PM] Alex Pivnyak: Kostya and Andrey are  working on TDS panel functionality
[7/15/2010 3:16:06 PM] Montira Rattanavijit: I am reviewing and doing UAT at the moment for the tasks that Sasha finished.
[7/15/2010 3:16:56 PM] alex dobrovolsky: So do you think our current sched looks fine (finish dev by the end of next week)?
[7/15/2010 3:17:04 PM] alex dobrovolsky: realistik?
[7/15/2010 3:17:24 PM] Alex Pivnyak: I think yes
[7/15/2010 3:17:45 PM] alex dobrovolsky: Sasha, you done?
[7/15/2010 3:17:51 PM] Alex Pivnyak: yes
[7/15/2010 3:17:57 PM] alex dobrovolsky: Roma, you turn
[7/15/2010 3:18:09 PM] alex dobrovolsky: • QA update
a. Status of QA tasks
b. Any questions/issues
[7/15/2010 3:18:33 PM] Роман Лахно: two task on me now from Shasha for tomorow work
[7/15/2010 3:18:44 PM] alex dobrovolsky: #?
[7/15/2010 3:18:52 PM] Роман Лахно: 2218
[7/15/2010 3:18:55 PM] Роман Лахно: 2220
[7/15/2010 3:19:08 PM] Роман Лахно: and TDS panel for tomorow
[7/15/2010 3:19:29 PM] Alex Pivnyak: Andrey's part of work is almost done
[7/15/2010 3:20:09 PM] Роман Лахно: whithout * 5.2.5 TDS Action Panel
[7/15/2010 3:20:22 PM] Alex Pivnyak: Kostya is working on filters (Action panel)
[7/15/2010 3:20:34 PM] alex dobrovolsky: When do you think he will complete?
[7/15/2010 3:20:49 PM] Alex Pivnyak: Kostya?
[7/15/2010 3:21:08 PM] Alex Pivnyak: I think at beginning of next week
[7/15/2010 3:21:21 PM] alex dobrovolsky: right, pls ask him to estimate so we have approx idea of size. Thx.
[7/15/2010 3:21:26 PM] Alex Pivnyak: ok
[7/15/2010 3:23:07 PM] alex dobrovolsky: Roma, I would like to ask you to QA full time. If you have no new tasks pls try to come up with various use cases you did not test. Also pls post into mantis what specifically you tested. And do not forget to test all info in Data Dictionary wiki.
[7/15/2010 3:23:27 PM] alex dobrovolsky: ok?
[7/15/2010 3:23:29 PM] Роман Лахно: Ok
[7/15/2010 3:23:37 PM] alex dobrovolsky: Roma, anything else from you?
[7/15/2010 3:23:45 PM] Роман Лахно: yes
[7/15/2010 3:23:58 PM] Alex Pivnyak: or maybe here? http://mantis.jaguarfreight.com/wiki/Cybertrax_2.1_Client_%28UAT%29
[7/15/2010 3:24:01 PM] Роман Лахно: QA and UAT is merged now ?
[7/15/2010 3:24:20 PM] Роман Лахно: no need to move task to demo or somwere ?
[7/15/2010 3:24:34 PM] alex dobrovolsky: mantis folder? yes
[7/15/2010 3:25:45 PM] Alex Pivnyak: Roma asking where hi would move completed tasks since Demo folder is absent now
[7/15/2010 3:26:02 PM] alex dobrovolsky: Let me think
[7/15/2010 3:31:28 PM] alex dobrovolsky: Ok, I am going to have QA, UAT and Demo as separate folders
[7/15/2010 3:32:28 PM] alex dobrovolsky: Roma, pls move completed (passed QA) tasks to UAT. Tira will pick thm up from there, review and what is passed move to Demo
[7/15/2010 3:32:36 PM] Роман Лахно: ok
[7/15/2010 3:33:00 PM] alex dobrovolsky: OK, do you guys have any outstanding questions about specs?
[7/15/2010 3:33:14 PM] Montira Rattanavijit: no
[7/15/2010 3:33:21 PM] Роман Лахно: no
[7/15/2010 3:33:26 PM] alex dobrovolsky: Sasha?
[7/15/2010 3:33:35 PM] Alex Pivnyak: no questions
[7/15/2010 3:33:57 PM] alex dobrovolsky: Ok, now Tira is your turn
[7/15/2010 3:34:21 PM] Montira Rattanavijit: I am reviewing some requirement
[7/15/2010 3:34:38 PM] Montira Rattanavijit: and there may be some slightly changes.
[7/15/2010 3:34:50 PM] Alex Pivnyak: not again...
[7/15/2010 3:34:52 PM] Montira Rattanavijit: for what it didn't make sense
[7/15/2010 3:35:15 PM] Montira Rattanavijit: but the one that changed, Sasha is already notified
[7/15/2010 3:35:32 PM] Montira Rattanavijit: one thing that I am looking at it now it is about the notification
[7/15/2010 3:35:53 PM] Montira Rattanavijit: core functionality, we already discussed and Sasha understood
[7/15/2010 3:36:19 PM] Montira Rattanavijit: Only the format of the message, it might be changed.
[7/15/2010 3:36:29 PM] Montira Rattanavijit: not much just add some space...
[7/15/2010 3:36:29 PM] Alex Pivnyak: ok
[7/15/2010 3:37:04 PM] Montira Rattanavijit: created shipment has no signature...I have to find out what we would need for that
[7/15/2010 3:37:34 PM] Montira Rattanavijit: and also the Jaguar disclaimer thing, not sure whether we would like to show that or not.
[7/15/2010 3:37:40 PM] Montira Rattanavijit: I have to find that out
[7/15/2010 3:38:17 PM] Montira Rattanavijit: other than that, I am doing some UAT for the tasks that Sasha has finished and deployed.
[7/15/2010 3:38:44 PM] Montira Rattanavijit: that's pretty much it.
[7/15/2010 3:40:49 PM] alex dobrovolsky: OK, Thanks. I would like to remind that if there is a change or additiona to requirements then wiki spec must be updated (so it is up to date) and mantis created (so that QA will not miss it). As a shortcut, One mantis could be created covering several tweaks.
[7/15/2010 3:41:29 PM] Montira Rattanavijit: noted
[7/15/2010 3:42:55 PM] alex dobrovolsky: I have only one more thing - we dicussed with Sasha how to automate new user accounts.addresses creating , I will discuss this with Tira off line and create Mantis for this.
[7/15/2010 3:43:36 PM] Montira Rattanavijit: ok
[7/15/2010 3:43:52 PM] Alex Pivnyak: ok. new mantis for this will be good idea
[7/15/2010 3:44:46 PM] alex dobrovolsky: That is all from me. Anyone has any more questions for this meeting?
[7/15/2010 3:44:54 PM] Montira Rattanavijit: no
[7/15/2010 3:44:55 PM] Роман Лахно: no
[7/15/2010 3:44:57 PM] Alex Pivnyak: no
[7/15/2010 3:46:18 PM] alex dobrovolsky: 42 min total, not too bad ))) See you all next time Tuesd 10:30. Just to remind you - we have proj updates 2 times a week: Tuesdays, Thursdays
[7/15/2010 3:46:29 PM] alex dobrovolsky: Thanks you all! Bye!
[7/15/2010 3:46:35 PM] Роман Лахно: tnx. bb
[7/15/2010 3:46:41 PM] Alex Pivnyak: Thank you, see you soon
[7/15/2010 3:46:42 PM] Montira Rattanavijit: bye
Retrieved from "https://wiki.jaguarfreight.com/Cybertrax_2.1_Client_(project_plan)"
Personal tools