Changing how Falcon works

Thanks for pointing that out @Fox!

Moving the entire epic would be one option, but another (perhaps less disruptive) approach could be to just farm out the majority of tasks from it to Falcon and keep the epic itself in Bebop.

@samuel Maybe a little :slightly_smiling_face:

There’s two things happening for Falcon right now.

The cell’s last batch of projects is ending, so it’ll need additional work to fill its capacity starting soon.

At the same time, Falcon’s sustainability ratio was off target in Q1. So the cell should ideally focus on billable work in the coming weeks and months to improve the ratio1.

In terms of filling capacity, having some specific tickets available to pick up certainly helps in the short term. (Thanks for identifying some and posting about them here!) Falcon would also benefit from taking on some larger projects or chunks of work, though, as that would help keep the cell busy more reliably in the medium/long term.

When it comes to sustainability, any non-billable tickets that Falcon picks up in the short term (e.g. SE-6610, BB-10450, and BB-10510 from your list) should stay in the donating cell, and any billable tickets (e.g. BB-10728) would be transferred over. That would be the ideal scenario from Falcon’s perspective. However, we need to keep in mind that Bebop also needs to improve its sustainability ratio. So right now, the best approach would be:

  • For Falcon to only take over work from Bebop that (a) is billable and that (b) exceeds Bebop’s current capacity2.
  • For the corresponding tickets to be transferred over to Falcon.

1 Unless we end up changing sustainability targets.
2 Unlike in Q1, Bebop currently has no shortage of billable projects so giving away some work that exceeds the cell’s capacity in the short term shouldn’t have too big of an impact on the cell’s ability to increase its output of billable hours and improve its sustainability ratio in the remaining quarters of the year.

2 Likes