Table of Contents

1. Project Overview
2. Project Governance
3. Project Progress
4. Effective and Appropriate Decision Making
5. Project Outputs
6. Appropriate Documentation

1. Project Overview

Trade Up is a software company that aims to solve the inefficiency of the labour usage in Australian construction companies. Trade-Up has several platforms that perform different functions to reduce costs among subcontractors, track resources and site productivity, automated timesheet logs, and site diaries. Code Repository

Client's Vision

Automate different components of current and future features on the existing platform to improve subcontractos' productivity, efficiency, and help them save and time money.

Project Value

As part of the Techlauncher team for Trade-Up, we will develop and provide a user friendly platform that can calculate employees' productivity, roster and allocate employees, and generate smart decisions with users' data within the context of productivity.

1. Subcontractors will be able to visualise the employee's rosters and timesheets online.
2. Subcontractors would take more than an hour to complete rostering, but with the component that we are offering to Trade-Up, they will be able to complete rostering within less than 30 minutes.
3. Trade-Up will have the ability to transfer created component from this project to future components.

2. Project Governance

2.1 Milestones

Milestone 1: Project Calendar

Sprint 1 (Week 3 - Week 4)
Research, look at Angular tutorials, find similar rostering examples.
Understand client's needs and wants.
Create roster UI design.

Sprint 2 (Week 5 - Week 6)
Start development for project calendar features.

Milestone 2: Employee Rostering

Sprint 3 (Week 7 - Week 8)
Link employee availability to the project calendar.
Start the project roster.

Sprint 4 (Week 9 - Week 10)
Develop project roster.
Set up final version of development.
Prepare for poster showcase.

2.2 Evidence of Decision Making

[Decision Making Sheet](https://docs.google.com/document/d/1rNijuexMwzqXhBVuOw6-GahGKt6cx17uGpKY4V0NzUo/edit)

2.3 Traceability of Actions

Sprint 1 (Week 2 - Week 4)

Sprint 2 (Week 5 - Week 6)

Sprint 3 (Week 7 - Week 8)

2.4 Team

Team Member	Role
Annalisa O'Sullivan	Client
Trent O'Sullivan	Client
David Roussov	Client
Hong You	Project Leader & Back-End
Tianhao Li	Technical Leader
Honggu Lin	Back-End Developer
Lin Peng	Front-End Developer
Jie Gao	Front-End Developer
Xinyu Hou	Front-End Developer
Qingyang Li	Front-End Developer

Detailed Information

• We have meeting with clients and discuss what we did and what we are going to do. If anyone have more questions, they can organise individual meeting time with the client. Then team members and client will create tasks on JIRA. We assign tasks on JIRA and members will work together on some related tasks.

• Team communication have been transitioned from Facebook to Slack where team have the opportunity to communicate with internal team members, client, tutor, and shadow team within one platform.

2.5 Development Approach

- The development approach we adapt is agile methodology. We hold weekly Saturday meetings consists of Scrum. The time of our weekly Scrum meeting is from 2pm - 3pm every Saturday at the provided workspace by Trade Up.

• Each team member answers 3 following questions:

1. "What they have done?"
2. "What were struggles and challenges encountered?"
3. "What will they be doing next?"

• When a new sprint starts, each task will be distributed among each team member from JIRA assigned by client and/or the team itself.

• Each sprint will last 2 weeks, where each member will work on the allocated task individually during the week and during team weekly meeting we come together and work on unresolved or difficulty tasks as a team.

2.6 Engagement With Stakeholders

- We have individual meetings and chats with client whenever any of us have questions (phone, video chat, meet in office)

• We have regular client meeting from 2pm - 3pm every Saturday.

• During our 1-hour client meeting, we ask client questions and update client the progress of our project.

3. Project Progress

Sprint 1 (Week 3 - Week 4)

sprint	sprint 1
Total sprints in this semester	4
Period	5th March to 18th March

• Learn Angular JS5
  

• Research on rostering system
  

• Display allocation in the project calendar per employee
  Research, look at Angular tutorials, find similar rostering examples.
  Understand client's needs and wants.
  Create roster UI design.
  

Sprint 2 (Week 5 - Week 6)

sprint	sprint 2
Total sprints in this semester	4
Period	19th March to 1st April

• Learn Angular JS5 for advanced function and prepare for further step
  

• Discuss, design and optimise rostering system
  

• Rebuild the Employee Availability Calendar with Angular JS5
  

• Display allocation in the new project calendar per employee
  

• Discuss with client about the features
  

• Add and change the features in the Employee Availability Calendar
  

• Discuss with client about the UI design about calendar
  

• Design the UI design about calendar
  

• Programming for front end, back end
  

• Connect front end and back end
  

• Find more info on current status

• More details and explainations on Audit Slides

Sprint 3 (Week 7 - Week 8)

sprint	sprint 3
Total sprints in this semester	4
Period	9th April to 20th April

• Complete employee availability
  

• Connect database with pages
  

• Retrieve required data for display
  

Sprint 4 (Week 9 - Week 10)

sprint	sprint 4
Total sprints in this semester	4
Period	23th April to 4th May

• Complete project roster
  

• Finalise two main components
  

4. Effective and Appropriate Decision Making

We make decisions during the client meeting and scrum meeting and the decision making documents are in Google Drive:

Decision Making Progress
React on Feedback

5. Project Outputs (Technical Artefacts)

5.1 Technical Depth of Outputs:

Week 3 to week 4

• status are in progress with research, UI design for the Epic 2 rostering system.
• Team members will have to figure out how to design and implement a rostering system with flexibility of moving employees from project to project.

Week 5 to week 6

• Decide the features and implementation approach about the rostering system.
• Final version of UI design of each part of the rostering system.Click to view UI design
• Mock up about each calender.Click to view mock up
• System design and report.Click to view
• Programming Employee Availability Calendar.Click to view code
• Database.Click to view

System Archictecture of The Protyping System/Environment

5.2 Technical Breadth of Outputs:

We tried and used different tools in order to optimise our output

• Angular5 for front end development
• Mysql for database
• Excel for mock-up for algorithms
• Grails for back-end
• JIRA for agile project management
• Slack for communication
• Github for landing page
• Google Drive for notes and documents

6. Appropriate Documentation

• Weekly Scrum Meeting
  Documentations 1
  Documentations 2
  
• Client Meeting
  Documentations 3
  
• Group Meeting Notes
  Click to view
• Algorithm In Our Project
  Click to view