We're a 20 ppl company in supply chain management and I'm leading the IT department with 2 ppl (+ outsourced development company).
For new features, in my ideal, imaginative world, the users would test real cases on the test system. After they've verified that everything is developed according to their needs, the developers could deploy the feature to the live system.
- people are super busy and don't want/have time to spend on a test system.
- People are reluctant to changes and improvement and adoption is growing only slowly/gradually.
- Use cases, that the IT hasn't thought of, will be discovered after the deployment to the live systems and need to be fixed on urgent/priority bases.
(side note: We're a small company, the team doesn't understand much IT and many are rather junior, so the CEO requires the CTO to understand the business processes and come up with solutions. We've tried involving the team in planning and idea generation but the outcome was rather poor.
side note 2: We're currently shifting from a waterfall pm to some methods of agile/scrum, but it's not a clean switch, rather a process and partial improvements.)
For new features (before deploying to live) I've done:
- Recorded screen videos, explaining/demoing the new feature
- Created user accounts in the test system for the key team members
- Shared requirements and documentation during the planning phase with key team members
- Created screen designs and wireframes to the team
but we keep on running into the issues mentioned about. Busy people, no contribution during the planning phase and fixes as well as change requests after deployment to live.
What can I do, to catch more use cases in the project planning phase? What can I do, to get people more involved early on in the development?