akio
Uploaded by
23 SLIDES
398 VUES
240LIKES

Effective Project Management using TRAC: Streamlining Issue Handling and Communication

DESCRIPTION

This project overview focuses on the use of TRAC as a project management tool, highlighting its role in managing communication, issues, and ticketing. It explains the workflow involved in handling issues, including components like ticket ownership, priority settings, and milestones. Participants are encouraged to engage with the project documentation on the wiki, familiarize themselves with coding standards, and participate in code reviews. The aim is to streamline project processes, enhancing team collaboration and productivity while maintaining high-quality coding practices.

1 / 23

Télécharger la présentation

Effective Project Management using TRAC: Streamlining Issue Handling and Communication

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Workflow Harry<harry@sparcs.org>

  2. Trac • Review board Contents

  3. Horrible situation

  4. Cost of Communication

  5. Project Management Tools

  6. Project Management Tools

  7. We use TRAC

  8. 일감 • Unit of jobs Ticket / Issue

  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 Ticket / Issue

  11. General workflow

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

  13. Milestone (Library)

  14. Milestone (Wheel)

  15. Milestone (Arara)

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

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

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

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

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

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

  22. Review board

  23. Review board

More Related