1. Project Workflow Harry

2. Contents Trac Review board

3. Horrible situation

4. Cost of Communication

5. Project Management Tools

7. We use TRAC

8. Ticket / Issue 일감 Unit of jobs

9. Ticket / Issue

10. Reported by ◦Who issued the ticket Owned by ◦Who is responsible for the process of the ticket Priority Milestone ◦To be explained later Component ◦Which part the ticket is related to

11. General workflow

12. Milestone 이정표 Release Regular time interval Arara: ??

13. Milestone (Library)

14. Milestone (Wheel)

15. Milestone (Arara)

16. Wiki Documentation is extremely important Get familiar with wiki grammar Feel free to write on wiki ◦If you did something wrong, just UNDO!

17. What’s on wiki? Project roadmap Developers Setting up development environment Program code explanation Features of the program (Backlog) History of the project ALL ABOUT THE PROJECT

18. Found a bug? Ticket already exists? Issue a ticket Found a bug Done Y N

19. Assigned a ticket? B assigned a ticket to you Can be separated? Makes sense? Done Resolve as won’t fix Reassign to B Work Resolve as separable Issue new tickets Y N N Y

20. Code review A code segment may be harmful ◦Violating coding conventions ◦Bad coding habits ◦Duplicate codes ◦Ambiguous naming ◦… Codes need to be reviewed before reflection

21. Code review Strong ◦Reflected codes are always `good’ ◦Newbies can learn from the trained advisors Weak ◦Slows the project ◦Committers become timid ◦If reviewers are busy…

22. Review board