PM4K DISCUSSION 003: TOP #1 CHALLENGE FACED DURING TEMENOS T24 IMPLEMENTATION

For all of us who have managed Temenos T24 implementation projects, we know about the challenges we've faced during implementation. Implementation challenges are not specific to T24 only; but all projects face minor/major challenge(s). The objective of this discussion is to focus on T24 implementation projects and understand, what in your opinion is the most recurring and fatal challenge that you've faced during your T24 implementation? Most importantly, how did you (your team) manage to overcome it? Let's continue Sharing & Learning.

 

[Mathew@PM4K]

HTTP://WWW.ANISHMATHAIMATHEW.BLOGSPOT.COM

Do join our growing online communities on Blogger, Twitter, Facebook, LinkedIn & NetworkedBlogs. Most importantly, please do come back for more.

SWEET DREAMS BUSINESS ANALYSTS

Ever come across business users who don't know what they are doing? Ever come across business users who don't know what they want? Ever wondered how someone copes up with all these knowledge gaps and yet manages one of the most important constraints/aspects of a Project i.e. SCOPE? Well maybe as a Project Manager you've never bothered (beyond ensuring you're Business Analyst is doing his/her job), but ask a Business Analyst and he/she would tell you about the nightmares they get thinking about the trauma they face while managing Project Scope. Here @ PM4K, Mathew would like to share with you the 'BUSINESS ANALYSIS MAGIC QUADRANT' that would surely make your Business Analyst's nights more DREAMY & less NIGHTMARISH ;) 

As you can see, the BUSINESS ANALYSIS MAGIC QUADRANT has 4 blocks across the 2 axis. On the ‘Y’ axis is the Current Situation (As-Is Situation) & on the ‘X’ axis is the Future Situation (To-Be Situation).

 

As the saying goes, ‘A Picture Speaks a Thousand Words’, so Mathew’s going to let the self-explanatory picture of the Magic Quadrant do all the talking on this post. Below is just the gyst of it all:

1. Result of ENTERPRISE ANALAYSIS = Awareness of CURRENT SITUATION (As-Is Situation)

• 1.1. HAVE (We have these features/functions in the existing system)
• 1.2. DON'T HAVE (We do NOT have these features/functions in the existing system)

2. Result of REQUIREMENTS GATHERING = Understanding of FUTURE SITUATION (To-Be Situation)

• 2.1. WANT (We want these features/functions in the new system)
• 2.2. DON'T WANT (We do NOT want these features/functions in the new system)

You can never consider your requirements complete until you answer the 4 A's of Business Analysis i.e. What to Affirm? What to Acquire? What to Abolish? What to Avoid? 

• If you HAVE it + You still WANT it = You AFFIRM such requirements
• If you DON’T HAVE + You WANT it = You ACQUIRE such requirements
• If you HAVE it + You DON'T WANT it = You ABOLISH such requirements
• If you DON’T HAVE + You DON'T WANT it = You AVOID such requirements

Mathew would like to conclude this post with 2 words to all the Business Analyst's out there; SWEET DREAMSSSSSSSS :)

 

[Mathew@PM4K]

HTTP://WWW.ANISHMATHAIMATHEW.BLOGSPOT.COM

HTTP://WWW.ANISHMATHAIMATHEW.WORDPRESS.COM