ToDo Cycle - how we work

From account manager to developer and tester: see how we all interact to make our clients happy and how we manage project tasks.

Our ToDo Cycle is a ten-step process and has three aims

• ensure consistent quality
• never forget a task
• alway do the most important first

It is based on telepark.wiki's ToDo List business module.

Step 1, our customer sends in an observation, bug information or change request either by, phone, email, IM / Skype, fax or a combination of these. His telepark account manager checks and validates the observation (step 2) and confirms it to the customer (step 3). He Step enters a new ToDo item, uploads a screenshot or document and marks the item either as Bug (no cost to customer), Service (part of service contract with customer), Quote (a new request which requires a quotation) or Other (step 4).

In step 5, both the tester(s) and developer(s) get an automatic notification about the new ToDo item and they start an interactive process of "solving, testing, and solving-until-right". Each step of the process is supported by notifications (steps 6 and 7). Enduser customers can be explicitely excluded from intermediate notifications, only being informed about new ToDo's and when they are done, for example. Finally, in step 8 the tester marks a ToDo item as "done" , which triggers  a notification to the account manager who confirms to the customer that the issue was solved (steps 9 and 10).

It has proven an effective approach to manage multi-project tasks and to be consistent in high-quality, on time deliverables.

Buy telepark.wiki online and benefit from a free package of exclusive business modules such as dynamic ToDo Lists.