Bug tracking

Purpose: Utility to report issues/ tasks Convey status of each task on list unambiguously Contribution to planning: Plan releases Manage product versions Configuration: Projects: Projects should be clearly defined in the system to avoid any confusions regarding the context of the reported issue/ given task Versions: At least three versions should always be considered in roadmap Status: Enough status codes should be defined to convey the actions being taken without having to spend time on co-ordination for this task. Status transition process: A process that has always worked for me in all the .......................... READ FULL ARTICLE

Over chat – tech team

Just a few simple things to keep in mind .. in suggested order :) Greet Use smileys often Thank for every help Ask precise questions and wait for answers Appreciate them for any positives they have Try to explain reasons/purpose for asking for things from the person Use words like we rather than you or he or she. If you have to, use names - politely. After a couple of talks - practise small talk. Small talk includes talking about anything but work like wheather, a news etc. Try getting casual Don't forget to greet while leaving .......................... READ FULL ARTICLE

Get organized

Here are 10 habits to develop for self organization. In my opinion, this looks like the most practical and a “follow-able” list. How to use? Each of these habits should be learned and practiced one at a time if possible, or 2-3 at a time at the most. You don’t need to adopt all 10 habits. Habits 1-8 are essential. You can consider habits 9 and 10 if possible. The subject: 1. Collect habit Carry a notebook or whatever tool convenient to you and write down any tasks, ideas, projects or other information that pops into your head. Taking it out of your head and onto paper will help you to remember.......................... READ FULL ARTICLE