@pooja I’m sorry about how this played out. We were trying to be proactive for the libraries project, but when it got delayed we didn’t address the lack of work issue. With Falcon being a focused cell there isn’t any more work at the moment, and I suspect there may not be any more until after the current tagging project phase is wrapped up. I will be discussing this with Axim next week to see if we can find a way to make the work volume more predictable.
I think moving to Bebop would make sense for now, or at least helping Bebop or Serenity with their tasks until we have some more clarity about the next phases of Falcon’s work (hopefully next week). You should not end up in a similar situation as we are actively working to eliminate this issue and it’s ultimately our responsibility to ensure there’s enough work for you. Whichever cell you’re in, I think we should plan a synchronous call with the sprint planning manager for you and anyone else who doesn’t have enough work, to make sure we get it resolved at the start of the sprint. Because our current system doesn’t have a consistent mechanism to “notice” that you don’t have enough tasks unless you really make an effort to flag it (which you should also do please). We always have work on things like Contributions and Grove and Listaflow as a backup if there’s nothing else.
To reiterate what Jill said, this is nothing to do with your skills as a developer and in fact it’s because of your skills that we wanted you on Falcon when we thought a big important project was about to launch.