Monday, July 9, 2012

TWO lists that managers needs to follow

( from Harvard Business Review)

I was late for my meeting with the CEO of a technology company and I was emailing him from my iPhone as I walked onto the elevator in his company's office building. I stayed focused on the screen as I rode to the sixth floor. I was still typing with my thumbs when the elevator doors opened and I walked out without looking up. Then I heard a voice behind me, "Wrong floor." I looked back at the man who was holding the door open for me to get back in; it was the CEO, a big smile on his face. He had been in the elevator with me the whole time. "Busted," he said.

The world is moving fast and it's only getting faster. So much technology. So much information. So much to understand, to think about, to react to. A friend of mine recently took a new job as the head of learning and development at a mid-sized investment bank. When she came to work her first day on the job she turned on her computer, logged in with the password they had given her, and found 385 messages already waiting for her.

So we try to speed up to match the pace of the action around us. We stay up until 3 am trying to answer all our emails. We twitter, we facebook, and we link-in. We scan news websites wanting to make sure we stay up to date on the latest updates. And we salivate each time we hear the beep or vibration of a new text message.

But that's a mistake. The speed with which information hurtles towards us is unavoidable (and it's getting worse). But trying to catch it all is counterproductive. The faster the waves come, the more deliberately we need to navigate. Otherwise we'll get tossed around like so many particles of sand, scattered to oblivion. Never before has it been so important to be grounded and intentional and to know what's important.
Never before has it been so important to say "No." No, I'm not going to read that article. No, I'm not going to read that email. No, I'm not going to take that phone call. No, I'm not going to sit through that meeting.
It's hard to do because maybe, just maybe, that next piece of information will be the key to our success. But our success actually hinges on the opposite: on our willingness to risk missing some information. Because trying to focus on it all is a risk in itself. We'll exhaust ourselves. We'll get confused, nervous, and irritable. And we'll miss the CEO standing next to us in the elevator.

A study of car accidents by the Virginia Tech Transportation Institute put cameras in cars to see what happens right before an accident. They found that in 80% of crashes the driver was distracted during the three seconds preceding the incident. In other words, they lost focus — dialed their cell phones, changed the station on the radio, took a bite of a sandwich, maybe checked a text — and didn't notice that something changed in the world around them. Then they crashed.

The world is changing fast and if we don't stay focused on the road ahead, resisting the distractions that, while tempting, are, well, distracting, then we increase the chances of a crash.
Now is a good time to pause, prioritize, and focus. Make two lists:
List 1: Your Focus List (the road ahead) What are you trying to achieve? What makes you happy? What's important to you? Design your time around those things. Because time is your one limited resource and no matter how hard you try you can't work 25/8.
List 2: Your Ignore List (the distractions)
To succeed in using your time wisely, you have to ask the equally important but often avoided complementary questions: what are you willing not to achieve? What doesn't make you happy? What's not important to you? What gets in the way?
Some people already have the first list. Very few have the second. But given how easily we get distracted and how many distractions we have these days, the second is more important than ever. The leaders who will continue to thrive in the future know the answers to these questions and each time there's a demand on their attention they ask whether it will further their focus or dilute it.
Which means you shouldn't create these lists once and then put them in a drawer. These two lists are your map for each day. Review them each morning, along with your calendar, and ask: what's the plan for today? Where will I spend my time? How will it further my focus? How might I get distracted? Then find the courage to follow through, make choices, and maybe disappoint a few people.
After the CEO busted me in the elevator, he told me about the meeting he had just come from. It was a gathering of all the finalists, of which he was one, for the title of Entrepreneur of the Year. This was an important meeting for him — as it was for everyone who aspired to the title (the judges were all in attendance) — and before he entered he had made two explicit decisions: 1. To focus on the meeting itself and 2. Not to check his BlackBerry.

What amazed him was that he was the only one not glued to a mobile device. Were all the other CEOs not interested in the title? Were their businesses so dependent on them that they couldn't be away for one hour? Is either of those a smart thing to communicate to the judges?

There was only one thing that was most important in that hour and there was only one CEO whose behavior reflected that importance, who knew where to focus and what to ignore. Whether or not he eventually wins the title, he's already winning the game.

( As reported by Peter Bregman)

All New - Modern Tester’s Dictionary

I figured it was time for a review of some modern testing terms.  Feel free to challenge me if you don’t like my definitions, which are very conversational.  I selected terms I find valuable and stayed away from terms I’m bored with (e.g., “Stress Testing”, “Smoke Testing”). 

Afterwards, you can tell me what I’m missing.  Maybe I’ll update the list.  Here we go…

Tester – Never refer to yourself as QA.  That’s old school.  That’s a sign of an unskilled tester.  By now, we know writing software is different than manufacturing cars.  We know we don’t have the power to “assure” quality.  If your title still has “QA” in it, convince your HR department to change it. 

Sapient Tester – A brain-engaged tester.  It is generally used to describe a skilled tester who focuses on human “testing” but uses machines for “checking”.

Manual Tester – A brain-dead tester.  Manual testers focus on “checking”.

Test (noun) – Something that can reveal new information.  Something that takes place in one’s brain.  Tests focus on exploration and learning. 

Check – An observation, linked to a decision rule, resulting in a bit (e.g., Pass/Fail, True/False, Yes/No).  Checks focus on confirmation.  A check may be performed by a machine or a human.  Repetition of the same check is best left to a machine, lest the tester becomes a “Manual Tester”, which is not cool.

Developer – It takes a tester, business analyst, and programmer to develop software; even if they’re just different hats on the same person.  That means if you’re a tester, you’re also a developer.

Programmer – Person on the development team responsible for writing the product code.  They write code that ships.

Prog – Short version of “Programmer”. 

