15 questions that reveal how much your legacy system is threatening your operations and business growth.
0 / 15 otázek
Knowledge & dependency
Yes, we have complete, up-to-date documentation
We have no documentation
We have documentation, but it's incomplete or outdated
Operations won't be threatened, we don't expect complications
There would be complications, but operations wouldn't be threatened
It would threaten operations – the running of the system or its further development
There is coverage – multiple people know the full system
Only one person knows the whole system, or nobody does
At least two people understand how the whole system works
We have no idea
We have a rough idea of the critical parts, but they're not documented
Yes, the critical parts are described and mapped
Months or "that's hard to estimate"
Several weeks
Days to 2 weeks
Sometimes we know, sometimes we're guessing
We can usually estimate the impact fairly well
We often don't know what the change will cause
Occasionally
Almost with every change
Rarely
Testing is mostly ad hoc or non-existent.
Part of the system is tested.
We have implemented testing procedures that cover most of the system.
Estimates are very inaccurate and often way off
Estimates are usually reasonably accurate
Estimates often slip, but within tolerance
It contains some, but they're still navigable
It's a mix of exceptions, workarounds, and patches
The system is relatively structured and clear
It significantly limits the ability to make changes, introduce new ideas, and grow the business
Barely at all, the system handles most needs
It slows us down in some important areas
Integrations are practically impossible to carry out in a reasonable time
Integrations can be done, but are costly and time-consuming
Integrations are easy (structured API, well documented...)
The technology is maintained and we update the stack on a regular basis
We don't have time for updates, but they're possible
The technology is no longer supported and updates cannot be performed
Yes, we have a clear plan and a list of the necessary steps
We have a rough idea but lack an implementation plan
We have nothing, we'd be going in blind
The team has learned to work with it, but isn't enthusiastic
The system is well-maintained, has a clear UX, and users are happy to work with it
Working with the system is complicated, causes stress and resistance to change