A warning to All Canadian Banks or Financial institutes, who are/ or willing to implementing SAP Banking/parts using Accelerated SAP(ASAP) methodology

A warning to All Canadian Banks or Financial institutes, who are/ or willing to implementing SAP Banking/parts using Accelerated SAP(ASAP) methodology.

First try to understand that there are certain important things to iron out when using Accelerated SAP(ASAP) methodology.

1. Yes it’s very sexy and very attractive when you read about it on internet or wiki or by sale pitch by SAP sales person.
2. Time frame: Don’t be dumb and buy what sale pitch is selling you about time to implement for GO LIVE. They always try to fool you with short time period to implement SAP Banking or part. If they say ONE year, ADD 3 years to it, to get actual time frame to implement SAP Banking and accordingly budget you implementation.
3. Try to follow your own old, well established methodology. ASAP methodology is a generic approach methodology. It will not solve all of banking problems, why, because it is NOT specifically accurate. Each and every bank and financial institute has unique aspects and implementation will be affected by the organization.
4. Your bank is totally different from other banks constitute. Your reasons for implementing SAP Banking are different from other bank. An ASAP work in other organization doesn’t mean it work in your bank. ASAP methodology can’t be relied on to such a degree of flexibility.
5. An ASAP methodology will NOT describe every necessary task, and following every details of the methodology may result in unnecessary work.

In conclusion, don’t blindly start using ASAP methodology. Put into context of your business and its need in your bank. It should be used with an understanding of the needs by adopting those aspects that supports your banking business/goals and by abandoning those do not.

SAP Core Banking and Big Bang Methodologies?

SAP Core Banking and Big Bang Methodologies?

My last post was on April/9. And today is June/5. Wow two months passed and no posting from my side.

In these two months, a lot of changes happen to my life. I got a new job as an independent contractor in new company, as a SAP Banking Functional Business Analyst. I have to relocate to new place. And new job keep me so dam busy, that I near about forget to post a blog.

My company is implementing full SAP Core Banking suite from end to end. Program is in very critical stage. They are following SAP ASAP methodologies. Whenever I join new project I always ask superior project members, what methodologies project is following and where we are at this time?
But unfortunately in this project the project lead is such a rookie on SDLC methodologies, that she have no idea where the hell project is going and I was told project is following Big Bang methodologies.
My first reaction was, excuse me… what… say it again.

Lead says, “Yes we are following Big Bang methodologies to implement SAP Core banking”.

Me, “Are you telling me, you guys are implementing SAP Core banking, which is huge elephant, with Big Bang.” Just like that, one day first of May/2011 everyone wakeup and SAP Core banking in production and whole company business is live, WOW…”

“Yes”, said lead.

And in my mind, I was thinking, “she doesn’t have any idea what she is talking”. And train of thoughts start running in my mind.

What!, SAP core banking and Big Bang methodologies??

How the hell, can someone implement $ 100 millions dollars project with big bang. My mind was very uneasy about this idea.

I left the lead. Came at my desk and do some research. Open solution manager and started to hunt down methodologies documents.

After reading lots of papers and documents in solution manager, I get some information.

First thing is they are following SAP-ASAP. Seconds thing is, yes they going GO-LIVE on 1st May/2011, as per project management documents and project roadmap. They are telling everyone that 30th April/211 is end of Final Preparation phase and start of Go Live & Start phase.
My experience enlighten me, that’s not possible, yes they will put something in Prod. Or whatever is ready after end to end testing they will put in Prod. And then they make second or third iteration of big Release.
May be I’m coming from this kind school, which believe in iterative methodologies is best suitable for big program like SAP Core banking.

That’s what happened in FCC. FCC was following RUP/Agile methodologies.
I think a RUP/Agile methodology is only best methodologies to implement big programs like SAP Core banking. I think a SAP- ASAP methodology is same as waterfall methodologies. First come Project Preparation and then fall Business Blueprint and then fall Realization and the fall Final Preparation phase and the last Go Live & Support. This is pure Water Fall methodology. And lately SAP just add feedback or a small iterative in ASAP methodologies. Because Agile is going super hit and they also want some part of Agile, so SAP add feedback in its own methodologies.

But truth is SAP ASAP methodologies is waterfall methodologies.

Vee- Model Development Process or V-Model methodology

Vee- Model Development Process or V-Model methodology

V-model is the development process proceeds from the upper left point of the V toward the right, ending at the upper right point. In the left-hand, downward-sloping branch of the V, development personnel define business requirements, application design parameters and design processes. At the base point of the V, the code is written. In the right-hand, upward-sloping branch of the V, testing and debugging is done. The unit testing is carried out first, followed by bottom-up integration testing. The extreme upper right point of the V represents product release and ongoing support.

The V-Model, is a product-development process originally developed in Germany for government defense projects. It has become a common standard in software development. The V-Model gets its name from the fact that the process is often mapped out as a flowchart that takes the form of the letter V.

Pro: It’s simple and straightforward

Corn: It is too stiff for the growing nature of IT (information technology) business environments.

Agile

I just wanted to say "Happy Labour Day" to my readers in Canada/ U.S. I hope you are enjoyed a day off. This post is my first post on series of posts on Agile methodology. I don’t want to load my reader with all information at one shot, that’s why I’m breaking Agile methodology into chain of series. I think this methodology is quite new and we have to give some time to this methodology to mature. Furthermore no methodology can’t mature with in it 2-3 years, so Agile methodology also need some more time to mature and IT industries also need more time to alliance with Agile. They also need more time to adjust with this new methodology.

So just for curiosity, I want to know first, what the word Agile means. So according to thefreedictionary.com and link: www.thefreedictionary.com/agile

Def: ag·ile (jl, -l)
adj.
1. Characterized by quickness, lightness, and ease of movement; nimble.
2. Mentally quick or alert: an agile mind.
[French, from Latin agilis, from agere, to drive, do; see ag- in Indo-European roots.]

It’s an adjective with meaning quick in movement, lightness.

Defining Agile in Software development:
An iterative and incremental (evolutionary) approach performed with project stakeholders in a highly collaborative and self organizing manner with just the right amount of ceremony to produce high quality software and timely manner that meets stakeholders changing needs. For more information click on IBM website on agile, link: www.ibm.com/software/rational/agile/resources/