latest news
2008-03-27
We just launched this website: sphene.net - we are still adding content so expect more to come.
Hey, we have Signatures !!! Great, isn't it ? 
Projects
ProjectsBack to Snip <-- Previous Change | Next Change -->
| Diff Summary | |||||
|---|---|---|---|---|---|
| Title | |||||
| Date | 2008-03-29 10:32:50 | 2008-03-29 11:36:53 | |||
| Editor | Herbert Poul | Herbert Poul | |||
| Tags | |||||
| 2008-03-29 10:32:50 by Herbert Poul | 2008-03-29 11:36:53 by Herbert Poul | ||||
|---|---|---|---|---|---|
| 12 | there is one tool to merge the functionality of a | 12 | there is one tool to merge the functionality of a | ||
| > | Project Management | > | Project Management | ||
| 13 | and CRM tool into one package. | 13 | and CRM tool into one package. | ||
| 14 | 14 | ||||
| 15 | 15 | ||||
| 16 | ## Project Management | 16 | ## Project Management | ||
| n | 17 | It's possible to create a full featured project pl | n | ||
| > | an and assign all tasks to the corresponding proje | ||||
| > | ct memebers. | ||||
| 18 | In addition to a "normal" project plan you can cre | ||||
| > | ate a netplan and all necessary charts you will ne | ||||
| > | ed to control the whole project. | ||||
| 19 | 17 | ||||
| n | 20 | ## Taskamangement | n | 18 | - Plan your projects by defining milestones, dead |
| > | lines and responsibilities of team members. | ||||
| 21 | As mentioned before, all the tasks which can occur | 19 | - Aggregated reports of all tasks and tickets asso | ||
| > | in a project or beside a project can be managed w | > | ciated with your projects allow you to control and | ||
| > | ith these functions. | > | prioritize every aspect of your project. | ||
| 22 | Every task consists of exactly one responsible per | ||||
| > | son and a variable count of involved people. | ||||
| 23 | 20 | ||||
| n | n | 21 | |||
| 22 | ## Taskmangement | ||||
| 23 | |||||
| 24 | Tasks are specific responsibilities or duties with | ||||
| > | in a project. Every task has one responsible team | ||||
| > | member, a given priority, time estimate and option | ||||
| > | ally a dead line. Tasks are organized in a hierarc | ||||
| > | hical tree and can be easily created to produce sm | ||||
| > | all and manageable work units for each project mem | ||||
| > | ber. | ||||
| 25 | |||||
| 26 | |||||
| 24 | ## Ticketmanagement | 27 | ## Ticketmanagement/CRM | ||
| 25 | A huge part of Inosit is the integrated Ticketmana | 28 | |||
| > | gement. It's kind of a taskmanagement containing a | ||||
| > | history with all changes and all newly gained inf | ||||
| > | ormation to a topic. | ||||
| 26 | A ticket can e created by a customer or by a membe | 29 | Ticketmanagement is an important part of Inosit. I | ||
| > | r of the company by itself. | > | t allows you to make customer support part of proj | ||
| > | ect management to get a better grasp of the proble | ||||
| > | ms and challenges within each project. In addition | ||||
| > | it allows the support team to automatically get a | ||||
| > | ll knowledge of the development tasks and get insi | ||||
| > | ght into possible peculiarities or design decision | ||||
| > | s. | ||||
| 27 | Every ticktet contains of a few basic information | 30 | |||
| > | fields, just like creator, owner and some addition | ||||
| > | al information as time worked on it. Another featu | ||||
| > | re is, to assign tickets to the different costumer | ||||
| > | s manually and also with a predefined fitler metho | ||||
| > | dic. Each costumer is able to view the status of t | ||||
| > | he different tickets of his company by logging int | ||||
| > | o a webinterface, where all tickets are listed. | ||||
| 31 | Tickets can be associated with customers either by | ||||
| > | an automatic filter based on email address or man | ||||
| > | ually by the support team. Customers will get acce | ||||
| > | ss to all their tickets to see the current status | ||||
| > | and assignment of the tickets, upload additional a | ||||
| > | ttachments, add comments or close them. It is also | ||||
| > | possible for customers to create tickets through | ||||
| > | a web form and assign meta properties - like affec | ||||
| > | ted installation, URL to reproduce the problem, et | ||||
| > | c. | ||||
| 32 | |||||
| 28 | 33 | ||||
| 29 | ## Document Sharing | 34 | ## Document Sharing | ||
| t | 30 | Every phase/task/ticket can have additional docume | t | 35 | Every phase/task/ticket can have additional file a |
| > | nts, just like word-files or anything else. You ca | > | ttachments like word documents or spreadsheets. Yo | ||
| > | n connect every document to a phase/task/ticket to | > | u can connect every document to a phase/task/ticke | ||
| > | provide more information to this topic. If a new | > | t to provide more information to this topic. If a | ||
| > | version of a document is available, the old versio | > | new version of a document is available, the old ve | ||
| > | n can be archived so the new one replaces it. | > | rsion can be archived so the new one replaces it. | ||
| 31 | 36 | ||||
| 32 | 37 | ||||
| 33 | # Sphene Community Tools (SCT) | 38 | # Sphene Community Tools (SCT) | ||
| 34 | 39 | ||||
| 35 | {img id=21 resize=150xX align=left} | 40 | {img id=21 resize=150xX align=left} | ||