Metrobank Remittance Systems

March 3, 2009

We are going on production, yes we are going on production. That is if everything THE SENIORS PLANNED turned out well. Luckily there are few bugs found on my module, except for features that is not in the Functional Specification Document. Come on, how can you expect a feature to be deployed, wherein in the first place it wasn’t asked implicitly or explicitly. Anyway, here are the things I want to say regarding my current project:

1. The senior developer should also get inputs from the junior developers SPECIALLY IN PLANNING. After all, JUNIOR DEVELOPERS are also part of the team.

2. Never spoonfeed. If you want your junior developer to enhance his skill, allow him to explore and make a research.

3. Identify what SDLC model is best suited for the project. Not a BAHALA na SYSTEMS. Also, establish sprints and milestone.

4. If there are change in system requirements, update everything including FSD. Don’t assume that everything is understandable. After all, documenting the systems is a must for all software projects.

5. Establish a mailing list for both the client and the team members. This will make sure everyone is part of the communication.

6. SENIOR SHOULD DO A PEER-TO-PEER CODE REVIEW. Make junior developers aware. Don’t just erase their code.