Project Management Details

We worked towards an Agile system of light documentation, simplified end-to-end user stories and detailed screen mock-ups containing high-level information only on user flows.

• Initial Planning – The overall scope of the project was outlined in this phase. High level workflows and the choice of algorithms were decided in this phase.

• Iteration Planning – The scope for each iteration was outlined. Detailed screen mockup were created in this phase. Screen mock-ups are documented in wiki.

• Requirements – The specific requirements were gathered, defined and documented into PBIs. The high level workflows were captured as a UML diagram. During this phase, we made assumptions on business values we were trying to deliver. We have constructed our requirements using user stories. PBIs were written in the format of “As a role , I can goal/need so that why ”. goal/need contains project specifications and why contains all the assumptions we collectively made. Workflow diagrams and screen mock-ups are documented in wiki.

• Analysis & Design – Software architecture and code is designed.

• Implementation – Construction of the actual code.

• Testing – Done during the Implementation phase, and done as QA & User Acceptance Testing at the end. Basic unit testings were automated. QA & User Acceptance Testing were done manually. The testing details and known bugs are documented in wiki under web testing cases.