{"id":1814,"date":"2013-11-11T14:35:24","date_gmt":"2013-11-11T14:35:24","guid":{"rendered":"https:\/\/www.cmwlab.com\/blog\/?p=1814"},"modified":"2023-02-15T14:58:15","modified_gmt":"2023-02-15T14:58:15","slug":"project-status-tracking","status":"publish","type":"post","link":"https:\/\/www.cmwlab.com\/blog\/project-status-tracking\/","title":{"rendered":"Project Status Tracking (for Dummies)"},"content":{"rendered":"

Today I\u2019m going to tell you about how Comindware Tracker<\/a> can help you in the case when you start working as the project manager on a project you have little knowledge of. Of course, information from this article will be useful to experienced project leaders too. But, most probably, they have already discovered best practices to manage their projects. So, my main audience for today is \u2018accidental\u2019 project managers.<\/p>\r\n

\r\n\"CMW<\/a><\/p>\r\n

Your main task as a project manager is to build an effective process, where every employee will always know what to do and your whole team will deliver results at the specified time. If you\u2019re a novice in project management<\/a>, your first idea can be to manually control each employee\u2019s activities. For example you will always stand behind their backs and watch what they are currently doing & give them advice. In the project management world this is called \u2018micromanagement\u2019 and it\u2019s a great way to fail the project. Remember \u2013 do not try to control each employee personally. You must rule processes, not personalities.<\/p>\r\n\r\n

First of all \u2013 discover your team\u2019s current structure. What are the sub-teams of your team, who are leaders of these sub-teams, what are the tasks these sub-teams perform and in which order? With the right approach, you can discover this information in your first day as the project manager. Do not hesitate to ask your colleagues \u2013 you\u2019re the new man and they know more than you do about this team.<\/p>\r\n\r\n

The next step is to design your team processes in Comindware Tracker Workflow Designer. Let\u2019s use the next example. You\u2019re a project manager in a Software Development Company and your task is to support existing software and improve it with new features. Let\u2019s start with support department\u2019 activities.<\/p>\r\n\r\n

On your first day, you have discovered that the support team receives requests from clients, tries to find if the client\u2019s problems can be solved in the current version of your product and, if not, creates feature requests for the development team. John Curry is the leader of the support team. Open Comindware Tracker Workflow Designer and create a simple three step process \u2013 \u2018Support Request received\u2019, \u2018Support Request Resolved\u2019 and \u2018Create feature request\u2019. Draw transitions between these steps and make \u2018John Curry\u2019 the responsible person for the \u2018Create Feature request\u2019 step.<\/p>\r\n\r\n

\"Project<\/a>\r\n

\r\n\"Project<\/a><\/p>\r\n\r\n

With this simple high-level process, you can be sure that starting from tomorrow, you will see all support requests in Comindware Tracker and \u2018John Curry\u2019 will create feature requests for requests, which cannot be resolved in the current product. You can start to use Comindware Tracker reporting tools to see reports about features that are missing, percentage of resolved requests, how many requests are resolved per day, etc. This will be a great source of information for your next activity.<\/p>\r\n\r\n

So what is my next activity \u2013 you will ask? This high-level process design is good for several days. But it\u2019s only the beginning \u2013 you can\u2019t continue with that. In next few days you should monitor who creates support request objects, what information about the request is required, to whom support requests are reassigned after creation, etc. After sometime, you should redesign your process, targeting it to be more effective and corresponding to the real-life process.<\/p>\r\n\r\n

Most probably, you will discover that when a support request is created, the creator should fill in the \u2018Product Area\u2019 field. And after filling in this field, the process should be automatically transferred to the person, who is an expert in this area. So, open your process in Workflow Designer, add a new field to your process and place it into the form.<\/p>\r\n\r\n\"Project<\/a>\r\n\r\n

After that, go to the \u2018Support Request received\u2019 step settings and let\u2019s make the request auto-assigned to the appropriate person, depending on the selected \u2018Area\u2019 field. For that, we must use Comindware Expression language \u2013 it is simple and an easy-to-learn language, which allows you to customize many workflow behavior aspects. Using the following expression, we auto-assign the task to the account with ID = \u2018account.1\u2019, when the support request is in the \u2018Integration\u2019 area, and to \u2018account.2\u2019 if there is a second account.<\/p>\r\n\r\n\"Project<\/a>\r\n\r\n

So, you\u2019ve just improved your process and it now corresponds to what happened in real life. But is that enough? The answer is always \u2018No\u2019 \u2013 you should never stop improving your processes, interacting with your colleagues, building your best team. Do not hesitate to contact our support team for any questions you will have with Comindware Tracker. And, I hope, you will feel comfortable in your new status of project manager.\r\n\r\n

P.S.: almost forgot to mention \u2013 Comindware is such a generous company, that it has prepared professionally designed processes for several areas \u2013 like Software Development<\/a>, Finance and Administration<\/a>, IT Help Desk<\/a>, Human Resources<\/a>, Compliance and Policy Initiatives<\/a>. You can install these processes and discover best practices by going to the \u2018Menu\u2019 tab in Comindware Tracker UI, and pressing the \u2018One-click solution Setup\u2019 button.<\/p>\r\n\r\n

\n \n\n Get a 30-day trial!\n\n <\/a>\n<\/section>\r\n\r\n
\n\t
\n