1 / 12

EWII and India Bart van Kuik Application Developer

EWII and India Bart van Kuik Application Developer. EWII. Elsevier Electronic Warehouse II Processes scientific literature, receiving it from suppliers and distributing it to clients. RAC cluster with more than 12 Tb data Various technologies: Forms, Workflow, Advanced Queuing, J2SE

isla
Download Presentation

EWII and India Bart van Kuik Application Developer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EWII and IndiaBart van Kuik Application Developer

  2. EWII • Elsevier Electronic Warehouse II • Processes scientific literature, receiving it from suppliers and distributing it to clients. • RAC cluster with more than 12 Tb data • Various technologies: Forms, Workflow, Advanced Queuing, J2SE • For the J2SE part, cooperation with India

  3. Java Team • Team: • Netherlands: Sjoerd Michels, Bart van Kuik • India:Gurdev Parmar, Raghu Narasimhamurthy • Tasks: • Netherlands:50% design, management and systemtesting50% programming, unittesting • India:100% programming, unittesting • Staff Augmentation a.k.a. body shop

  4. Communicatie • Sometimes through telephone, but mostly through instant messaging • Differences in communication: • Dutch people are open to the point of rudeness. Expect a more 'reserved' attitude. • Don't expect a straight No • Don't expect straight criticism

  5. Knowledge • The Indian IT jobmarket is moving • People's backgrounds vary somewhat • Don't assume a strong relational background • Do an introduction into the business backgrounds and technologies • Don't include queries in design, they take responsibility away from the developer

  6. Distance • Not exactly across the room • Be as accessible as possible; adjust daily schedule to match the Indian timezone and vice versa • Keep them up-to-date on: • Meetings • Happy or angry client • Deadlines • Gossip

  7. “It compiles, so it works.” Project joke

  8. Quality • Code reviews necessary: • Error handling: user error or exception? Pass exceptions with which the testteam can work • Logging: don't log the girlfriend's name, log IDs and whatnot • Keep administration tight: don't leave bugs open while they're actually fixed! • Give them a full development environment • Class ownership can then stay with one person • Bugs can be fixed by the class owner

  9. Remote working technology • Use one development environment; maintaining two costs too much time • When VPN is taken care of, test it with various tools including browser and instant messaging • When our Indian colleagues used VPN, they couldn't use instant messaging • VPN was too slow for Designer • Web Conferencing, remote desktop or VNC is NOT a substitute for VPN

  10. Conclusion • Solve the aforementioned problems • After some time at the project, a tight teamspirit will develop • Hearthily recommended!

  11. Q & Q U E S T I O N S A N S W E R S A

More Related