Showing posts with label My personal rumbling. Show all posts
Showing posts with label My personal rumbling. Show all posts
Friday, April 9, 2010
Change Title and scope of blog.
I included BA roles also in the scope of this blog, so you noticed I change the Title of Blog.
Saturday, April 3, 2010
Have a Great Weekend!
Just a note to let you know that I'm outta here for the weekend!Easter weekend and I wish the same for all of you.
Thursday, February 11, 2010
Why I love working in FCC (Farm Credit Canada)?
Why I love working in FCC (Farm Credit Canada)?
I love working with FCC because they have very solid working cultural practises. Everyone there, try to practise with few exceptions. They put Cultural Practices on there home page of wiki. I like there Cultural Practices so much that I’m just copying and pasting as-it-is. I have this “knowledge spreading” urge that I have to spread to my readers.
Cultural Practices
1. We hold ourselves and each other accountable for our impact on business results and our impact on people.
2. We hold ourselves and each other accountable for delivering on commitments, agreements and promises.
3. We hold ourselves and each other accountable for building and sustaining committed partnerships.
4. We hold ourselves and each other accountable for creating a safe environment where people can speak up without fear.
5. We measure our success by how others perceive and respond to our leadership, not by our personal point of view.
6. We talk straight in a responsible manner.
7. We "listen for" contributions and commitment. We do not "listen against" people or ideas.
8. We are open to coaching. We actively seek and listen to coaching.
9. We clean-up and recover quickly.
10. We acknowledge others often and celebrate both small and large successes.
Source: FCC wiki www.fcc-fac.ca
I love working with FCC because they have very solid working cultural practises. Everyone there, try to practise with few exceptions. They put Cultural Practices on there home page of wiki. I like there Cultural Practices so much that I’m just copying and pasting as-it-is. I have this “knowledge spreading” urge that I have to spread to my readers.
Cultural Practices
1. We hold ourselves and each other accountable for our impact on business results and our impact on people.
2. We hold ourselves and each other accountable for delivering on commitments, agreements and promises.
3. We hold ourselves and each other accountable for building and sustaining committed partnerships.
4. We hold ourselves and each other accountable for creating a safe environment where people can speak up without fear.
5. We measure our success by how others perceive and respond to our leadership, not by our personal point of view.
6. We talk straight in a responsible manner.
7. We "listen for" contributions and commitment. We do not "listen against" people or ideas.
8. We are open to coaching. We actively seek and listen to coaching.
9. We clean-up and recover quickly.
10. We acknowledge others often and celebrate both small and large successes.
Source: FCC wiki www.fcc-fac.ca
Thursday, December 31, 2009
Wednesday, December 30, 2009
A Thwarted Day, Ha!
A Thwarted Day, Ha!
Today was the very hectic day, boy. Yes... I’m working in holiday seasons. As there are lots of task on my plate and the major one is testing Revenues sharing rules. As our UAT testing is going to be started in New Year that’s mean next week. My major concern is Revenue sharing is still not fixed. I’m not feeling confident to let this shit pass to UAT and then to Prod. So I told this to my Project Manager and guess what; what was her reaction, “Ya I know that, but we still are going with Revenue sharing in prod with know defects”. Ha!
Anyway, so we have that chunk (Revenue sharing) to test in QA region and in morning we were told that QA region is down and it will be down till next day for refresh Ha!. Ok so we can’t test in QA region. Then PM said do some test in upper tier T3. We started to test in T3 for our UAT, but T3 is also broken. Our SAP/Java and web server were down, Ha!. At around afternoon we get final Yes from Netweaver to go and do Revenue sharing testing in T3. Guess what Revenues sharing functionality is broken in T3, why? The transports related to Revenue sharing were not in T3, Ha!. Dam developer and Netweaver forget to move big junk of transports in T3.
I got an email from, Netweaver, “All transports related to Revenues sharing were in T3, go and test”. Ok when I try to run Revenue sharing program in SAP CML, guess what it still not working getting an error.
I further investigate why the hell it’s not working? The reason was that a SAP is taking data from oracle tables and those oracle tables were not created in T3 while doing deployment in T3. Why, because someone forget to add the steps in deployment check to, “Run script to create oracle table in T3” Ha!
So in the entire day I was like investigator, who was investing, why the hell Revenue sharing is not working in T3 and I did no testing related to my task.
In this way my day END, Ha!
Today was the very hectic day, boy. Yes... I’m working in holiday seasons. As there are lots of task on my plate and the major one is testing Revenues sharing rules. As our UAT testing is going to be started in New Year that’s mean next week. My major concern is Revenue sharing is still not fixed. I’m not feeling confident to let this shit pass to UAT and then to Prod. So I told this to my Project Manager and guess what; what was her reaction, “Ya I know that, but we still are going with Revenue sharing in prod with know defects”. Ha!
Anyway, so we have that chunk (Revenue sharing) to test in QA region and in morning we were told that QA region is down and it will be down till next day for refresh Ha!. Ok so we can’t test in QA region. Then PM said do some test in upper tier T3. We started to test in T3 for our UAT, but T3 is also broken. Our SAP/Java and web server were down, Ha!. At around afternoon we get final Yes from Netweaver to go and do Revenue sharing testing in T3. Guess what Revenues sharing functionality is broken in T3, why? The transports related to Revenue sharing were not in T3, Ha!. Dam developer and Netweaver forget to move big junk of transports in T3.
I got an email from, Netweaver, “All transports related to Revenues sharing were in T3, go and test”. Ok when I try to run Revenue sharing program in SAP CML, guess what it still not working getting an error.
I further investigate why the hell it’s not working? The reason was that a SAP is taking data from oracle tables and those oracle tables were not created in T3 while doing deployment in T3. Why, because someone forget to add the steps in deployment check to, “Run script to create oracle table in T3” Ha!
So in the entire day I was like investigator, who was investing, why the hell Revenue sharing is not working in T3 and I did no testing related to my task.
In this way my day END, Ha!
Subscribe to:
Posts (Atom)