If you had to use Jira, how would you set it up for ShapeUp? I realize this isn’t ideal, of course, but it’s pretty common for Jira to be the preferred project management tool for an entire organization, with individual teams unable to choose to use something else.
Disclaimer: I’m shooting from the hip here
If you’re projects are set up using Jira next-gen I would:
- Disable backlogs
- Use confluence for pitches
- Use boards as the hill chart a column per position on the hill?
I tried setting up Jira for Shape Up. The one thing I could not manage to do is recreate the way we make to-do lists for the scopes in Basecamp and capture discovered tasks beneath them as we go.
Thanks for the insight @jerrylopez!
Ryan, how did you map concepts between ShapeUp and Jira? Best I can come up with is:
Project <–> Jira Epic with link to Confluence page for pitch/kickoff, as @jerrylopez noted
Scopes <–> Jira Issues
Discovered tasks <–> Jira Subtasks within each Issue
Subtasks in Jira are obviously not as lightweight and easy to work with as to-dos in Basecamp (because it’s Jira, and none of it is lightweight and easy to work with, ugh), but this seems like it would work? Were you running into something else that made this unfeasible?
I remember feeling skeptical that Issues and Subtasks were lightweight enough to work for managing scopes — which are captured and changed as we learn, not planned up front. But please give it a shot and let us know how it goes.
We are just about to run our first cycle and have been running Jira for many years, so we’re basically stuck with it for now. Our plan is this:
- No backlog. The Jira project is cleared after each cycle.
- One batch = one issue with a squad assigned to that issue
- We will install a plugin called Issue Checklist Pro which adds a pretty light weight checklist to the issue where we can group items in scopes in a similar way as it’s shown in ShapeUp.
I’m happy to give you guys an update once we’ve gotten started.
We still have to figure out how to represent the Hillcharts in Jira. Initially we are just not going to use hillcharts. One idea that I’ve had is to say that one batch is one epic and that the scopes are issues (with the checklist plugin on them). This would not give a single overview over how the scopes are going as how many checklist items are left. But maybe that’s an irrelevant number to look at?
Using Confluence for pitches sounds smart. We are planning to try out Trello, but I’m afraid that Trello is simply too lightweight to present the pitches in a good way. Any one have any experience of that? (Sorry if that’s of topic)
I think I have enough experience with both to recommend something here.
- Set up a scrum project. This is your “team”
- Make sure epics, stories, tasks, and subtasks are enabled
- Write pitches somewhere like confluence
- Set up columns on the board to represent the hillchart. Something like ready, figuring things out 1, figuring things out 2, ready to make it happen, making it happen 1, making it happen 2, done (sorry not feeling creative on names for those). The ready to make it happen column is important for teams that would prefer to get all scopes up the hill first by doing all the hard stuff.
- Epics are your projects. Create each epic at the beginning of the cycle that will be worked on. Close epics at the end of each cycle.
- The backlog is the unscoped work for the cycle, the team should put discovered tasks in the backlog during the cycle before scoping
- Stories are scopes. Assign the stories to an Epic and move them into the sprint. Convert tasks in the backlog to subtasks of the scope stories. Those can then be tracked on the hillchart board. Instead of moving sub tasks across the board, click the story (scope) and change it’s status accordingly. Sub tasks can move directly from ready to done as needed
This is what it looks like for us at the moment.
Epic is the cycle work. Right now I have it grouped by Epic with only 1 showing. Custom issue type of scope indicated in red. In this case, “Split public / private embed API” and “New pricing plan for basic.” Clicking “+ Create issue” adds a new scope.
Subtasks are discovered work:
Pitches, ideas, and collaboration happen in notion and elsewhere. It should only land in Jira when we’ve committed/bet on it.
Great suggestions everyone! Lots of options to try out here.
For what it’s worth, I just tried adding a subtask in Jira, and this thing wants me to fill out a 16 field form just to add a little subtask! Now I know what @rjs was talking about. That’s so much more involved than I remember.
Hey @kevinsmith here’s what it looks like for our setup.
It’s heavy handed for editing or deleting, but adding is fairly quick. Hope that helps.
Oh yeah, that’s a lot better. I wonder if that’s only available in “next-gen” Jira.
Could be a configuration thing as well. Jira can be setup to become a nightmare of required fields and the likes.