Omnichannel ‘Bogus Solution’: Project Status is RED
We’ve all been there a time or two ourselves, but hopefully not. The slide deck hits your inbox, you double click, and the PPT comes up with the first glaring color as RED. You sit back and ask “how did we get here?”
Most organizations we’ve worked with on Omnichannel projects attribute this to one, if not all areas below:
- Scope increased since the Sales Phase
- Development time and resources needed were more than expected
- Resources for testing or key resources for use-case validation were not properly planned for
These situations are usually avoidable and having been added to a few projects after-the-fact, we can tell you that this scenario is remedied by effective project planning, which comes from experience in the field implementing Omnichannel solutions.
TIP: Use cloud-based issues tracking tools
SCApath experts suggest using tools such as Confluence for content management (Change Management) and JIRA (Defect and Use-Case Creation) to better plan project task. It’s centralized for all users, in the cloud so it can be accessed anywhere, and secure.
TIP: Create a project charter and hold people accountable to it
Most implementation seem to go south during the testing phase where ‘defects’ are raised back to the software vendor that are in actuality product gaps where the retailer expects functionality that the software vendor never committed to. To avoid this, create a project charter before designing the software, then re-confirm the charter post-design with the team. If a question comes up after the fact, and it’s not part of the written intent of the project, then resolve to agree that the expectation isn’t a valid one and work with the user to re-align their expectations. It’s in this way that you don’t give a false-impression that the project is in-red. This also helps to keep the “people” and “timeline” boxes out of the red as well.
Contact an SCApath expert through the link below for help digging into your project contacts us here.