This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
One of the things I've been struggling with is justifying when I have to say no to requests for changes or enhancements to Maximo's UI or to associated reports. I'll say no when it's obviously a one off request - e.g. please change all the fonts on the reports from Arial to Helevetica (yes, I really got that one).
But I'm curious what criteria others have used to set the bar on what gets done vs not.
Hello Jason,
I've seen some organizations where the IT staff manages the entire system. They try to survey all parties but sometimes fail to do this. The other problem is
when a "bad decision" is made, meaning the change you made impacted another group and they say they weren't properly informed, then this hurts reputation.
In any case,
the first recommendation is to enlist the involvement of a review group (e.g. Core Team). If you already have one, then formalize this review process. If the process is there, make sure you have an electornic punchlist (could be Excel sheet) with various columns for ranking and categorizing requests. Users "feel better' when you the administrators have actually recorded their request (and given them a tracking number). As to processing the requests, it should be treated like a maintenance work order backlog. High priority items should float to the top. These requests can also be estimated in terms of effort, and, they can be marked as "needing outside help". And they could be linked to future versions. Recurring problems can be identified. This punchlist could be used for problems as well as enhancements.
Final note: I would differentiate between customization versus tailoring.
Tip: hire a business analyst who does regular end-user surveys
w/br
j.r.
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> One of the things I've been struggling with is justifying when I have to say no to requests for changes or enhancements to Maximo's UI or to associated reports. I'll say no when it's obviously a one off request - e.g. please change all the fonts on the reports from Arial to Helevetica (yes, I really got that one).
>
> But I'm curious what criteria others have used to set the bar on what gets done vs not.
>