Organized Crime: Weapons of Successful Project Management
|
|
- Ethel Horton
- 5 years ago
- Views:
Transcription
1 Organized Crime: Weapons of Successful Project Management
2 About Promet Source Director of Products Web & mobile app product building Strategy and requirements Agile practices and methodologies Previously IT management and consulting Enterprise CMS software Open source convert Product development at startups Jay Uhlinger 2
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 3
4 Organized Crime: Weapons of Successful Project Management 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 4
5 The Laundry List of Challenges Time tracking Bug reporting and tracking Document/file storage/sharing Client reporting/time reporting Issue prioritization Team collaboration Distributed teams Work in multiple time zones Story/effort/task estimations Knowledge sharing Joint dev teams with client Scheduling/calendaring Utilization Code review SCM integration Maintaining backlogs Onboarding resources Wiki/documentation Project progress tracking Gantt charts Burndown charts And more 5
6 Four Quadrants Wikis, Documents Project Documentation Management Information Time Tracking, Commit Activity, Workflow Management Stories, Issues, Git Repositories Project Management Updates Status, Activity Stream 6
7 Existing Tools: Open Atrium (Drupal) 7
8 Existing Tools: Basecamp (User Friendly) 8
9 Existing Tools: Atlassian Products (Suite) Jira Confluence TeamCalendars GreenHopper Stash Fisheye 9
10 Existing Tools: Assembla (SaaS Agile) 10
11 Existing Tools: Bugzilla (Bug Tracking) 11
12 Existing Tools: Mantis (Old School) 12
13 Existing Tools: Harvest (SaaS User Friendly) 13
14 Existing Tools: FreshBooks (SaaS) 14
15 Existing Tools: QuickBooks (Accounting) 15
16 Existing Tools: GitHub (SaaS Developer Friendly) 16
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 17
18 Promet's High Level Requirements Open Source Secure Extensible Usability (for us and our clients) Self Hosted 18
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 19
20 20
21 Redmine Main Features Multiple projects support Flexible role based access control Flexible issue tracking system Gantt chart and calendar News, documents & files management Feeds & 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 Multiple LDAP authentication support User self-registration support Multilanguage support Multiple databases support 21
22 Redmine: Issue/Ticket Tracking 22
23 Redmine: Issue/Ticket Tracking 23
24 Redmine: Gantt 24
25 Redmine: Workflow for Issue Trackers and Roles 25
26 Redmine: Role-Based Permissions 26
27 Redmine: Source Code Repo Viewer and Diff 27
28 Redmine: Spent Time 28
29 Redmine: Workflow for Issue Trackers and Roles 29
30 Redmine: Customize Issue Trackers 30
31 Redmine: Customize Issue Status 31
32 Redmine: Customize Workflow 32
33 Redmine: Custom Fields on Almost Every Object 33
34 Redmine: Git Integration 34
35 Redmine: User Management 35
36 Redmine: Views/Queries Customization 36
37 Project and Agile Perspective Johnnie
38 Agile Organization of Stories and Tasks 38
39 Agile Story Board 39
40 Redmine: Git 40
41 Source Code Ties to Tickets 41
42 Project Information at a Glance 42
43 Retrospective Metrics 43
44 Retrospective Metrics 44
45 Business Management Perspective Jay
46 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
47 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
48 Client Access and Roles 48
49 Manage Internal Projects and Products 49
50 Integration 50
51 Business Management Perspective Andy
52 Projects Activity View 52
53 Time Reporting 53
54 Time Reporting 54
55 Company Reports Support Snapshot 55
56 Company Wide Resource Scheduling 56
57 Company Wide Resource Scheduling 57
58 Gains from 360 View 58
59 Questions?
60 The Problem 60