Tothal Systems

Out there, in the working field you sometime find yourself facing or handling all kinds of customers. When you have to deliver “bad news”, say “no” to customers or to people in power, you are often tempted to placate with a “yes”. It is indeed a challenge trying to balance the need to be customer-oriented and the need to deliver difficult messages to our customers. You always want to provide exceptional service to both your internal and external customers. However, in the real world, things might go wrong, and mistakes are made. Nevertheless, your goal is to have a happy customer through communication, which involves respect for the boundaries of oneself and others. It also presumes an interest in the fulfillment of needs and wants through cooperation. We All Work for the Customer. Obviously! But is it always visible, at hand? Let’s try a schematic visualization on the situation. The example is a fairly big organization, with internal and external value and cash flow. What can be prett...

People always complain about the poor quality of requirements, but usually that all they do say: requirements are a mess. What would really be useful is they say what’s wrong with them, why they don’t like then, what to improve, what cannot be implemented or tested; generally, where they need to be able to do their work. There are of course some recommendations and rules to writing requirements. Good practice and a complete document nevertheless come following an optimal combination between experience, product knowledge, industry know-how and a solid and clear systematic approach. There are requirements format rules, and document structural guidelines/checklists that a requirement set for any product should follow. Writing clear and unique requirements Requirements unicity may be expressed in a complementary fashion: each thing /requirement must be described just once, in one place (avoid redundancy and support consistency), one requirement must specify a single thing (add clarity and ...