commentBlock = $("#comment_post_36489").find('.comment-blocks'); commentBlock.find('.loading').hide(); commentBlock.find('.see-all-comments').hide(); commentBlock.html("
<\/a>
\"it_user400080<\/a>
it_user400080<\/a>Sr. BMC Remedy Lead Developer (PM) at a transportation company<\/span><\/div>
<\/span>Real User<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

i agree with you completely. BMC Remedy is a special “beast”. I play the role of BA helping the BA understand how the platform will serve their needs. I design and architect the solutions, write up the technical requirements for the developers, develop the most difficult parts of the design when need be. And if time allows it, it will code too. Training the rest of the team is a big part of Remedy. Experience is what makes you a better developer<\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"Jeevan<\/a>
Jeevan Chaukar<\/a>Principal Consultant at a computer software company with 501-1,000 employees<\/span><\/div>
<\/span>Consultant<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Dear Pascale,\n
Definitely a useful review! We have a major customer on 8.1 SP2 version and we are in process of upgrading to Remedy 9.1 SP4 version. I agree that it can be quite painstaking process to upgrade and one really needs to invest in strong hardware in order to truly utilize BMC Remedy ITSM.<\/p>\n\n

One critical aspect of BMC Remedy projects is the choice of people involved in functional/technical design when performing customizations according to end user requirements.<\/p>\n\n

There are many customers where Business Analysts, Designers and Developers are 3 separate set of people. BA\'s do the analysis and handover requirements to designers. Designers handover designs to Developers...Developers handover coded functionality to testers and so on....<\/p>\n\n

This concept doesn\'t work very well with BMC Remedy and it is far better to have relatively senior developers perform the function of BA + Designer + Developer while junior people can simply be developers and are led by these senior developers.<\/p>\n\n

It also automatically means that you can\'t and shouldn\'t have over-aggressive release cycle where one design phase gets over and same set of designers immediately move to next release design while current design is being developed by the developers.<\/p>\n\n

The moment you start doing this kind of aggressive release cycle, you are going to sow the seeds for future issues!<\/p>\n\n

Regards,\n
Jeevan<\/p><\/div>