Test Automation Engineer – This is a Tester who specializes in writing automated checks.  This is the best I have so far.  But here are the problems I have with it.  Test Automation Engineers are also programmers who write code.  That means the term “Programmer” is ambiguous.  A Test Automation Engineer has the word “Test” in their title when, arguably, a test can’t be automated.

Heuristic - a fallible method for solving a problem or making a decision.  Like a rule of thumb.  It's fallible though, so use it with care. Why is this term in a tester dictionary?  Skilled testers use heuristics to make quick decisions during testing.  For example: a tester may use a stopping heuristic to know when to stop a test or which test to execute next.  Testers have begun capturing the way they solve problems and creating catchy labels for new heuristics.  Said labels allow testers to share ideas with other testers.  Example: the 'Just In Time Heuristic' reminds us to add test detail as late as possible, because things will change.  Example: the' Jenga Heuristic' reminds us that if we remove too many dependencies from a test, it will easily fall down...instead, try removing one dependency at a time to determine the breaking point.

Test Report – Something a team member or manager may ask a tester for.  The team member is asking for a summary of a tester’s findings thus far. 

Context Driven Testing – an approach to software testing that values context. Example: when joining a new project, Context Driven testers will ask the team what level of documentation is required, as opposed to just writing a test plan because that is what they have always done.  IMO, Context Driven testers are the innovators when it comes to software testing.  They are the folks challenging us to think differently and adjust our approaches as the IT industry changes. 

Bug – Something that bugs someone who matters.

Issue – It may result in a bug.  We don’t have enough information to determine that yet.

Escape – A bug found in production.  A bug that has “escaped” the test environment.  Counting “escapes” may be more valuable than counting “bugs”.

Follow-on Bug – A bug resulting from a different bug.  “we don’t need to log a bug report for BugA because it will go away when BugB gets fixed”. 

Safety Language – Skilled testers use it to tell an honest accurate story of their testing and preserve uncertainty.  Example: “This appears to meet the requirements to some degree”, “I may be wrong”.

Test Idea – less than 140 characters.  Exact steps are not necessary.  The essence of a test should be captured.  Each test ideas should be unique among their set.  The purpose is to plan a test session without spending too much time on details that may change.  Test Ideas replace test cases on my team.

Test Case Fragment – see “Test Idea”.  I think they are the same thing.

AUT – Application Under Test.  The software testers are paid to test. 

Showstopper – An annoying label, usually used to define the priority of bugs.  It is typically overused and results in making everything equally important.

Velocity, Magnitude, Story Points – Misunderstood measurements of work on agile development teams.  Misunderstood because Agile consultants do such a poor job of explaining them.  So just use these terms however you want and you will be no worse off than most Agile teams.

Session-Based-Test-Management (SBTM) – A structured approach to Exploratory Testing that helps testers be more accountable.  It involves dividing up test work into time-based charters (i.e., missions), documenting your test session live, and reviewing your findings with a team member.  The Bach brothers came up with this, I think.  Best free SBTM tool, IMO, is Rapid Reporter.

As reported by :

Sunday, July 8, 2012

Men and women differences in chemistry

Hi friends, I am back and want to continue to write on Anger management/ Emotion management. Before you jump in lets try to understand whats happening at chemical level and who are good at what?

Traditionally the following differences are widely accepted and acknowledged., that for

1. MULTI-TASKING
Women - Multiple process.Women's brains designed to concentrate multiple task at a time.
Women can Watch a TV and Talk over phone and cook.
Men - Single Process. Men's brains designed to concentrate only one work at a time. Men can not watch TV and talk over the phone at the same time. they stop the TV while Talking. They can either watch TV or talk over the phone or cook.

2. LANGUAGE
Women can easily learn many languages. But can not find solutions to problems. Men can not easily learn languages, they can easily solve problems. That's why in average a 3 years old girl has three times higher vocabulary than a 3 year old boy.

3. ANALYTICAL SKILLS
Mens brains has a lot of space for handling the analytical process. They can analyze and find the solution for a process and design a map of a building easily. But If a complex map is viewed by women, they can not understand it. Women can not understand the details of a map easily, For them it is just a dump of lines on a paper.

4. CAR DRIVING.
While driving a car, mans analytical spaces are used in his brain. He can drive a car fastly. If he sees an object at long distance, immediately his brain classifies the object (bus or van or car) direction and speed of the object and he drives accordingly. Where woman take a long time to recognize the object direction/ speed. Mans single process mind stops the audio in the car (if any), then concentrates only on driving.

5. LYING
When men lie to women face to face, they get caught easily. Womans super natural brain observes facial expression 70%, body language 20% and words coming from the mouth 10%. Mens brain does not have this. Women easily lie to men face to face.
So guys, do not lie face to face.

6. PROBLEMS SOLVING
If a man have a lot of problems, his brain clearly classifies the problems and puts them in individual rooms in the brain and then finds the solution one by one. You can see many guys looking at the sky for a long time. If a woman has a lot of problems, her brain can not classify the problems. she wants some one to hear that. After telling everything to a person she goes happily to bed. She does not worry about the problems being solved or not.

7. WHAT THEY WANT
Men want status, success, solutions, big process, etc... But Women want relationship, friends, family, etc...

8. UNHAPPINESS
If women are unhappy with their relations, they can not concentrate on their work. If men are unhappy with their work, they can not concentrate on the relations.

9. SPEECH
Women use indirect language in speech. But Men use direct language.


10. HANDLING EMOTION
Women talk a lot without thinking. Men act a lot without thinking.




Suggested further reading : Men are from Mars, Women are from Venus by John Grey.
You can down load it from the following link xa.yimg.com/kq/groups/21230179/1805388939/name/ladies.pdf