Keeping Your Projects on Budget using GreenHopper and Tempo

Post on 19-Nov-2014

3.010 views 0 download

Tags:

description

Case study: This presentation shares the journey of Balfour's development team using JIRA Studio, including GreenHopper and Tempo. Michael shares how they use JIRA, the best practices they have learned, and the results they have achieved.

Transcript of Keeping Your Projects on Budget using GreenHopper and Tempo

#Summit112011.06.10 v6

Keeping your departmenton budget

Using GreenHopper and Tempo

Michael RainwaterDirector EngineeringTwitter: @mjrainwater

2#Summit11

Balfour

3

• Yearbooks• Letter Jackets• Graduation

Products• Class Rings• Retail Jewlery

• JC Penney• Walmart

• Professional Sports

• Team• Fans

Engineering

Balfour Organization

4

Yearbooks

Class Rings

Retail Jewelry

Jackets

Grad Products

MarketingInformation Technology

Dallas, TX

Austin, TX

Waco, TX

Louisville, KY

Mérida, MX

Taiwan

Operations

Infrastructure

Ecommerce

Systems

Engineering

Balfour Organization

5

Information Technology

Development

Quality Assurance

Manufacturing Support

Development• Java, PHP, MySQL• Project Management

Quality Assurance• Testing + Tech Support• Defect Management

Manufacturing Support• Publishing Support• Mfg Quality Control

Manufacturing

Operations

Balfour Roles

6

Marketing

ITManagemen

t

QualityDeveloper

Staying On Budget

• Operating Expenses (OPEX) vs Capital Expenses (CAPEX)

• Tracking capitalized expenses supports increased EBITDA

• Project expense tracking

• Labor is generally the largest project expense

• Client Billing

• Detailed records supports improved client billing

7

Michael Rainwater
What does it mean to be "On Budget"

Why JIRA?

• Balfour has been agile development for over 2 years.

• We were using Rally Enterprise Edition to support the engineering team, but did not have enough licenses for all of our other stakeholders.

• Last year, we decided to look more broadly for a new agile tool for the department.

8

First Problem To Solve

Objectives

1. Increase the number of users / licenses

2. Reduce annual total cost3. Option to bring in-house at a later

date

9

Selecting a new agile tool

Change is harder than improvement

• We knew we needed to change• Not just the tool The process

• But change isn’t easy• Battling Pre-conceived ideas• Previous tool strongly dictated the process (Right vs. Wrong)

• Developers satisfied with current system• Management not satisfied with the results

• Major Issues• Each iteration “Accepted” less than “Committed”• Completing work from previous iterations• Management reports were meaningless

10

“JIRA is a defect management system. I can see how it is useful for issue tracking. But we need an agile development tool.”

Development Manager

11

JIRA Skepticism

“Our accounting processes rely on the current system (Rally). We can’t adopt a new product.”

Accounting Analyst

12

Change Skepticism

How Does JIRA Studio Compare?

13

What We NeedDefect ManagementPer User CostsAnnual Total (50 users)

Backlog ManagementMetrics / DashboardWiki (Doc Management)Time Management

JIRA StudioExcellent

$150 / year$7,500

GreenHopperHighly

ConfigurableIncludedTempo

The Old WayExtra Fees$450 / year

$22,500

ExcellentSome Included

NoneExtra Fees

What makes the difference?

• Iteration Planning

• Release Planning

• Dashboards

• Custom Reports

• Timesheet Entry

• Accounting Integration

• GreenHopper Integration

• Custom Reports (with an API)

14

GreenHopper Tempo

GreenHopper Tips & Tricks

15

Needs

16

I need the tool to get out of

the way!

I need to organize by program and

sub-project

GreenHopper

I need to see all changes across

projects for the release

ITManagemen

tDeveloper

Workflows

Hierarchies

ClearCommunication

Marketing

JIRA + GreenHopper Delivers:

Custom Workflows

Problem #1

17

Defined

Balfour Engineering Process

18

Map Your Own Process

Developer

Quality

Scoped DevQA

ReadyDone

QA Rejected

Defined Scoped DevQA

ReadyDone

QA Rejected

Task Board Mapping = Workflows

19

20

5 issues – 24h5 issues – 24h

Agile Task Board

21

5 issues – 24h5 issues – 24h

Quality

I simply drag-and-drop to accept an issue!

Agile Task Board

22

5 issues – 24h5 issues – 24h

Quality

I simply drag-and-drop to accept an issue!

Developer

JIRA + GreenHopperLet us work our way.

Tools should not dictate the process

Agile Task Board

JIRA + GreenHopper Delivers:

Hierarchical Projects

Problem #2

23

Hierarchical Projects• Studio Balfour is a Program with many

projects.

• JIRA does not have project hierarchies

• You can achieve the same results by using both components in JIRA combined with GreenHopper context

24

Studio Balfour

AdBuilder

Ad BuilderManager

BaanIntegration IT

Management

Manufacturing

Operations

25

Components + Context = Hierarchy

26

ITManagemen

t

I can see work for the entire project, or

drill into sub-projects using GreenHopper

context

Components + Context = Hierarchy

JIRA + GreenHopper Delivers:

Clear Communication

Problem #3

27

Reporting Iteration Changes

• Need to report across all programs and projects

• Customers do not know or care about projects.

• By simply naming JIRA project revisions the same for each iteration, the built-in reports operate across projects.

28

Marketing

ITManagemen

t

Use Revision Naming Scheme

SY12 IT05

29

School Year

Iteration

Use Revision Naming Scheme

SY12 IT05

30

School Year

Iteration

Marketing

Cross Project Reporting is easy

with common names

Click to edit Master text styles

#atlassiansummit

