Tell HN: Pivotal Tracker removes non-enterprise price tiers
Just got this email from VMware re Pivotal Tracker:
To our Pivotal Tracker customers,
Effective March 31, 2024, Pivotal Tracker “Startup” and “Standard” subscriptions will no longer be available for purchase and yearly auto-renewals will be canceled. Going forward, Pivotal Tracker will only be available for purchase as an “Enterprise” subscription. If you are interested in purchasing an “Enterprise” subscription to continue your Pivotal Tracker access, more information can be found here.
You will continue to have access to Pivotal Tracker until your yearly subscription expires. Upon expiration of your subscription you will be given 60 days access at no charge to ensure you have time to migrate any needed data, please review the download instructions here.
Regards, Tanzu Division
62 comments
[ 2.5 ms ] story [ 117 ms ] threadAnybody know of other task/project management software that has similar automatic velocity measurement and sprint planning functionality? It does so much for my productivity that I might just build something myself if there's nothing else around.
I'm still waiting for them to re-add features around capacity estimation by team member per project, a feature that was in Portfolio in 2017. At least they finally fixed the biggest issue I had with Portfolio, that the "save changes" view didn't have any filters.
1. Tasks have points 2. Sprints have duration 3. Points accomplished per sprint is velocity 4. Use the average velocity of the past few sprints to pull some number of tasks off the top of the backlog. Those are the tasks for the next sprint.
It makes sprint planning basically transparent. I just prioritise the backlog (sometimes lazily) and it keeps me pretty productive. It's almost gamification in a way, but not quite.
You could use Linear’s cycles and milestones but you probably don’t need any of that structure if you’re just working ticket by ticket.
If a PM wants to see how adding in just one more feature impacts the schedule, they can just drag the pointed story into the queue and see what gets pushed out to the next week.
If a developer goes on vacation, it is easy to see how that impacts the schedule cause you can subtract their average velocity.
Most people don't understand this killer feature of PT unless they've actually spent a bunch of time using it. It really enables you to do accurate project estimates, if you do it right.
Source: worked for cloudfoundry/pivotallabs
I put in a very random guess as to the points value of each request - nothing more than "trivial, easy, difficult, bastard-bloody-hell-shit-buckets-difficult".
I had Tracker set to work in "weekly sprints" - but they're not really sprints at all - it's just a unit of measure. Internally it averages the number of points completed over the last three weeks, uses that for an average velocity, then moves the date markers on the "backlog" list to match.
Then, when a client asked when something will be done, I could pretty accurately say "unless something urgent crops up, it will be '18th-24th March'" (where "something urgent crops up" means I insert a story at the top of the queue instead of at the end).
It's just a bad metric to optimize for.
Took me a few attempts writing it before I managed an appropriately civil tone. Ended up venting my frustration cryptically instead, by including a pic of the Enterprise D in the footer.
You should be running away
How did the export go?
Gotta find a new home for years of data as well.
I'm also scoping out Shortcut. Shortcut's interface feels a bit more familiar when coming from Pivotal. Their import process is even less polished though. For Pivotal you have to send an email to them, they reply with a template .csv that you have to ETL your data into.
Right now the jury is still out for us.
Also while Pivotal does offer an export, most alternatives don't appear to import from it. Though maybe that will change with this. And I suppose a middleman could be used.
I think the higher level project stuff is a little bit lacking, especially on the reporting side, but it’s definitely a leaner option than the incumbents.
Out of the box it is quite simple. Complexity comes from companies doing a lot of customisation.
Plus it's free up to 10 users.
I am always on the lookout for options since we're on Jira at $DAYJOB (and yeah it sucks), not that we'll ever change.
We were on Rally before which was okay. I've used things like Bugzilla and trac in the distant pass (for mostly solo things). Basecamp and trello a few times and even gitbug (again for a solo project).
I currently like Linear's ui/ux/approach (but I have not used it really). Shortcut and Plane.so look very similar.
You don't disrupt customer businesses like this just because you want to eliminate their pricing tier.
A more likely way to handle that situation is to grandfather in the current subscribers (for a much longer period), and only disallow new subscribers at that tier.
Grandfathering in is nice, but it really just pulls the bandage off slower in the long run.
(You'll alienate numerous small companies and startups, who will never buy a VMware product again, but only a small percentage of those will grow enough to become enterprise customers.)
A slow bandage pull in this case means giving giving a large window, for the customer to migrate on customer's own timeline, such as after completion of projects using the tool.
This is why the big vendors continue to exist. Sucks for us, but that's life.
Also, seems like the reputability of the vendor should be a factor in vendor selection. Why would one willingly use a vendor with an apparent mindset of "screw you, the moment it makes sense for me"?
(Maybe because a decision-maker didn't expect to personally be on the hook if the vendor also screws their company, in the same well-known ways it's screwed others? If screwing happens before the decision-maker moves on: "I'm shocked; shocked! Who could have foreseen this costly mess?")
Once you realize that you start to notice exactly the difference between companies that are selling to the people who will use the product, and those selling to their bosses, and those selling to the bosses' bosses.
But some people (who didn't understand the use of the software) had already already invested some face in the purchase.
Maybe also a bit of "nobody ever got fired for buying ___", and the enterprise sales rep seemed very reassuring. :)
I used PT for a project a few years ago and it was super underwhelming and janky. The fact that they would pull this... no surprise at all.
You can still download a backup of all your data (in Pivotal Tracker, click on the MORE menu, then on Export CSV).
I don't think their current team thinks about the product website very much. I think this has become even more true since the Broadcom acquisition, but even before that, they still had - and have! - a banner about being "here for you in these unusual times." It's from early COVID times.
As of this writing, their latest blog post is about _adding PayPal as a payment option._
It's from December, before the Broadcom deal closed. I think "add paypal" and "eliminate non-enterprise paid tiers" are different enough as product directions to illustrate the impact of Broadcom's thinking on the product.
For anyone coming to this conversation later, there's a site at talk.storytime.solutions dedicated to talking about Pivotal Tracker alternatives.