TrackStudio Overview


Published on

Describes TrackStudio issue tracker

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

TrackStudio Overview

  1. 1. TrackStudio Overview
  2. 2. Presentation overview <ul><li>Overview of Task Management and TrackStudio </li></ul><ul><li>Walk through the as-installed TrackStudio environment </li></ul><ul><li>Question and Answer session </li></ul>
  3. 3. The true nature of Task Management <ul><li>Many different people with different roles </li></ul><ul><li>Roles on each project may not be the same </li></ul><ul><li>Many top-level tasks each of which may spawn sub-tasks </li></ul><ul><li>Different tasks have different workflows </li></ul><ul><li>The same workflows may need to be shared between different projects </li></ul><ul><li>Priorities and dependencies </li></ul>
  4. 4. The nature of Tasks <ul><li>Big bugs have little bugs </li></ul><ul><li>Upon their backs to bite them. </li></ul><ul><li>Little bugs have littler bugs. </li></ul><ul><li>And so, ad infinitum. </li></ul><ul><li>Jonathan Swift 1667 - 1745 </li></ul>
  5. 5. The nature of Plans <ul><li>“ Therefore no plan of operations extends with any certainty beyond the first contact with the main hostile force. ” </li></ul><ul><li>Helmuth von Moltke Prussian field marshal mid-nineteenth century </li></ul>“ no plan survives first contact with the enemy”
  6. 6. Project complexity Department Manager Project Manager Memb1 Memb2 Memb3 Memb4 PROJECTS PROJECTS Operational Department
  7. 7. Project complexity 2 Memb1 Memb2 Memb3 Memb4 PROJECTS PROJECTS Content Management Servs CMS Manager PROJECTS PROJECTS Data Development Memb1 Memb2 Memb3 Memb4 Data Dev Manager PROJECTS PROJECTS Hosting Memb1 Memb2 Hosting Manager PROJECTS PROJECTS Design Memb1 Memb2 Design Manager Project Manager 1 Project Manager 2 Project Manager 3 Project Manager 4 PROJECTS PROJECTS Application Development Memb1 Memb2 Memb3 Memb4 Memb1 Memb2 Memb3 Memb4 App Dev Manager
  8. 8. Project complexity 3 <ul><li>N ot only different users work on different projects but also different projects may require different configurations. </li></ul><ul><li>If, as a C ompany you might have several large customers, each with different workflow s , and be require d to integrate your own workflows with their workflows. </li></ul><ul><li>This is possible with TrackStudio </li></ul>
  9. 9. The ingredients for success <ul><li>Communication and control </li></ul><ul><ul><li>What needs to be done by whom and by when </li></ul></ul><ul><li>Impossible for the project manager to have complete picture </li></ul><ul><ul><li>Polling of task executors to ascertain status becomes impractical and unrealistic </li></ul></ul><ul><li>Everyone needs to be able to have an overview </li></ul><ul><ul><li>Project Manager </li></ul></ul><ul><ul><li>Programme Manager </li></ul></ul><ul><ul><li>Department Manager </li></ul></ul><ul><ul><li>Task Executor </li></ul></ul><ul><li>Everyone needs to be able to have their own view </li></ul><ul><ul><li>Only tasks that are relevant to them </li></ul></ul>
  10. 10. What will help you deliver success? <ul><li>Enterprise-strength task-tracking solution </li></ul>
  11. 11. Essential concepts <ul><li>Tasks and users </li></ul><ul><li>A task can be though of an an object </li></ul><ul><li>Hierarchies, objects and inheritance </li></ul><ul><li>Domain model </li></ul><ul><li>Who you are and where you are </li></ul><ul><li>Soft labels </li></ul><ul><li>Delegated control </li></ul><ul><li>Single interface </li></ul><ul><li>Messages </li></ul>
  12. 12. Tasks and users
  13. 13. Hierarchies <ul><li>H ierarchical organization is a very important for project management tool </li></ul><ul><li>Very few task-tracking packages support it </li></ul>&quot;Work Breakdown Structure (WBS) is a fundamental project management technique for defining and organizing the total scope of a project, using a hierarchical tree structure.&quot; Wikipedia
  14. 14. User and Task tree connections
  15. 15. Single interface – different views
  16. 16. Messages <ul><li>A message encapsulates a number of separate elements into a single action </li></ul><ul><li>State - change, assignment and comment are all handled in one step </li></ul><ul><li>For example, if a support team member were to receive a re ply from customer, he needs to : </li></ul><ul><ul><li>reopen the task. </li></ul></ul><ul><ul><li>assign it to developer </li></ul></ul><ul><ul><li>write comment and attach file from the customer </li></ul></ul><ul><ul><li>submit his own task time </li></ul></ul><ul><li>Within TrackStudio this is handled as a message </li></ul><ul><li>This allows for a powerful search of task history </li></ul>
  17. 17. How TrackStudio meets your needs <ul><li>Connectivity </li></ul><ul><li>Configurability </li></ul><ul><li>Integration </li></ul><ul><li>Extensibility </li></ul>
  18. 18. Connectivity - TrackStudio e-mail <ul><li>Inbound </li></ul><ul><ul><li>E-mail submission </li></ul></ul><ul><ul><ul><li>Filters configured by header or content to direct inbound e-mail to particular tasks. </li></ul></ul></ul><ul><ul><ul><li>Attachments are imported into the system automatically </li></ul></ul></ul><ul><li>Outbound </li></ul><ul><ul><li>E-mail notification </li></ul></ul><ul><ul><ul><li>The creating a task or task-related message can be configured to send an e-mail according to the criteria of the associated filter. </li></ul></ul></ul><ul><ul><ul><li>It is possible to easily to configure who gets what when messages are created. </li></ul></ul></ul><ul><ul><ul><li>Different templates can be specified for different tasks/rules </li></ul></ul></ul><ul><ul><ul><li>High level of detail for developers, low level for customers </li></ul></ul></ul>
  19. 19. Connectivity - TrackStudio e-mail - 2 <ul><li>Outbound - continued </li></ul><ul><ul><li>E-mail digests </li></ul></ul><ul><ul><ul><li>Filter subscription rules can be defined that will generate for any particular user or user group a periodic summary </li></ul></ul></ul><ul><ul><ul><li>Rules are defined per task </li></ul></ul></ul><ul><ul><ul><li>Interval is definable per rule </li></ul></ul></ul><ul><ul><ul><li>Standard filter mechanism used to determine what type of summary gets sent </li></ul></ul></ul><ul><ul><ul><li>Example: List of high priority bugs, not touched in the last 3 days – managers can receive this report every morning </li></ul></ul></ul><ul><ul><li>E-mails sent by triggers </li></ul></ul><ul><ul><ul><li>If it is not possible to define exactly what e-mail you want to be sent using the interface it is possible to define it using a script </li></ul></ul></ul><ul><ul><ul><li>Such e-mails may be sent to other systems/data repositories </li></ul></ul></ul>
  20. 20. Configurability – Workflows Issue Tracking – Issue workflow
  21. 21. Configurability – Workflows - 2 <ul><li>Workflows consist of 4 main components: </li></ul><ul><ul><li>Priorities – an in-built list field. Definable per workflow. </li></ul></ul><ul><ul><li>States – the state in which a task is at any time </li></ul></ul><ul><ul><li>Messages – move task from one state to another </li></ul></ul><ul><ul><li>Custom fields – 10 field types available </li></ul></ul>
  22. 22. Configurability - Workflows - 3 <ul><li>Workflows may be as simple or complex as you wish </li></ul><ul><li>For each Message type it is possible to define who is able to: </li></ul><ul><ul><li>View </li></ul></ul><ul><ul><li>Process </li></ul></ul><ul><ul><li>Be assigned as Handler </li></ul></ul><ul><li>Each Message type may have any number of “resolutions” associated with it </li></ul><ul><li>A “resolution” is a supplementary to the message ie </li></ul><ul><li>Message Resolution </li></ul><ul><li>Reviewed – bug replicated </li></ul>
  23. 23. Configurability - Workflows - 4 <ul><li>Categories are “containers” that connect workflows to tasks </li></ul><ul><ul><li>The same workflow may be used in many categories </li></ul></ul><ul><ul><li>Categories define who can view, create, modify, delete or be initial handler for a task of that category </li></ul></ul><ul><ul><li>Categories also allow you to define a template – headings that will appear in the Task description box </li></ul></ul><ul><ul><li>Categories have Create task and Edit task triggers </li></ul></ul><ul><li>Relations are defined within categories and determine what sub-tasks can be created as children of a task of that category </li></ul><ul><ul><li>It’s easy to miss the step of creating relations! </li></ul></ul>
  24. 24. Configurability – permissions model <ul><li>Who is connected to what </li></ul><ul><li>What rights does own/base status provide to user </li></ul><ul><li>Ability to supplement or override own/base status within the context of a task </li></ul><ul><li>Categories define who is able to view, create, modify, delete or be initial handler for a task of that category </li></ul><ul><li>Within workflows it is possible to define who is able to view, process or be assigned as handler for any message type </li></ul>
  25. 25. Statuses <ul><li>Three types of status might be usefully considered: </li></ul><ul><ul><li>Statuses with rights that are to be assigned to users as an own/base status </li></ul></ul><ul><ul><li>Statuses with no rights - merely to be used as &quot;labels&quot; that can be identified in the context of workflows and categories. </li></ul></ul><ul><ul><li>Statuses with rights that are to be assigned to users depending on their role within the context of a task. These statuses are also used to identify who may do what in the context of workflows and categories. </li></ul></ul>
  26. 26. Status-task permissions
  27. 27. Status-user permissions
  28. 28. State-Message-Status map
  29. 29. Extensibility <ul><li>SOAP API </li></ul><ul><ul><li>very powerful, just thin wrap over the kernel </li></ul></ul><ul><li>Source Code </li></ul><ul><ul><li>anything is possible here! </li></ul></ul><ul><li>Eclipse plugin </li></ul><ul><ul><li>very simple, just a browser opened in Eclipse window </li></ul></ul>
  30. 30. Integration <ul><li>E-mail messaging </li></ul><ul><li>“ back-end” database connectivity </li></ul><ul><li>Scripts and triggers </li></ul><ul><li>SVNKit library used for SVN repository interaction </li></ul>
  31. 31. Scripts and Triggers <ul><li>For each message type it is possible to specify a script that will run for each of up to three events. </li></ul><ul><li>Each event is called a trigger. </li></ul><ul><ul><li>BEFORE Trigger - action which is executed before the message is created . </li></ul></ul><ul><ul><li>INSTEAD OF Trigger - action which is executed instead of message being created . </li></ul></ul><ul><ul><li>AFTER Trigger - action which is executed after an the message has been created . </li></ul></ul><ul><li>Scripts are small pieces of code that use the API to modify the application’s behaviour. </li></ul>
  32. 32. What do you want from TrackStudio?   Simple Sophisticated Organisational scope Single department Enterprise wide Task complexity Single or few simple workflows Many and/or complex workflows Role variability Everyone within the department has same role all the time Individuals’ roles within tasks vary depending on task Degree of control Low level High level External Users No external users External users Multi-domain capability Don’t want the ability to create separate root domains Want to retain the ability to create separate root domains
  33. 33. What more might you want? <ul><li>The only limit is your imagination ! </li></ul>
  34. 34. Time tracking <ul><li>Built-in task duration field </li></ul><ul><li>Each time a message is created the user is able to enter the time spent working on the task on that occasion </li></ul><ul><li>A ll the individually entered times are summed both within the task and the in the parent task and so on up the task hierarchy </li></ul>
  35. 35. Reporting <ul><li>Report creation </li></ul><ul><ul><li>Permission to create reports can be granted in a context-sensitive way to either users or user groups </li></ul></ul><ul><ul><li>Reports are defined per task </li></ul></ul><ul><ul><li>Standard filter mechanism used to determine what the report will contain </li></ul></ul><ul><ul><li>Four different in-built report types available: </li></ul></ul><ul><ul><ul><li>List - display s the list of tasks as a table. C onfigure the columns and the sort order by specify filtering conditions. </li></ul></ul></ul><ul><ul><ul><li>Detailed - display s all task fields that have values. </li></ul></ul></ul><ul><ul><ul><li>Distribution - group s tasks and allows the use of aggregate functions ( Avg, Min, Max, Sum ) for each group . </li></ul></ul></ul><ul><ul><ul><li>UserWorkload - display s information about the time (actual time) your subordinates worked on subtasks of a task. </li></ul></ul></ul><ul><ul><li>All reports can be exported as CSV/XML for use by third-party applications </li></ul></ul>
  36. 36. Summary - key differentiators <ul><li>Hierarchical work breakdown </li></ul><ul><li>Support for matrix management </li></ul><ul><li>Project-specific customisation </li></ul><ul><li>Highly granular permissions model </li></ul><ul><li>Massive extensibility </li></ul><ul><li>Delegated authorities and responsibilities </li></ul>
  37. 37. Commercial offering <ul><li>All product packages, except starter pack, have unlimited user licences </li></ul><ul><li>Excellent “bang per buck” ratio </li></ul><ul><li>Competitively priced support and upgrade package </li></ul><ul><li>Source code available </li></ul><ul><li>Single application can be configured to service many different “task tracking” needs </li></ul><ul><li>Consolidation of differing “task tracking” requirements within a single application reduces training and maintenance over head </li></ul>
  38. 38. Corporate offering <ul><li>Established but leading-edge product since 2001 </li></ul><ul><li>Open user forum </li></ul><ul><li>Small and dedicated team </li></ul><ul><li>Privately held and debt free </li></ul><ul><li>Quality and sophistication of the product should outweigh any concern about the company </li></ul>
  39. 39. Thank you for listening <ul><li>Any questions? </li></ul>