The Vila Project

Review

Nguyen Chi Hieu

15/12/2009
 Vila – Project introduction
• The largest store we (Boozt group, NI
Global, NI Vietnam, SmartOSC)
have ever taken so far
• Officially apply new technology to
adapt with Netsuite
• Huge push and preparation from
clients
• The “flagship” project that persuades
clients to continue with other
bigger projects
 The feelings

-Không, hôm qua ề

“..cu chuoi qua…”

“Em rềt rềt khó chều”

Lề
Không làm đâu!!!
 Wtf.. W h a t T h e y
.. Fo u n d ... ?
 Technology Problems
I. Marketing
- No. Don’t have
II. Product

- Limited knowledge of framework,

system design
- CodeIgniter is new to all members
- Limited support from Ras
-
 Technology Problems
III. Design
- Not much issues
- Re-standardize JS library
- No technical support
IV. Test

- Did not prepare good test cases to

cover all situations
- Want to improve on Stock Documents,
Data Documents and Test Case for
Checkout
 Process

I. Theoretical process vs. Actual
1. Marketing

Requirements  ềhecềlist  ềrepare marềeting

worề s  ề mplement worề s with other

teams
ềctual is different because no earlề

involvement in the proề ectề Late

information
ềgề Until ềềNovề no email regarding Vila

has been sent to ề arề etingề



2. Product
Requirement  Design  Kicề off  Tasề

allocation  ềề stem design  ề ode 

Test  Fix  Live
Actual is almost the same but stages are

not clear and overlappedA



3. Design



 Process (cont.)
II. Difficulties in implementing process
1.Marketing: Little preparation
2.Product:
Lack of information from clients + Too long

testing time  long waiting

time
ềề De s ig n ề

Little time to do anềthing

ềề T e st ề

ề ềan not implement since

step ềề Testers didnt have

time to test because
tasề s were finished too
lateA No time!!!

 Process (cont.)
III. Suggestion for a better


process
- Need overall plan of project shared to
everybody (M)
- Better collaboration tools, such as
google sites, wiki, shared docs...(P)
- Need time for code review (D)
- Need time (T)
 Communication
1. Marketing: Very good, very responsive clients, and
talkative team members
ề ềề ro d u c t ề
- ềlient communicationề verề
responsive
- ềross teamề Difficultề through
ề antisề chatề manager
- ềnside teamề Good communication
- Responsible team members
ềề De s ig n A

- A lient communicationADifficult
because it changes at different
stagesA and theA are not
consistentề Theề sometimes give
too much worề at the same timeề
No one point communication
- Aross timeA Good
- AnsideA Good
ềề T e st
 Others
1. Marketing:
Need information as early as possible

2. Product

- Priority are not consistent among teams

- Test is not good enough
 ềetter ềlanningề ềmprove Testề ềetter
evaluation
ềề De s ig n ề
- ềrief is not clear
- No ềroềect planề deadlines are verề
confusing
- ềad worề allocation
- ềant other groups to ềoin Design group
from beginning because Design alwaề s
start first
- ềant to have code review onceềweeề
ềề T e st ề
- Need ề weeềs – ề month ềust to test
- ềoders need to be more cooperative
 Problem needs
Solution
Problems Solutions Responsible

A common place sharing Project Plan ề will be in Mantis soon

Hieu + Nga

N o cle a r p ro je ct p la n Kick off across teams ề Agree on Time + Tasks + Priority

All - active
To o little tim e to d o th e jo b
Early involvements of all relevant parties All- active
C o n fu sin g ta sks a n d p rio rity
Actively and early inform Top managers situation and important issues
All - active

W e a k skills Proper training + allocation ề Long time Managers

N o Pro fe ssio n a l a ttitu d e Professional culture, hate negative thoughts

All - nature

e a r & fre q u e n tly ch a n g e d re q u ire m e n t

Educate clients Managers

H a rd to co m m u n ica te a m o n g te a m Schedule weekly cross team meetings Hieu + Managers