Updated timelines for Omni Features

Sharing this document to inform that some of the features Omni team is working on are a little  behind schedule. We understand that as our customers, you might have planned your future plans on these features in your Omni software. We apologize for the delay. 

In order to address these unforeseen circumstances, We have also taken some immediate actions and some planned some future actions so such delays can be avoided in future 

Please do not hesitate to contact the support team if you have any questions about the new timelines, any other details.

Reasons for Delay

General reasons 

Campus hiring 

Massive effort by the Development team and QA team went into campus hiring. In taking multiple online interviews, campus visits etc. Campus hiring got closed recently.

Specific feature related reasons

Multiple units of measure (UOM) and Handling Eaches and Packs

Unexpected edge cases in Bulk Break Part

When we started the development, we realised there are more edge cases in bulk break than what we anticipated

Major QA effort 

UOM feature has major changes in Inventory reservation workflow, we are adding new buckets and doing soft allocation to support bulk break.

This means all the flows involving these line items have to be done QA. Since inventory is involved, it's almost all the inwards, outwards, returns, inventory management etc.  

Expiry and Virtual combo

Expiry and Virtual combo have added a lot of complexity to current system and also a lot of new cases, which are difficult to solve.

Immediate Actions

JIRA Roadmaps

We have Upgraded JIRA plan, now we have access to advanced Roadmaps feature. 

With Jira Advanced roadmaps we will be able to break large tasks into smaller chunks and assign dependencies. JIRA roadmaps will give us visibility of who is doing what and allow us to have better visibility over timelines.

We are now implementing the same for our current sprint itself. 

QA Data creation automation

Most of our time is spent in making the test cases data for each and every case. If we are able to automate this, we will be able to save about 40% to 50% time in QA. 

We are immediately starting to implement data creation automation at least (as a poc) for UOM QA so maybe then UOM over timeline will get early, if that is successful we will update with new timelines again. 

Future Actions

Team SOPs

With JIRA roadmaps in place, we will be creating new SOPs for the team on what all things to do for planning large features.

QA automation

We are moving towards full QA automation. One part of the QA team will only write new Automation test cases for new features and functionalities, the other part will just run the pre-defined scenarios for new features.

Updated Timelines

Updated in the Public Roadmap page