Changing how Falcon works

[ChrisChV (Christofer Chávez)]

@navin

This seems reasonable, Falcon should be able to handle 2 or more epics based on the size in parallel without any issue.

I agree with @navin, Falcon can handle more than one epic; we’ve done it before. We can handle an internal epic as @rpenido proposed in Replacing JIRA at OpenCraft.

@rpenido

If this is the root cause, I think we have a good business opportunity for our Product/UX team. How can we foster that?

@braden

Good point. I hope the current work on the Learning Paths project can help demonstrate that.

@braden

Yes, after the course outline, we will likely tackle an epic(s) involving workflow improvements (logs / change history, better publish workflow, and/or bulk actions). And then after that, and probably after Verawood, would likely be something related to Course Templates (not libraries related but still modular learning). But there will probably be gaps between these projects.

I think the root cause is that Schema is completely focused on the current epic, and it doesn’t work well or on time in the next epic. If there are other epics after the course outline, isn’t there a way to create an opportunity for our Product/UX team to work on them in parallel? That way, Schema would focus on the current epic while our Product/UX team works on the next one.