After much anticipation, the Citi-UCL collaboration project was finally launched on the 30th of April 2007. We had our preliminary meeting at Canary Wharf – Citi’s Investment Banking headquarters in London. This was followed by another meeting, at UCL, to further discuss the project scope, team organization structure and grading criteria.
We all decided to meet up after the project brief and proactively take the first steps towards launching the project. The Project Manager – Andy and Technical Lead – myself, were chosen to lead the team.
Since most of the team were fairly new to actually taking on and executing a project, I stressed on the importance of selecting and then adhering to a software development methodology (process) that would ensure that we engineer the project in an organized manner.
We swiftly began our project initiation activities,
- Formulating the team - dividing the team into 3 sub-teams. Each sub team was responsible for the requirement gathering, design and implementation of their sub-system.
- Researching and then defining a suitable software development process that would suit our project size and experience, and wouldn’t be that difficult to follow.
- Define templates that the team would use so that, all deliverables would be consistent.
- Define a problem statement, so that we could validate and clarify our understanding of the project, and act as a mechanism to trigger more discussion around requirement gathering
No comments:
Post a Comment