Academic project developed as part of the Diploma of Information Technology at TAFE NSW (Sydney, Australia).
A complete IT project management exercise covering software development methodology, project planning, source control, team collaboration and risk management — applied to the development of an online shopping portal for Sports Warehouse.
As a project manager at Gelos Enterprises, this project involved planning and managing the development of an e-commerce portal for Sports Warehouse — a sports equipment retailer in NSW, Australia.
Unit assessed:
- ICTPRG530 – Manage Projects Using Software Management Tools
Project scope:
- 6-month timeline
- Budget: $150,000
- Team of 10 (project manager, 3 developers, 1 UI designer, 1 business analyst, 2 testers, 2 stakeholders)
| File | Description |
|---|---|
20250522_SportsWarehouseECommerce_ProjectPlan_JulioF_v1.pod |
Project plan v1 – MS Project file |
20250529_SportsWarehouseECommerce_ProjectPlan_JulioF_v2.pod |
Project plan v2 – updated with delays and risk adjustments |
20250529_SportsWarehouseECommerce_ProjectPlan_JulioF.mp4 |
Video evidence of project plan and collaboration |
20250605_SportsWarehouseECommerce_ProjectPlan_JulioF.docx |
Full assessment submission document |
Software Development Methodology: Agile
- Chosen for its flexibility, iterative sprints, and stakeholder engagement
- Supports fixed budget and 6-month deadline
- Prototype included to validate requirements early
Project Management Software: Microsoft Project
- Gantt chart, sprint planning, resource management
- Baseline snapshots to track planned vs actual progress
- Integration with Microsoft 365 (Teams, Excel, Outlook)
Source Control System: GitHub
- Version control for a team of 8 active developers
- Pull requests, code reviews, Agile Kanban boards via GitHub Projects
- CI/CD integration and branch management
Collaboration Software: Microsoft Teams
- Daily stand-ups, file sharing, channel-based communication
- Integration with SharePoint, OneDrive, and Microsoft Planner
- Compliant with Gelos Enterprises Digital Communications Policy
Project Plan (MS Project)
- Defined project phases, task types, milestones and dependencies
- Gantt chart covering all 6 months of development
- Resource allocation across all team roles
Source Control Procedures
- File naming convention:
YYYYMMDD_ProjectName_DocumentName_AuthorInitials_vX.ext - Folder structure organised by project phase and activity
- Version numbering: Major (v1, v2) for breaking changes; Minor (v1.1, v1.2) for features
- Workflow: Draft → Review → Approve → Commit
Collaboration Environment
- Microsoft Teams channels set up for each team role
- Document sharing and version tracking via OneDrive
- Daily check-ins and weekly status reports
Scenario 1: Project Delays
- Server delivery delayed by 2 weeks → development moved to local workstations
- Potential banking integration added 25 extra days to timeline
- Team members sick → 2-day delay each
- Project plan updated with revised milestones and baseline comparison
Scenario 2: Version Control
- First website version uploaded to GitHub following naming and commit conventions
- Meaningful commit messages documented for each push
- Branch strategy applied for login feature development
Scenario 3: Team Collaboration
- Daily check-in conducted via Microsoft Teams
- Delay communicated to all stakeholders with updated project plan shared
- Source control usage and collaboration best practices discussed
- MS Project – Project planning, Gantt charts, resource management
- GitHub – Source control, version management, code collaboration
- Microsoft Teams – Team communication, file sharing, daily stand-ups
- Agile Methodology – Sprint planning, backlog, iterative development
- Microsoft 365 – Word, Excel, OneDrive, SharePoint
Completed as Assessment Event 2 of 2 for the unit ICTPRG530 — Diploma of Information Technology at TAFE NSW, Sydney, Australia (2025).
Julio Cesar da Silva Filho | LinkedIn