2nd types of Project Manager are Joker: I mean those managers who paint themselves as very humours, they do comedy. Every time they crack jokes, it doesn’t matter to them what Time or Place they are. That’s ok having a sense of humour. But people only laugh on good timing of jokes, not on every joke.
In our corporation there is one jokes, I hate that basted. He do all kind of act, like.. hoooo, haa.. its so disgusting. I mean come on, you can’t be a good PM by acting and making other laugh, you think that, you are very friendly, very approachable. No Jokers, at the end of the day, it’s not how good you are friendly and approachable. At the end of the day Management looks at your result. That’s matter, in what budget, time and what you deliverables?
We were lucky on that. Management make decision to change PM in mid of project. I think that’s the most stupid decision in any Project, to shuffling PM in mid of project. Our team protect that, and last we win, that Jokers was out of Project.
Tuesday, September 30, 2008
Wednesday, September 24, 2008
How should be Project Manager?
How should be Project Manager?
I think PMs are of Three kinds.
First kinds of PMs are serious one. Do PM should be very serious. No laugh, just talk work. Try to demoralize project team for enjoying any events. They are like party killer. Such kinds of PMs are like burden on team members who like fun-joys. Whenever there is some fun event going on in project, they kill that fun by just being there or by starting conversation on what done, and what left to done about project. They just start asking some kind of project report from BA, QA and developers. That kills all joys and fun in team.
The good things with this PMs are
A. All team remain in his/her control.
B. Works and commands follow the defined paths.
C. Team save time.
D. There will be some kind of undefined formality between PM and team.
E. Such kind of PM delivered project on time, they are much focused.
The bad goes against them are
A. They closed door themselves against team.
B. Team don’t feel free.
C. Team hesitate to enter PM office to talk about project or some personal problem.
D. They miss the internal information or internal who-how-what-when political talks and rumours, which I think is very important in company where politics is very common practice.
E. For the next project, team members try to avoid be in his/her project team member.
Management like these kind of PM, because at the end of the day, its matter project is deliver on time in budget
I think PMs are of Three kinds.
First kinds of PMs are serious one. Do PM should be very serious. No laugh, just talk work. Try to demoralize project team for enjoying any events. They are like party killer. Such kinds of PMs are like burden on team members who like fun-joys. Whenever there is some fun event going on in project, they kill that fun by just being there or by starting conversation on what done, and what left to done about project. They just start asking some kind of project report from BA, QA and developers. That kills all joys and fun in team.
The good things with this PMs are
A. All team remain in his/her control.
B. Works and commands follow the defined paths.
C. Team save time.
D. There will be some kind of undefined formality between PM and team.
E. Such kind of PM delivered project on time, they are much focused.
The bad goes against them are
A. They closed door themselves against team.
B. Team don’t feel free.
C. Team hesitate to enter PM office to talk about project or some personal problem.
D. They miss the internal information or internal who-how-what-when political talks and rumours, which I think is very important in company where politics is very common practice.
E. For the next project, team members try to avoid be in his/her project team member.
Management like these kind of PM, because at the end of the day, its matter project is deliver on time in budget
Saturday, September 20, 2008
SAP QA - Integration Testing
" All heads and hands on the table, its time for Integration testing, before we sign off with our blood"
This say is repetitively echoed by our Non Functional Manager, that we all are now piss off, with this. I don't know, what is going on on Integration testing, i don't know, i simply don't know. We all are just puzzled, bang head to each other, i mean its mess! No project, not a single project, out of 10 projects is in defined line. It seems we are doing some unwanted things. Even moral of project teams is like Lehman Brother's share. People want to jump from Integration Project to some where else. And i look myself as captain of Titanic ship, just watching people dyeing, kind off. It sucks...
Ok let me think how we started this Integration Testing. What was the approach to Integration testing, when we start. Huum, It was, it was, huum, Our Project Sponsor says: "Win-Win Project for this team and organization"
And we kept very simple and straight approach. The purpose of Integration testing was to confirm that the organization's business processes work according to the requirements established in the Business Blueprint Phase and that the system is ready to go live in Oct. To accomplish this, we must test every aspect of the processes. QA, are here to help in accomplish this goal.
We are using some SAP Best Practice, and here it is(I am not sure):
A. Validate common business scenarios, for all projects. We created some 700 valid test cases to test Integration testing scenarios. We done with it.
B. Integration test scripts, we done this also
C. Security testing, That's the bottleneck for our Integration Project. We are yet not there
D. Cycle testing
E. UAT testing in Jan
" Its so easy to Plan, but so difficult to implement", same as with advice.
This say is repetitively echoed by our Non Functional Manager, that we all are now piss off, with this. I don't know, what is going on on Integration testing, i don't know, i simply don't know. We all are just puzzled, bang head to each other, i mean its mess! No project, not a single project, out of 10 projects is in defined line. It seems we are doing some unwanted things. Even moral of project teams is like Lehman Brother's share. People want to jump from Integration Project to some where else. And i look myself as captain of Titanic ship, just watching people dyeing, kind off. It sucks...
Ok let me think how we started this Integration Testing. What was the approach to Integration testing, when we start. Huum, It was, it was, huum, Our Project Sponsor says: "Win-Win Project for this team and organization"
And we kept very simple and straight approach. The purpose of Integration testing was to confirm that the organization's business processes work according to the requirements established in the Business Blueprint Phase and that the system is ready to go live in Oct. To accomplish this, we must test every aspect of the processes. QA, are here to help in accomplish this goal.
We are using some SAP Best Practice, and here it is(I am not sure):
A. Validate common business scenarios, for all projects. We created some 700 valid test cases to test Integration testing scenarios. We done with it.
B. Integration test scripts, we done this also
C. Security testing, That's the bottleneck for our Integration Project. We are yet not there
D. Cycle testing
E. UAT testing in Jan
" Its so easy to Plan, but so difficult to implement", same as with advice.
Friday, September 12, 2008
Integration testing – sucks
Integration testing – sucks
Yaaa, integration testing sucks, management want to test integration testing with all projects as fast as we can. And that happen in our integration testing meeting, managers wants as soon as possible. But there is problem not is problem but are problems.
First one SAP BI, in BI we have just done foundation layer, and that also day to day we are getting new requirement and change requirements. We load all table, views and what ever garbage we have as data into DSOs as foundation layer, all history data, everything. So we have some 600 DSO in foundation layers, pew… Our developers are working on transformation layer and BAs are working on cubes. We QA tested foundation layer in Development environment, we are still waiting when all the stuff from T1-development transport into our environment T2-QA. I talk to my PM, and we figure out, most probably mid of this month. After transportation done, we have to test again foundation layer in T2. Transportation takes one week. So that’s a one big problem. All other project are in T2 (test environment) and we SAP BI are in T1 (development).
Second one PMs, yes Project Managers. I always think they played double game. One side they keep telling us we are not ready for integration testing, so we are not going for integration testing and on other side when they talk to management, there they all are fully ready for integration testing. So when integration meeting started with Management, they first shoot question to me, they said, "Your PM is ready for integration testing, what the heck you are not ready?" I replied them back, "We are ready, but not ready". All guys in meeting are looking at me, and mostly all PMs and particularly my PM, staring at me to kill me. I then explain to management, we are not ready fully, we are just done foundation layer and we are in development stage, we are just done 30% developments. Believe me, it was not only my view, but all other projects BA, QA and Developer also agree with me. Man, how you go for Integration testing when none of the projects are not fully ready to deploy. I think at PM levels there is more politics and diplomacy. So that’s makes PM double standard.
This make management to think, and our Integration testing again pushed to next month. This is third time we shifted integration testing. It seems these projects are never ending projects. And at last in my view if project goes more then year, it loses its charm and team lose its confidence and motivation. This is happing in CML team. CML is now 2 year old project, we have new PM, BA (one is still there) and kind of new QA team. QA team is mixed of new and old. Still CML is not on Go Support & Live. It seems there is no Go Support & Live stage in SAP projects.
Yaaa, integration testing sucks, management want to test integration testing with all projects as fast as we can. And that happen in our integration testing meeting, managers wants as soon as possible. But there is problem not is problem but are problems.
First one SAP BI, in BI we have just done foundation layer, and that also day to day we are getting new requirement and change requirements. We load all table, views and what ever garbage we have as data into DSOs as foundation layer, all history data, everything. So we have some 600 DSO in foundation layers, pew… Our developers are working on transformation layer and BAs are working on cubes. We QA tested foundation layer in Development environment, we are still waiting when all the stuff from T1-development transport into our environment T2-QA. I talk to my PM, and we figure out, most probably mid of this month. After transportation done, we have to test again foundation layer in T2. Transportation takes one week. So that’s a one big problem. All other project are in T2 (test environment) and we SAP BI are in T1 (development).
Second one PMs, yes Project Managers. I always think they played double game. One side they keep telling us we are not ready for integration testing, so we are not going for integration testing and on other side when they talk to management, there they all are fully ready for integration testing. So when integration meeting started with Management, they first shoot question to me, they said, "Your PM is ready for integration testing, what the heck you are not ready?" I replied them back, "We are ready, but not ready". All guys in meeting are looking at me, and mostly all PMs and particularly my PM, staring at me to kill me. I then explain to management, we are not ready fully, we are just done foundation layer and we are in development stage, we are just done 30% developments. Believe me, it was not only my view, but all other projects BA, QA and Developer also agree with me. Man, how you go for Integration testing when none of the projects are not fully ready to deploy. I think at PM levels there is more politics and diplomacy. So that’s makes PM double standard.
This make management to think, and our Integration testing again pushed to next month. This is third time we shifted integration testing. It seems these projects are never ending projects. And at last in my view if project goes more then year, it loses its charm and team lose its confidence and motivation. This is happing in CML team. CML is now 2 year old project, we have new PM, BA (one is still there) and kind of new QA team. QA team is mixed of new and old. Still CML is not on Go Support & Live. It seems there is no Go Support & Live stage in SAP projects.
Wednesday, September 3, 2008
Living an honouring life in QA world
Living an honouring life in QA world
Let me give you all, few pieces of advice on how to live an Honoured life in QA world.
1. The QA world is all about Bugs. Always act as a devil or evil in QA world. If you are very nice, soft-spoken and quickly sign-off, then QA world is not your world that sounds like Project Manager Job.
2. If you are testing anything, mean anything, and that thing is working well, that’s a bad news for you. So try to do something malevolence thing to break that working thing. You have to find bugs and defects in those working process. Never ever pass any functionality without defects. If you are not finding any bugs/defects people in your project team think that you are useless.
3. For eternity always exaggerated your finding of bugs. Create panic; create hype in project about your defects. Make the team believe that, the project success and failures only and only depends on this bug.
4. One bug-One at a time: If you found one bug, weather your PM know that you found the bug, but then also, run to his/her office and let PM know you found a bug. If you found bunch of bugs, then also run to PM one at a time bug.
5. And the last one, and very important one, never ever try to find the source of bugs. Just focus on bugs not on source of bugs. Believe me if you try to find source of bugs, you will be the first who burnt. That day will be your last day in QA world, you may be fired. In other word you will dead in QA world.
And at last by concluding this post, always follows the above advice and live happy and long life in QA world
Let me give you all, few pieces of advice on how to live an Honoured life in QA world.
1. The QA world is all about Bugs. Always act as a devil or evil in QA world. If you are very nice, soft-spoken and quickly sign-off, then QA world is not your world that sounds like Project Manager Job.
2. If you are testing anything, mean anything, and that thing is working well, that’s a bad news for you. So try to do something malevolence thing to break that working thing. You have to find bugs and defects in those working process. Never ever pass any functionality without defects. If you are not finding any bugs/defects people in your project team think that you are useless.
3. For eternity always exaggerated your finding of bugs. Create panic; create hype in project about your defects. Make the team believe that, the project success and failures only and only depends on this bug.
4. One bug-One at a time: If you found one bug, weather your PM know that you found the bug, but then also, run to his/her office and let PM know you found a bug. If you found bunch of bugs, then also run to PM one at a time bug.
5. And the last one, and very important one, never ever try to find the source of bugs. Just focus on bugs not on source of bugs. Believe me if you try to find source of bugs, you will be the first who burnt. That day will be your last day in QA world, you may be fired. In other word you will dead in QA world.
And at last by concluding this post, always follows the above advice and live happy and long life in QA world
Tuesday, September 2, 2008
Its all about Integration Testing in SAP QA-1
10:00 Am: This meeting was good, as expected; we have some issue with integration testing. Our router tables are not populated when we trying to convert data from obsolete system to CML. Second problem, CML vendors name are not matching with obsolete vendors. This seems conversion script is taking data from somewhere else. And a major one, we have some issue with security also. Its looks like all projects are affected with these problems. Nothing is working…huummm…..
2:00 pm: I shift this meeting, I am not getting time to write test plan for Integration testing. So I got few couple of hours to write test plan. I reschedule this meeting on Sep/4. BA agrees on this. I am running of time for integration testing. I just have 2 weeks for integration testing.
Some time I amazed that BAs and Developers take more then 6 to 9 months to analysis and design an application. And bloody Project Manager Need QA did testing and sign-off within 2 weeks, its sucks. I still remember one project, where I was give 2 days before sign-off to test language translation of application from English to French. Man, that’s sucks, believe me that’s sucks.
2:00 pm: I shift this meeting, I am not getting time to write test plan for Integration testing. So I got few couple of hours to write test plan. I reschedule this meeting on Sep/4. BA agrees on this. I am running of time for integration testing. I just have 2 weeks for integration testing.
Some time I amazed that BAs and Developers take more then 6 to 9 months to analysis and design an application. And bloody Project Manager Need QA did testing and sign-off within 2 weeks, its sucks. I still remember one project, where I was give 2 days before sign-off to test language translation of application from English to French. Man, that’s sucks, believe me that’s sucks.
Its all about Integration Testing in SAP QA
Its 8:00 AM just came office, from Labor Day, long weekend. Quickly check Voice mail and any email on Outlook. I always pray to god, every day in morning when open my Outlook, Oh god there should not be any trouble email. Today i don't have any. After checked email, then check my Calendar. There are four meeting today... thank god!
First meeting is at 10:00 Am to 11:00 Am, it’s about Integration Testing. Being a Team Lead of SAP BI QA and also SAP CML, is pain in ass. Actually whole Integration is pain in ass. On top of this you came after long weekend, it’s really a pain in ass. In this meeting all other 8 project QA lead will be there and they will discuss on Test Plan, Test cases and test scenarios related to Integration testing. And hope fully we all discuss where we are on our project, kind of status meeting. I am done 60% of work related to Integration testing. I think I am the only one who is ahead of all 8 QA leads. So let’s see what will happen in this "integration meeting". And yes the person who is chairing this meeting, he sit just crosses to my desk. He is good, he don’t bug me every time. This amazing guy, in this spacious office we are just 2 people, we hardly talk to each other.
Then there are couples of half hour meeting and then…
Last meeting is at 2:00 pm to 3:00 pm. This meeting is also about Integration testing, but with SAP BI Business Analyst. She is new in BA. I am not expecting any thing profitable from BA. In this meeting, we will discuss on test cases and test scenarios related to SAP BI. Most probably she will try to make maximum test cases to "invalid", as all BA does, try to prove QA don’t have thoroughly knowledge of business process. So I am mentally prepare to hear like, "Don’t do this", "We don’t do this" and my favorite "We don’t practice this kind of in real world, so don’t test this".
I will post what happen in these meeting…
First meeting is at 10:00 Am to 11:00 Am, it’s about Integration Testing. Being a Team Lead of SAP BI QA and also SAP CML, is pain in ass. Actually whole Integration is pain in ass. On top of this you came after long weekend, it’s really a pain in ass. In this meeting all other 8 project QA lead will be there and they will discuss on Test Plan, Test cases and test scenarios related to Integration testing. And hope fully we all discuss where we are on our project, kind of status meeting. I am done 60% of work related to Integration testing. I think I am the only one who is ahead of all 8 QA leads. So let’s see what will happen in this "integration meeting". And yes the person who is chairing this meeting, he sit just crosses to my desk. He is good, he don’t bug me every time. This amazing guy, in this spacious office we are just 2 people, we hardly talk to each other.
Then there are couples of half hour meeting and then…
Last meeting is at 2:00 pm to 3:00 pm. This meeting is also about Integration testing, but with SAP BI Business Analyst. She is new in BA. I am not expecting any thing profitable from BA. In this meeting, we will discuss on test cases and test scenarios related to SAP BI. Most probably she will try to make maximum test cases to "invalid", as all BA does, try to prove QA don’t have thoroughly knowledge of business process. So I am mentally prepare to hear like, "Don’t do this", "We don’t do this" and my favorite "We don’t practice this kind of in real world, so don’t test this".
I will post what happen in these meeting…
Subscribe to:
Posts (Atom)