Developers & QA Love JIRA + GreenHopper because:

• Custom workflows are simple using drag-n-drop

• System gets out of the way and lets me work

• Combined power of JIRA defect management with backlog management in GreenHopper

Developer

Quality

Click to edit Master text styles

#atlassiansummit

Operations and Management Love JIRA + GreenHopper because:

• Hierarchical views support roll-up for programs • Custom “Context” provides quick filtering• Dashboards provide quick project status

ManufacturingOperations IT

Management

Click to edit Master text styles

#atlassiansummit

Marketing Loves JIRA + GreenHopper because:

• Custom Reports from JIRA show all changes in all projects for a given release (aka iteration)

• Export to Excel for archiving• Personal Dashboards are relevant to each

person

Marketing

TempoTips & Tricks

34

ManufacturingOperations

35

I need time reporting to

be quick and painless

I need custom reports by user and

by project

Tempo NeedsI need charges

accounted correctly for projects and

customers

ITManagemen

tDeveloper

EasyTimecards

CustomReports

AccountingIntegration

JIRA + Tempo Delivers:

Easy Timecards

Problem #1

36

Simple Time Entry

37

Be Very Careful !!• These options operate

on the JIRA Issue.• If you choose “Delete”

it doesn’t just delete from your timesheet.

• The Delete Option here is VERY dangerous

Simple Time Entry

38

Developer

Quality

Why Managers Love It• Approval Workflow• Time corrections• Manager access for

terminated employees

Why Developers Love It• Enter time by week or

month• Enter time on the JIRA

issue directly

ITManagemen

t

Time Entry From Jira Issue

39

Time Entry From Jira Issue

40

Developer

Helpful Tip:Worklogs always add time, they don’t edit it.

JIRA + Tempo Delivers:

Custom Reports

Problem #2

41

Download this example: • Bitbucket

https://bitbucket.org/mjrainwater/• SourceForge.net

http://tempoplugin-xsl.sourceforge.net/

Custom Report Options

• Jasper Reports (http://jasperforge.org/)• This report tool is mentioned on the Tempo site, but there are

no directions. The XML from “tempo-getWorklog” did not work for me when I tried this.

• Build your own XSL• This works well if you are familiar with XSL. Even if you’re not,

you can use the samples I provide with simple modifications.

42

Example Custom Reports

43

1

2

3 4

Report 1: By User, Billing Key

44

Jenny.Price

Ray.Chu

Brian.May

Total Brian.May

Total Jenny.Price

Total Ray.Chu

Billing

KeyUser

Report 1: By User, Billing Key

45

Jenny.Price

Ray.Chu

Brian.May

Total Brian.May

Total Jenny.Price

Total Ray.Chu

Billing

KeyUser

ITManagement

Totals by employee let me manage my team

Report 2: By Billing Key, User

46

Total Tony Greene

Total Leon Chan

Total Laura Coats

Total Jay Keys

Laura Coats

Tony Greene

Leon Chan

Jay Keys

Billing

KeyUser

Report 2: By Billing Key, User

47

Total Tony Greene

Total Leon Chan

Total Laura Coats

Total Jay Keys

Laura Coats

Tony Greene

Leon Chan

Jay Keys

ManufacturingOperations

I can easily see billing information for non-billable

time as well as totalsfor each project / customer

Billing

KeyUser

Tempo Setup: Billing Keys

48

1

2

3

Tempo Setup: Billing Keys

49

Tempo Setup: Billing Keys

• Download Account Information

• Edit in Excel

• Import from CSV

• Project Mapping Editing Allowed

• Must have at least 2 Billing Keys in Project (even if only one is needed)

• This screen needs the most work! But is modified infrequently so I can live with it.

50

Project Accounting Reports

• Customization• Custom Date Ranges• Include/Exclude Internal

Issues• Print or Excel Export

51

Manufacturing

Operations

• Reports by:• User• Project• Team• Customer

JIRA + Tempo Delivers:

Accounting Integration

Problem #3

52

• This is just another report and varies by your own system requirements

• For Balfour, we created a CSV export. See the sample reports I provide for a simple CSV file. The columns can be easily adjusted.

53

Integration with Accounting

• This is just another report and varies by your own system requirements

• For Balfour, we created a CSV export. See the sample reports I provide for a simple CSV file. The columns can be easily adjusted.

54

ManufacturingOperations

Accounting integration with CSV eliminates data-entry errors and

is more reliable.

Integration with Accounting

Click to edit Master text styles

#atlassiansummit

Developers & QA Love JIRA + Tempo because:

• Timecard entry is quick and painless• Multiple options for entering time (by day,

week, or while editing a single issue)

Developer

Quality

Click to edit Master text styles

#atlassiansummit

Management Loves JIRA + Tempo because:

• Managers can enter time corrections when needed

• Simple approval process and team setup give managers tools they need

• Custom reports and export to accounting systems provide business intelligence for running the business

ITManagemen

t

Click to edit Master text styles

#atlassiansummit

ManufacturingOperations

Operations Loves JIRA + Tempo because:

• Cost accounting supports billing customers• Supports capitalized projects to minimize

operating expenses

58

Balfour keeps our engineering team:

• On Budget• On Time• Delivering the right scope

Using GreenHopper & Tempo

Summary

• Custom Workflows

• Hierarchical Projects

• Clear Communications

• Easy Timecards

• Custom Reports

• Accounting Integration

TempoGreenHopper

Questions

Download this example: • Bitbucket

https://bitbucket.org/mjrainwater/• SourceForge.net

http://tempoplugin-xsl.sourceforge.net/

Keeping your departmenton budget

Using GreenHopper and Tempo

Michael RainwaterDirector EngineeringTwitter: @mjrainwater

61

#Summit11