- Andy Kucharski presented on using Redmine for integrated project management, client communication, and business management. - Redmine is an open source project management tool that supports features like issue tracking, time tracking, wikis, project planning and more. - It allows organizations to manage projects, clients, and internal operations through a single system, providing benefits like increased efficiency, visibility, and collaboration. - The presentation provided examples of how Redmine can be used from the perspectives of project management, client management, and business management.

1. Project Management
Tools and Organization

2. About Andy
• Presenter
• Andy Kucharski
• @akucharski
• Promet Source
• Founder
• Engagement Management
• @prometsource

3. About Promet
• Focus on open source software and Drupal
• Founded in 2003
• Offices in the US (Chicago, San Jose)
• Some of the faces of Promet…

4. Objectives
• Understand project management and organizational challenges
• Review some of the tools out there being used for project
management, client communication, and business management
• Learn how to execute more efficiently and be agile by using an
integrated tool set
• Examples using Redmine for:
• Agile project management
• Client management
• Product management
• Business management

5. The Laundry List of Challenges
• Time tracking • Scheduling/calendaring
• Bug reporting and tracking • Utilization
• Document/file storage/sharing • Code review
• Client reporting/time reporting • SCM integration
• Issue prioritization • Maintaining backlogs
• Team collaboration • Onboarding resources
• Distributed teams • Wiki/documentation
• Work in multiple time zones • Project progress tracking
• Story/effort/task estimations • Gantt charts
• Knowledge sharing • Burndown charts
• Joint dev teams with client • And more…

6. Four Quadrants
Time Tracking,
Commit Activity,
Wikis, Documents
Workflow
Management
Stories, Issues, Git Status, Activity
Repositories Stream

7. Existing Tools: Open Atrium (Drupal)

8. Existing Tools: Basecamp (User Friendly)

9. Existing Tools: Atlassian Products (Suite)
Jira Confluence TeamCalendars
GreenHopper Stash Fisheye

10. Existing Tools: Assembla (SaaS Agile)

11. Existing Tools: Bugzilla (Bug Tracking)

12. Existing Tools: Mantis (Old School)

13. Existing Tools: Harvest (SaaS User Friendly)
•[Harvest]

14. Existing Tools: FreshBooks (SaaS)

15. Existing Tools: QuickBooks (Accounting)

16. Existing Tools: GitHub (SaaS Developer Friendly)

17. The Problem
• Many tools address individual problems very well, but do not
solve multiple problems at one time
• Having one place where you can integrate as many pieces as
possible provides significant gains in efficiency, quality, and
collaboration

18. Promet's High Level Requirements
• Open Source
• Secure
• Extensible
• Usability (for us and our clients)
• Self Hosted

19. Redmine Overview
• Flexible project management web application
• Open Source
• Ruby on Rails
• Plugin style extensions (think modules)
• Active (5300+ repos related to Redmine on GitHub)
• Used by wide variety of people and organizations
• ChiliProject community fork

20. Redmine Main Features
• Multiple projects support
• Flexible role based access control
• Flexible issue tracking system
• Gantt chart and calendar
• News, documents & files management
• Feeds & email notifications
• Per project wiki
• Per project forums
• Time tracking
• Custom fields for issues, time-entries, projects and users
• SCM integration (SVN, CVS, Git, Mercurial, Bazaar and Darcs)
• Issue creation via email
• Multiple LDAP authentication support
• User self-registration support
• Multilanguage support
• Multiple databases support

21. Redmine: Issue/Ticket Tracking

22. Redmine: Issue/Ticket Tracking

23. Redmine: Gantt

24. Redmine: Workflow for Issue Trackers and Roles

25. Redmine: Role-Based Permissions

26. Redmine: Source Code Repo Viewer and Diff

27. Redmine: Spent Time

28. Redmine: Workflow for Issue Trackers and Roles

29. Redmine: Customize Issue Trackers

30. Redmine: Customize Issue Status

31. Redmine: Customize Workflow

32. Redmine: Custom Fields on Almost Every Object

33. Redmine: Git Integration

34. Redmine: User Management

35. Redmine: Views/Queries Customization

36. Project and Agile Perspective
Johnnie

37. Agile Organization of Stories and Tasks

38. Agile Story Board

39. Redmine: Git

40. Source Code Ties to Tickets

41. Project Information at a Glance

42. Retrospective Metrics

43. Retrospective Metrics

44. Client and Product Perspective
Jay

45. Manage Everything for a Client
• Keep all info for a Client’s projects in one place
• “Product” lifecycle approach
• Leverage project hierarchy in Redmine
• Client account (top level project)
• Support (subproject)
• Main Site Migration Project A (subproject)
• Intranet Project B (subproject)
• Ecommerce Integration Project C (subproject)

46. Use Project Templates
• Copy existing project
• Create project templates
• Types of projects (agile,
audits, support…)
• Prefab issues/tasks
• Common info structure in wiki
• Continuous improvements

47. Client Access and Roles

48. Manage Internal Projects and Products
• All projects in Redmine managed in same way
• Make onboarding whether internal or external consistent
• Internal projects and tasks available for free time
• Products that we are building (product management)
• Rapid scoping and estimating new projects
• Our own Redmine improvements
• Private Notes

49. Integration

50. Business Management Perspective
Andy

51. Projects Activity View

52. Time Reporting

53. Time Reporting

54. Company Reports – Support Snapshot

55. Company Wide Resource Scheduling

56. Company Wide Resource Scheduling

57. Gains from 360 View
•No Bench time policy – everything is a project
•Ability to better scope projects
•Invoicing, Burn Rates, time analysis
•Ability to integrate with third party tools and
extend
•Consolidation of all info into one system
•More information
•Easier Access
•Data Mining

58. Questions?
www.prometsource.com
andy@promethost.com
Twitter: @akucharski
@PROMETSOURCE