Are there any roadmap/list/plan for Bitcoin Cash development?

BitcoinABC

Increase default block-size limit, and move towards adaptive block size limit
Move toward canonical transaction order, perhaps removing transaction ordering consensus rule as a first step.
Improved Difficulty Adjustment Algorithm
Re-activate some deactivated Opcodes, and move toward adding protocol extension points to facilitate future Opcode upgrades
BitcoinUnlimited see bottom of the page

Adjustable Block-size Cap (ABC): The BU client allows node operators and miners to easily adjust the size of blocks they accept without having to restart their node or recompile new executables.
Xtreme thin blocks (Xthin): Bitcoin Unlimited was the first client to fix the inefficiency in the core Bitcoin code that resulted in transactions often being received twice by each node. BU's solution improves block propagation times and reduces the number of required bytes.
Parallel validation: The BU client enables nodes to validate more than one block – along with new incoming transactions – all at the same time. This neutralizes an existing attack vector while improving the network’s performance.
nChain

Massive Scaling. The Developer and Testing Groups commit to enable massive scaling of the Bitcoin Cash network, so that Bitcoin Cash becomes a fast, low-fee, global peer-to-peer electronic cash system.
Regularly-Scheduled Protocol Updates. To achieve that vision, the Developer and Testing Groups will schedule Bitcoin Cash protocol upgrades on a planned date every 6 months – beginning May 15, 2018 and November 15, 2018. This regular schedule gives the Bitcoin Cash user community significant advance notice to prepare for protocol upgrades in an organized manner.
May 15, 2018 Protocol Upgrade. Under the semi-annual schedule, the next protocol upgrade is planned for May 15, 2018. nChain is pleased to see that the Developer and Testing Groups will work towards incorporating the following features, to the best extent possible:
Block Size: Increase the default block size limit, with a goal of 32MB for the next upgrade. nChain will support appropriate testing with the Developer and Testing Groups, which will help determine the increased block size. Whatever size is ultimately decided, nChain is pleased to see a commitment to larger blocks. Additionally, for a future protocol upgrade, the Developer and Testing Groups intend create an adaptive algorithm to determine the maximum block size.
Difficulty Adjustment Algorithm: Implement further improvement to the DAA to continue stabilizing mining on the network;
Op Codes: Begin the process to restore op codes that were previously disabled in the legacy BTC chain (now SegWit)
Transaction Order in Blocks: Remove the current restriction on transaction order in blocks, and replace it with a canonical order by transaction ID.
For the next following upgrade (on November 15, 2018) and subsequent upgrades, the Developer and Testing Groups will confer on what features to include.

Extension Points. The Developer and Testing Groups intend to use known extension points to introduce new features into Bitcoin Cash. To date, there have only been 2 ways to upgrade the Bitcoin (or Bitcoin Cash) network, commonly known as a hard fork or a soft fork. Both mechanisms have their own shortcomings. Soft forks are activated by miners and there is no way for node operators to voice their opinion nor oppose on the fork. On the other hand, hard forks require all users to upgrade in lockstep and creates risk at time of activation. Extension points provide a new, and easier, third method to implement protocol upgrades. (Extension points are a method by which nodes implement new Opcodes and other changes that are not, strictly speaking, hard or soft forks. This is accomplished by introducing an indeterminate state that is neither “valid” nor “invalid” but temporarily valid and dependent upon proof of work using a form of emergent consensus.) The Developer and Testing Groups will evaluate when, and how, to begin using extensions points for the upgrade process.
New BCH Address Format. The Developer and Testing Groups will work on a new address format for BCH, in order to prevent the risk of users mistakenly sending BCH to a BTC address, and vice versa.