2012 bad camp-project management tools and organization-v4


Published on

As many Drupal development firms continue to evolve and mature, we often run into many management issues involved with the growing pains. One of the biggest of those issues is effective and efficient project management. In this session, we will discuss tools and processes to use throughout the development project and beyond, as well as best practices to help your organization go and stay agile. We will delve into Redmine as an example of a highly flexible, open source project management tool for supporting agile development and support.

We will cover tools in the following categories:

Communication and collaboration
Internal processes
Client reporting
Ticketing and task management for development and support

These tools help us:

Run all operational aspects of a 30+ person Drupal shop
Stay organized and agile
Communicate amongst team members
Remotely manage distributed, virtual teams
Document our work
Track our time
Provide clients with visibility and transparency

The goals of this session are to help attendees understand some of the tools that are out there to improve project management and how to execute on their project more efficiently by using the tools to support agile development.

Published in: Technology
1 Comment
  • Did you like this presentation? Check this free eBook on the 6 steps for practical project management http://www.slideshare.net/MindGenius/the-six-step-guide-to-practical-project-management
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Fly through
  • ok
  • ok
  • Needs more slides - should ask audience about use
  • NEEDS MORE SLIDES [Atlasian Jira, Confluence Jira GreenHopper Stash Fisheye TeamCalendars
  • Who owns this?, also, I think we should split up and make come comments
  • Who owns this? again, split this up into more slides
  • Andy can take that one - Needs more slides
  • Who owns this one?
  • Need to check with thea on quickbooks time entry
  • Who owns this one?
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • configuration
  • Issues aren’t just Issues, Sprints, Stories, Tasks
  • configuration
  • configuration
  • Source Integration Multiple team members Client Development Tied to tickets What is happening with Development
  • Every project has it – Standardized Clients Onboarding new resources Support/re-launching development
  • Retrospective is Johnnie
  • configuration
  • 2012 bad camp-project management tools and organization-v4

    1. 1. Project ManagementTools and Organization
    2. 2. About Andy • Presenter • Andy Kucharski • @akucharski • Promet Source • Founder • Engagement Management • @prometsource
    3. 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. 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. 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. 6. Four Quadrants Time Tracking, Commit Activity,Wikis, Documents Workflow ManagementStories, Issues, Git Status, Activity Repositories Stream
    7. 7. Existing Tools: Open Atrium (Drupal)
    8. 8. Existing Tools: Basecamp (User Friendly)
    9. 9. Existing Tools: Atlassian Products (Suite)Jira Confluence TeamCalendarsGreenHopper Stash Fisheye
    10. 10. Existing Tools: Assembla (SaaS Agile)
    11. 11. Existing Tools: Bugzilla (Bug Tracking)
    12. 12. Existing Tools: Mantis (Old School)
    13. 13. Existing Tools: Harvest (SaaS User Friendly)•[Harvest]
    14. 14. Existing Tools: FreshBooks (SaaS)
    15. 15. Existing Tools: QuickBooks (Accounting)
    16. 16. Existing Tools: GitHub (SaaS Developer Friendly)
    17. 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. 18. Promets High Level Requirements• Open Source• Secure• Extensible• Usability (for us and our clients)• Self Hosted
    19. 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. 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. 21. Redmine: Issue/Ticket Tracking
    22. 22. Redmine: Issue/Ticket Tracking
    23. 23. Redmine: Gantt
    24. 24. Redmine: Workflow for Issue Trackers and Roles
    25. 25. Redmine: Role-Based Permissions
    26. 26. Redmine: Source Code Repo Viewer and Diff
    27. 27. Redmine: Spent Time
    28. 28. Redmine: Workflow for Issue Trackers and Roles
    29. 29. Redmine: Customize Issue Trackers
    30. 30. Redmine: Customize Issue Status
    31. 31. Redmine: Customize Workflow
    32. 32. Redmine: Custom Fields on Almost Every Object
    33. 33. Redmine: Git Integration
    34. 34. Redmine: User Management
    35. 35. Redmine: Views/Queries Customization
    36. 36. Project and Agile Perspective Johnnie
    37. 37. Agile Organization of Stories and Tasks
    38. 38. Agile Story Board
    39. 39. Redmine: Git
    40. 40. Source Code Ties to Tickets
    41. 41. Project Information at a Glance
    42. 42. Retrospective Metrics
    43. 43. Retrospective Metrics
    44. 44. Client and Product Perspective Jay
    45. 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. 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. 47. Client Access and Roles
    48. 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. 49. Integration
    50. 50. Business Management Perspective Andy
    51. 51. Projects Activity View
    52. 52. Time Reporting
    53. 53. Time Reporting
    54. 54. Company Reports – Support Snapshot
    55. 55. Company Wide Resource Scheduling
    56. 56. Company Wide Resource Scheduling
    57. 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. 58. Questions?www.prometsource.com andy@promethost.com Twitter: @akucharski @PROMETSOURCE