Sie suchten nach: ZCOPETip

ZCOPE Tip: Connections (task lists, milestones, documents, blog posts)


In ZCOPE you can connect documents and blog posts with task lists and tasks.

I will illustrate this tip with a case study. Let‘s suppose the task list is called „Design website“ and there is a task called „header image“.

The design company uploads a draft for the image and connects it with the task. At the same time a conversation resp. feedback is started in the blog. The design company writes that the first draft was made according to the requirements mentioned at the last meeting but that it became obvious during the design process that the text was too long and if it could be shortened. Also this post will be connected to the task. The customer sends a suggestion for the shorter text and wants the font colour to be slightly darker. The design company edits the image and uploads the new version.

A corresponding icon will be shown with the task if it‘s connected to a document or a blog post. By clicking on the icon one gets to the latest version of the document or the blog post.

ZCOPE Support am 19. November 2009 - 9:40 Uhr

ZCOPE Tip: iCal


As it becomes apparent, tool that can be used in combination with conventional resp. already adopted programs have a higher shot at being accepted.

Therefore milestones and dates in ZCOPE can be imported into the own calendar (Outlook, iCal, Google calendar, etc.). These programs are used a lot and thus reminders are in effectively noticed. Additionally it’s possible to be reminded by e-mail of course.

ZCOPE Support am 12. November 2009 - 10:03 Uhr

ZCOPE Tip: Tagging

ZCOPE_Blog_tagcloudImho tags are a fantastic invention. But one must know how to wisely use them to get the most out of this function.

In ZCOPE, task lists, tasks, milestones, dates, budgets, documents and blog entries can be tagged. You may want to apply a unified wording as to find all the relevant elements. Best to have a look into the existing tag cloud if an adequate term has already been used.

By experience I can say it is always good to have several tags with one element. It helps also with inconsistent wording – via one of the possible terms you mostly find something.

Besides the positioning of task lists and tasks according to their priority, it‘s possible to prioritise via tags as well: we use e.g. „important“, „urgent“ and „earmark“ in our further development project.

The tags can also be renamed or deleted, if you misspelled a word or don‘t need the term any longer.

A small tip for the tagging outside of ZCOPE: on I work with e.g. „2read“ oder „2blog“. Over time a quite considerable collection arised in this way – in case creativity leaves a lot to be desired ;-)

What tips and tricks do you have when it comes to tagging?

ZCOPE Support am 4. November 2009 - 10:29 Uhr

ZCOPE Tip: To start with a to do list


You may start your projects in ZCOPE as you wish, one possible start is the to do list. Here’s a short instruction how we do it:

For this purpose I create a task list and fill it with all the tasks that come to my mind. Once this is done I think of an appropriate grouping of tasks and create new task lists based on that. Then I move the tasks from the original to do list into the corresponding new task list: in ZCOPE you do that by drag & drop, it’s as simple as that.

We used this approach also for a SCRUM sprint: the single task lists stand fort he calendar weeks (CW), where we placed the tasks from the original to do list. In this way we could even image dependencies: What must be finished at first, goes into an earlier CW as the one depending on it. At the weekly meetings we talked about the tasks still open and moved them in a future CW if necessary.

All in the purpose of agile project management changes appeared during the sprint and we had to redispose. Thereto we created new task lists (Sprint 2 CW Y, etc.) and moved some of the tasks from the old sprint (Sprint 1 CW 1, etc.) into them. All the remaining tasks from the old sprint now are in one single task list (Sprint 1) until needed and planned.

Conclusion: The rescheduling was done in very little time, tasks of the postponed sprint won’t be lost, but aren’t in the way. Well, a successful experiment ;-)

ZCOPE Support am 20. Oktober 2009 - 15:31 Uhr
Feeling curious? Try it out for free!