You can use the latest released iTrust app in HERE
Git Workflow Guideline
The green team consists of these brilliant members.
| Name | Experiences | Iteration 1 | Iteration 2 | Iteration 3 | Iteration 4 |
|---|---|---|---|---|---|
| 정인교 | Java, Intellij | 1st Presenter | Team Leader | QA Leader | |
| 김희곤 | Java, Unity | Team Leader | Planning Leader | ||
| 조성원 | Android, Eclipse, Unity, Django | QA Leader | Planning Leader | ||
| 김도혁 | PHP, Web Hacking | QA Leader | Planning Leader | Team Leader | |
| 정유철 | Java, JavaScript, Web | Team Leader | QA Leader | ||
| 홍기재 | Java, JavaScript, ExtJs, Intellij | Planning Leader | 2nd Presenter |
We assigned pairs in each iteration.
| Pairs | Iteration 1 | Iteration 2 | Iteration 3 | Iteration 4(1) | Iteration 4(2) |
|---|---|---|---|---|---|
| Pair 1 | 정인교, 홍기재 | 김희곤, 홍기재 | 조성원, 정유철 | 정인교, 정유철 | 김도혁, 정인교 |
| Pair 2 | 김희곤, 조성원 | 김도혁, 조성원 | 정인교, 김희곤 | 김도혁, 홍기재 | 김희곤, 정유철 |
| Pair 3 | 정유철, 김도혁 | 정유철, 정인교 | 홍기재, 김도혁 | 조성원, 김희곤 | 조성원, 홍기재 |
We used gantt chart to manage our plan and schedule.
We estimated our plan based on how much time we have for each iteration and evaluated how much we achieved. This will help us to alert where we are in the project and to manage our schedule.
| Plan | Iteration 1 | Iteration 2 | Iteration 3 | Iteration 4 |
|---|---|---|---|---|
| Total SP Remaining | 62 SP (0 %) | 51 SP (18 %) | 21 SP (66 %) | 0 SP (100 %) |
| Desired Features | UC 39, 41, 92 user stories | Remaining tasks of iteraion 1 and UC 88, 89, 90 user stories | Remaining tasks of iteraion 2 and UC 91, custom user stories | Testing, coverage, error fix, refactoring |
| Desired SP | 17 SP | 36 SP | 21 SP | 0 SP (+ alpha) |
| Expected Velocity | 17 SP / 1 iteration | 36 SP / 1 iteration | 21 SP / 1 iteration | - |
| Actual Velocity | 11 SP / 1 iteration | 30 SP / 1 iteration | 21 SP / 1 iteration | - |
| Time we can spend | 51 Hours | 98 Hours | 66 Hours | (Flexiable) |
| Time per SP | 4.64 Hour / 1 SP | 3.27 Hour / 1 SP | 3.14 Hour / 1 SP | - |
| Duration | 1 iteration | 1 iteration | 1 iteration | 1 iteration |
These are main use cases that we have to implement in iTrust. ( -> ) means changed story points comparing real work.
| Use Case | Comment | User Stories | Story Points |
|---|---|---|---|
| UC39 | Theme: View Transaction Logs. See details here | See details here | 4 |
| UC41 | Theme: Reminder. See details here | See details here | 6 |
| UC88 | Theme: Orthopedic Office Visit. See details here | See details here | 8 -> 13 |
| UC89 | Theme: Physical Therapy Visit. See details here | See details here | 11 |
| UC90 | Theme: Orthopedic Surgery. See details here | See details here | 11 |
| UC91 | Theme: Patient View. See details here | See details here | 5 |
| UC92 | Theme: Schedule Physical Therapy/Orthopedic Appointment. See details here | See details here | 7 -> 10 |
| Our Own UC | Theme: Room Change Request and Acceptance. See details here | See details here | 10 |
These are possibly occurred risks that team members have to keep in mind of.
Anaylsis is based on the method named 'Failure Mode and Effects Analysis(FMEA)'.
Higher RPN implies that those risks have high risk.
| Risk | Possiblity of Occurence | Impact of The Loss | Possibility of Detection | RPN(Risk Priority Number) | Mitigation Strategies |
|---|---|---|---|---|---|
| A member cannot attend a general meeting or a pair programming meeting, but can work in remote. | 2 | 3 | 1 | 6 | Use TeamViewer. |
| A member cannot attend a general meeting or a pair programming meeting, and cannot work in remote. | 2 | 4 | 2 | 16 | Move a meeting schedule temporarily. |
| A scheduled meeting cannot be made by inevitable accident such as natural disaster. | 1 | 4 | 6 | 24 | Move a meeting schedule temporarily. |
| A member gets ill. | 1 | 4 | 5 | 20 | Keep meeting going and inform him of meeting contents. |
| A member drops out of the class because of some reasons. | 1 | 5 | 6 | 30 | Report to the professor. |
| A member pushes his code directly to remote master in Gitlab. | 3 | 4 | 3 | 36 | Let QA leader make revert commit. |
| A computer breaks down for some mysterious reasons. | 1 | 5 | 6 | 30 | Reimplement of corresponding parts. |
| A professor's computer(Remote repository) breaks down for some mysterious reasons. | 1 | 4 | 6 | 24 | Repush one of our local repository to Gitlab again. |
This is our weekly meeting schedule and can be rearranged in certain situation like exam week.
Every Sunday, 10:30 P.M.
These are meeting logs summarizing our dicussions in every meeting.
- 1st Meeting
- 2st Meeting
- 3rd Meeting
- 4th Meeting
- 5th Meeting
- 6th Meeting
- 2nd Demo
- 7th Meeting
- 8th Meeting
- 3rd Demo
- 9th Meeting
- 10th Meeting
These are presention files presented at each demo.
These are ppt sources that we used in planning.