Carpooling 505 proposal timeline

The project Carpooling 505 will not be developed in any complex or dynamic environment. For this reason, I decided to discard agile methodologies such as Scrum. Therefore, the chosen methodology for this project would be a classic sequential waterfall model. Besides, this project seems quite rigid, and I do not expect many changes from the original idea, these are two examples of points to take into account when you select a waterfall based methodology.

Notice that a maintenance phase should be included as part of the waterfall model, but we only have 12 weeks to be the project launched. For this reason, we assume the maintenance as a separate process after the website will be working properly.

The following two figures show a 12 week proposal timeline for the Carpooling 505 project:

Gantt diagram for Carpooling 505 (click to enlarge)

Task workflow network based on the Gantt diagram (click to enlarge)

Timeline description:

Group meetings: half an hour once a week. The main goal of these meetings is to keep track of the work done so far, and plan the next task for each member of the group. Suggestions and questions are always welcome on the group meetings.

Overview and planification: presentation, components of the team, first steps, ideas, suggestions, brainstorming, etc. 

Learn technologies: let's suppose that not all the members of the group know the technologies which will be used (Joomla!, PHP, MySQL, etc.)

Requirements: It includes elicitation, analysis, specification and management. The outcome will be a Software Requirements Specification.

System modeling (backend): designing of the application that will match the transportation requirements provided by the users. Joomla! database connections.

System modeling (frontend): Full website design.

System implementation (backend): development and implementation of the application that will match the transportation requirements.

System implementation (frontend): Website implementation using Joomla! CMS.

System integration: Embed backend application into the CMS (frontend). Web hosting and domain name.

Testing: Design a test plan. Depending on the requirements, the team will plan test such as unit test, quality test, integration test, load & stress test, etc.

Deployment and delivery: Launch website (domain name and hosting ready). 

Marketing: promotion on Media, advertising, etc. (if required)

Project start/end: "milestones"