Project Management

Please login or join to subscribe to this thread

Vendor uses JIRA, organization doesn't - thoughts?

linkedin twitter facebook  
avatar
Anonymous
Situation: a software developer (vendor) for a project uses JIRA for managing sprints, stories, etc. However, the organization (customer) does not use JIRA and is not planning on implementing it any time soon.

Possible solutions?

1) Buy regular JIRA licenses for the duration of the project and then "export" everything to the organization's tools.

2) Vendor proposed to provide 1 JIRA license to the customer (for the Product Owner). The PO would be the only role in the organization able to update and interact through JIRA with the vendor.

3) Other options?

What are your thoughts? Anyone has encountered similar situations and how did you solved it?

Thanks!!
Sort By:
< 1 2 >
avatar
Suneel Kumar Nadella Director (Self Employed)| Manasai Services Pvt Ltd (Self Employed) Solihull, West Midlands, United Kingdom
The customer should assess and ensure that any project management tools are used in line with their technology stack or roadmap. Otherwise, you will have constraints as customer. Having said that if you are able to get generated reports in a meaningful form, you can get away as your service provider will do real time monitoring. Alternate approach could be is to get Jira access for identified SMEs of customer organisation.
avatar
Scott Theus Senior Project Manager and Agilist| BWX Technologies Euclid, Oh, United States
Mar 02, 2019 11:27 PM
Replying to Deryl Lee
...
If the vendor is workig for their customer then they should use the tools provided by their customer. Period

For future contracts, this issue should be defined in the contract. The suggested solutions (#1 or #2) could be defined and the cost of license included in the contract. Installation of JIRA requires certain technical configurations. These must be in place in order for the vendor or the customer to use JIRA.
I realize this is an older post, but fell the need to chime in on it.

I would argue that forcing the vendor to use the customer's PM tool exclusively could be disruptive to the project. With T&M the organization will be paying more for time the vendor spend learning a new tool, changing processes on the project team, licensing for the new tool, and more. They also risk delays in delivery due to the unfamiliarity of the tool and potential missed dependencies. With a fixed bid, these costs and risks will be written into the SOW.

The customer PM should first ask why they care about the tool the vendor uses; what value does it bring to the project for the customer?

If the vendor is providing regular status reports, keeping up on sprints, delivering the MVP for testing and validation regularly, and inviting the customer to participate in demos then it shouldn't matter what tool is being used.

The customer cares about timely deliveries, staying on budget, any dependencies they need to be aware of and track as part of the overall projects, etc. All of that can be done with the vendor using one tool and the customer another.
avatar
Latha Thamma reddi Sr Product and Portfolio Management (Automation Innovation)| DXC Technology Mckinney, Tx, United States
Depends upon the other customers, Greate post.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I'm glad I did it, partly because it was worth it, but mostly because I shall never have to do it again."

- Mark Twain

ADVERTISEMENT

Sponsors