• Think Aloud Protocol

    Think Aloud Protocol (TAP) – Developed by Clayton Lewis, is a Software testing protocol where the user is allowed to talk or express his/her experience while performing a set of specified tasks. They are asked to say whatever they are looking at, thinking, doing, and feeling as they go about their task. Appears interesting to […]

  • Oslo again…

    Models! Models! Models! thats all what matters… I like working with models ( but Canis lupus familiaris  vision – only 2D 🙂 ) & diagrams partly because I have been good at drawing & painting during my school days and also because models make me think, be imaginative and be creative. Creative writing is possible but […]

  • Hello Calvin!

    I wish I could duplicate myself like calvin, I will be able to work on different technologies with different people all synced up and I could go to shopping too… and one of me left behind to attend my family, one for my friends! all said, here is today’s strip. from Calvin and Hobbes

  • A Metaphor a day, keeps me on my toes

    Metaphors or visuals to describe the application is a very powerful technique to avoid catastrophes in software development life cycle. Use as many metaphors as possible so that everyone on the project is aware of the concept, the main intent, the ‘ask’. I myself have used images where I was not able to explain in […]

  • Trying to change something? Its fun, its a challenge.

    I face challenges at workplace trying to bring change, but I realized the trick is communication – communicate, communicate, communicate. If your idea for change is not feasible or just impossible, you’ll instantly know from your feedback mechanism. I get an idea and I feel as if sitting on a pin; they click, I yak […]

  • Serenity Prayer

    “Know what I pray for? The strength to change what I can, the inability to accept what I can’t and the incapacity to tell the difference.” – Calvin and Hobbes Calvin and Hobbes variation of the Serenity Prayer.  

  • Requirements are the Software

    What does it really take to convert requirements into working software? I think the trick is getting the requirements right; if you do not understand the requirements, no matter what skill/technology you master, your effort goes to trash. The best way is asking for clarifications and getting a clear picture of what the user or customer really wants the software […]

  • Live Framework

      Click here for enlarged image   Experience a new world of technology with Live Services  

  • Are you a Scrummer?

    Classic story of the pig and chicken More about scrum and a bunch of other scrum cartoons at www.implementingscrum.com