CONTENT<\/h5>\n\n- Foreword: the most relevant requirements for the IT sector<\/a><\/li>\n
- The different instances of workflow management in IT teams<\/a><\/li>\n
- 1. Co-existence of projects with different course and type<\/a><\/li>\n
- 1.1. Operator load calculation <\/a><\/li>\n
- 1.2. Integration with cost management<\/a><\/li>\n
- 2. Managing workflows and bottlenecks<\/a><\/li>\n
- 2.1. Dependencies<\/a><\/li>\n
- 2.2. The timeline<\/a><\/li>\n
- 3. Agilit\u00e0 nella gestione dei flussi grazie ai to-do<\/a><\/li>\n
- Twproject: lo strumento ideale per ottimizzare i flussi nelle aziende IT<\/a><\/li>\n\n<\/ul>\n<\/div>\n\n\n\n
In this article, we will focus on the main problems IT companies face daily in project management<\/strong> and look at some solutions to solve them.<\/p>\n\n\n\nTwproject<\/strong> is well acquainted with workflow issues in projects<\/a><\/strong>, both through feedback from its users and through internal experience of its team.<\/p>\n\n\n\nThis is why we believe we can share some useful strategies for dealing with the<\/strong> main issues <\/strong>and the best tools to handle them.<\/p>\n\n\n\n<\/a><\/p>\n\n\n\nForeword: the most relevant requirements for the IT sector<\/h2>\n\n\n\n
Before getting to know these tools, let’s start with the basics: how does the IT world approach process optimisation tools? How do IT project managers<\/strong> evaluate and choose tools?<\/p>\n\n\n\nThis is a sector that is certainly open to new developments in technology<\/strong> and where the desire to optimise and speed up processes dominates.<\/p>\n\n\n\nEfficiency in project execution<\/strong> is certainly one of the most important goals in an IT company, and we will now see how it can be achieved.<\/p>\n\n\n\n<\/a><\/p>\n\n\n\nThe different instances of workflow management in IT teams<\/h2>\n\n\n\n
Let us now look at the specific challenges IT teams face every day, and at the same time see the main issues and tools that can help them change course<\/strong>.<\/p>\n\n\n\nIT departments highly value improved internal efficiency and corporate reputation, so we are confident that these strategies will prove useful.<\/p>\n\n\n\n
It is always important to bear in mind that the whole team<\/strong> must be able to reap the benefits of using management tools. This will help to reduce the start-up<\/strong> phase <\/strong>and will immediately lead to an improvement in flows<\/strong>.<\/p>\n\n\n\n![\"workflow](\"https:\/\/twproject.com\/blog\/wp-content\/uploads\/2024\/08\/flusso-di-lavoro-840x560.png\")
<\/figure>\n\n\n\n<\/a><\/p>\n\n\n\n1. Co-existence of projects with different course and type<\/h2>\n\n\n\n
The first effort that IT project managers make every day concerns delivery<\/strong> times <\/strong>that are not always easy to meet.<\/p>\n\n\n\nTime schedules planned at the beginning are often postponed due to a non-linear workflow<\/strong> that gets jammed easily.<\/p>\n\n\n\nThe main cause that in our opinion risks slowing down workflows in IT teams is the coexistence of projects of different natures<\/strong>.<\/p>\n\n\n\nIn IT companies, in fact, it is very common for staff to deal with various types of projects at the same time in their daily work.<\/p>\n\n\n\n
- There are the actual projects<\/strong>, with a beginning, a duration and an end, the load of which accumulate over the next days if not done on time.
<\/li>- Then there is the maintenance activity <\/strong>that takes place on a more or less regular basis during the course of the year and that must also be counted in the operator’s load.
<\/li>- Finally, there are the \u2018tickets<\/strong>\u2019, i.e. those activities that do not have a start and end date but represent micro-activities, such as bug fixes or small occasional requests.<\/li><\/ul>\n\n\n\n
The latter in particular can be a major cause of delays and <\/strong>bottlenecks<\/strong> <\/a>as they interrupt the regular workflow.<\/p>\n\n\n\nAs a matter of fact, each of these activities is inherently different and should not be treated in the same way.<\/p>\n\n\n\n
There are strategies and tools designed specifically to manage this difference in projects and which greatly help to plan work by calculating how much time each of these activities requires from the project team<\/strong>.<\/p>\n\n\n\n<\/a><\/p>\n\n\n\n1.1. Operator load calculation<\/h3>\n\n\n\n
The first problem caused by these different activities is that they affect the workload of the operators<\/strong> differently.<\/p>\n\n\n\nFor example, in some cases these activities will accumulate over the next few days if not carried out promptly, and increase the daily work rate until the project deadline. In other cases they may be postponed, but it is always important to calculate their incidence in the team load.<\/p>\n\n\n\n
Managing operator load is not an easy task and therefore it can be useful to use workload management software<\/a><\/strong> in projects that allows for detailed planning, taking into account the differences among projects, as seen so far.<\/p>\n\n\n\nTwproject<\/a><\/strong>, for example, allows each project to be assigned a different value from the three listed above and thus weight the workload<\/a><\/strong> of the operators, taking into account the fact that each project behaves differently depending on its type.<\/p>\n\n\n\n![\"resources](\"https:\/\/twproject.com\/blog\/wp-content\/uploads\/2022\/01\/spot-workload-840x239.png\")
<\/figure>\n\n\n\nThis helps to avoid overloading<\/strong> of team members and to optimise workflows in IT teams at an early stage of planning.<\/p>\n\n\n\nIn fact, if we plan more carefully<\/strong>, taking into account this threefold task of team members, delivery times can be better met and the work as a whole will become smoother.<\/p>\n\n\n\n<\/a><\/p>\n\n\n\n1.2. Integration with cost management<\/h3>\n\n\n\n
In addition, another reason for segmenting the different types of projects is the better reporting accuracy<\/strong> we will achieve.<\/p>\n\n\n\nFor a company with many projects underway, of different types and trends, work reporting and invoicing can be a daunting task.<\/p>\n\n\n\n
A good solution may be to use a work planning system with integrated cost management<\/a><\/strong>, which automatically records the work done by the team, but at the same time allows all incidental expenses to be recorded.<\/p>\n\n\n\nUsing a comprehensive platform such as Twproject<\/strong>, the data will be updated automatically<\/strong> and a comparative analysis between estimated and actual work can be carried out.<\/p>\n\n\n\nUnlike many other project management software, Twproject <\/strong>offers timely and accurate work tracking<\/strong>, allowing you to stay up-to-date on internal costs, resource work and margins, providing transparency internally and to the customer.<\/p>\n\n\n\n<\/a><\/p>\n\n\n\n2. Managing workflows and bottlenecks<\/h2>\n\n\n\n
Moving on to issues concerning project execution, we identified as a second problem the lack of focus on the sequencing of work phases<\/strong>.<\/p>\n\n\n\nAs we have seen, a non-fluent work organisation can lead to the bottleneck phenomenon<\/strong>.<\/p>\n\n\n\nThis is an annoying slippage in the time schedule for project execution. Causes of interruptions in the execution process on planned projects can be tickets to be processed, a technical urgency to be handled, and so on.<\/p>\n\n\n\n
It is often difficult to pinpoint the exact point in the workflow where this blockage occurs<\/strong>; it may therefore make sense to equip oneself with tools that visually show the process steps and thus highlight the critical points.<\/p>\n\n\n\nThe best example of these tools is the Gantt chart<\/a><\/strong>.<\/p>\n\n\n\nOnce used as a simple initial planning schedule, today this tool has become much more dynamic <\/strong>and follows us for the entire project duration.<\/p>\n\n\n\nIt is because of this interactivity that the Gantt diagram is now a recommended tool for all project teams, even the most agile<\/a><\/strong> ones such as IT teams.<\/p>\n\n\n\n<\/a><\/p>\n\n\n\n2.1. Dependencies<\/h3>\n\n\n\n
A good Gantt chart<\/strong> allows us to link the different project phases together and set up their different types of dependencies<\/a><\/strong>.<\/p>\n\n\n\nFirst of all, we have to list the project activities and set up our WBS <\/strong>(Work Breakdown Structure<\/strong>), which as the name implies divides the project into hierarchically ordered work blocks.<\/p>\n\n\n\nSubsequently, our WBS can be visualised as a Gantt chart that will allow us to easily link activities together.<\/p>\n\n\n\n
The more accurate and realistic the correlation between the phases and sub-phases<\/strong>, the more we will be able to identify problems causing delays, blockages or overruns.<\/p>\n\n\n\nIf we use project management software such as Twproject<\/strong>, the Gantt chart can be created in just a few minutes: thanks to it, it is easy to realise how the work is organised and to easily assign tasks to the various assignees.<\/p>\n\n\n\n<\/a><\/p>\n\n\n\n2.2. The timeline<\/h3>\n\n\n\n
When the work starts and it is therefore necessary to monitor and analyse workflows, the Gantt chart is particularly well suited to perform this analysis.<\/p>\n\n\n\n
With Twproject, you can use the Project Timeline<\/a><\/strong>, a tool within the Gantt as well as on the statistics page, which allows you to easily identify the causes of project delays.<\/p>\n\n\n\nThe Timeline represents the historical memory of the project, which records everything that was initially planned in the start-up phase<\/strong>.<\/p>\n\n\n\nSubsequently, the Timeline keeps track of all project variances<\/a><\/strong> automatically, without the project manager having to explicitly note them down.<\/p>\n\n\n\nIf, for example, a delivery date is changed, this shift will be recorded in the timeline and at the end of the project it will be possible to review the exact moment when the timeline changed.<\/p>\n\n\n\n![\"project](\"https:\/\/twproject.com\/blog\/wp-content\/uploads\/2024\/02\/eventi-su-timeline.gif\")
<\/figure>\n\n\n\n<\/p>\n\n\n\n
In the IT world, it is very easy for this to happen, especially due to the coexistence of several ongoing projects, as we have seen.<\/p>\n\n\n\n
Knowing the causes of delays is very useful to plan more accurately in the future and helps to avoid the notorious bottlenecks<\/strong> we often run into if not wisely managed.<\/p>\n\n\n\n<\/a><\/p>\n\n\n\nAgility in workflow management thanks to ToDo’s<\/h2>\n\n\n\n
So, after having carefully calculated the workload of operators and planned the work steps accurately, let’s finally see what is the last step to improve workflows in the execution phase<\/strong>.<\/p>\n\n\n\nOne of the most difficult tasks during this phase is the optimisation in the distribution of deliveries and tasks<\/strong>, which if not done effectively can negatively affect the productivity of the team.<\/p>\n\n\n\nOften when embarking on a new project, the amount of information that needs to be communicated to the project team may seem overwhelming.<\/p>\n\n\n\n
But if you break down all activities into small, precise<\/strong> tasks<\/strong><\/a>, not only do you communicate effectively with the team, but you get a clearer picture for the whole team.<\/p>\n\n\n\nIT teams usually like agile ways of managin workflows<\/strong>, and in this Twproject has several solutions that are highly appreciated by them.<\/p>\n\n\n\nIts ToDo’s<\/a> are very flexible<\/strong> because they can contain a lot of information such as assignee, tag, type, attachments, etc.<\/p>\n\n\n\n![\"to-do](\"https:\/\/twproject.com\/blog\/wp-content\/uploads\/2023\/03\/to-do_list-1-840x368.jpg\")
<\/figure>\n\n\n\n<\/p>\n\n\n\n
We can add comments to them, mentioning the recipient. We can filter them in multiple ways and organise them by priority. In short, they have everything that can be useful to an agile team that needs an efficient and fast communication tool.<\/p>\n\n\n\n
They can also be managed via the Twproject Kanban visual board<\/a><\/strong>, which contains some special functions such as the column sorting method. Not only priority, but also sorting by project, by assignee, by status and type.<\/p>\n\n\n\nToDo’s are functional for any type of work<\/strong>, be it related to classic projects, maintenance or ticketing.<\/a><\/p>\n\n\n\n<\/a><\/p>\n\n\n\nTwproject: the ideal tool for optimising workflows in IT teams<\/h2>\n\n\n\n
To sum up, we know that IT companies are those most attentive to new technological developments and those most inclined to adopt software tools<\/a><\/strong> to improve internal processes<\/strong>.<\/p>\n\n\n\nHowever, it is just as likely that IT companies will decide to make handmade systems, being software producers themselves.<\/p>\n\n\n\n
But as we know today there is an increasing segmentation in the software industry<\/a><\/strong> and therefore the choice to internalise the development of business management systems<\/strong> is not always successful and can divert attention away from more profitable projects.<\/p>\n\n\n\nThat is why it is best to turn to those who have decades of experience in the field and know how to anticipate and solve the needs of IT companies in project management<\/strong>.<\/p>\n\n\n\nOur customers working in the IT sector have no doubt: Twproject <\/a>has everything they need<\/strong> to simplify IT project management.<\/p>\n\n\n\n <\/p>
\tWith Twproject, projects run more smoothly, everyone finds it easier to create timesheets and the system is used\t<\/p><\/div>
Read the interview with Advance<\/a> \tand find out why it chose Twproject for its IT projects\t![](\"https:\/\/twproject.com\/blog\/wp-content\/uploads\/2023\/06\/quote-arrow.png\")
<\/a><\/div> <\/div>\n\n\n\n<\/p>\n\n\n\n
In addition to what we have seen so far, Twproject <\/strong>has many other functionalities that can simplify the workflow within an IT team.<\/p>\n\n\n\nFrom the ability to manage staff, customers and suppliers<\/strong> on a single platform for more effective and immediate communication, to the combined waterfall and agile<\/a><\/strong> mode, and the very high flexibility and customisation of the system.<\/p>\n\n\n\n
In this article, we will focus on the main problems IT companies face daily in project management<\/strong> and look at some solutions to solve them.<\/p>\n\n\n\n Twproject<\/strong> is well acquainted with workflow issues in projects<\/a><\/strong>, both through feedback from its users and through internal experience of its team.<\/p>\n\n\n\n This is why we believe we can share some useful strategies for dealing with the<\/strong> main issues <\/strong>and the best tools to handle them.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n Before getting to know these tools, let’s start with the basics: how does the IT world approach process optimisation tools? How do IT project managers<\/strong> evaluate and choose tools?<\/p>\n\n\n\n This is a sector that is certainly open to new developments in technology<\/strong> and where the desire to optimise and speed up processes dominates.<\/p>\n\n\n\n Efficiency in project execution<\/strong> is certainly one of the most important goals in an IT company, and we will now see how it can be achieved.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n Let us now look at the specific challenges IT teams face every day, and at the same time see the main issues and tools that can help them change course<\/strong>.<\/p>\n\n\n\n IT departments highly value improved internal efficiency and corporate reputation, so we are confident that these strategies will prove useful.<\/p>\n\n\n\n It is always important to bear in mind that the whole team<\/strong> must be able to reap the benefits of using management tools. This will help to reduce the start-up<\/strong> phase <\/strong>and will immediately lead to an improvement in flows<\/strong>.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n The first effort that IT project managers make every day concerns delivery<\/strong> times <\/strong>that are not always easy to meet.<\/p>\n\n\n\n Time schedules planned at the beginning are often postponed due to a non-linear workflow<\/strong> that gets jammed easily.<\/p>\n\n\n\n The main cause that in our opinion risks slowing down workflows in IT teams is the coexistence of projects of different natures<\/strong>.<\/p>\n\n\n\n In IT companies, in fact, it is very common for staff to deal with various types of projects at the same time in their daily work.<\/p>\n\n\n\n The latter in particular can be a major cause of delays and <\/strong>bottlenecks<\/strong> <\/a>as they interrupt the regular workflow.<\/p>\n\n\n\n As a matter of fact, each of these activities is inherently different and should not be treated in the same way.<\/p>\n\n\n\n There are strategies and tools designed specifically to manage this difference in projects and which greatly help to plan work by calculating how much time each of these activities requires from the project team<\/strong>.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n The first problem caused by these different activities is that they affect the workload of the operators<\/strong> differently.<\/p>\n\n\n\n For example, in some cases these activities will accumulate over the next few days if not carried out promptly, and increase the daily work rate until the project deadline. In other cases they may be postponed, but it is always important to calculate their incidence in the team load.<\/p>\n\n\n\n Managing operator load is not an easy task and therefore it can be useful to use workload management software<\/a><\/strong> in projects that allows for detailed planning, taking into account the differences among projects, as seen so far.<\/p>\n\n\n\n Twproject<\/a><\/strong>, for example, allows each project to be assigned a different value from the three listed above and thus weight the workload<\/a><\/strong> of the operators, taking into account the fact that each project behaves differently depending on its type.<\/p>\n\n\n\n This helps to avoid overloading<\/strong> of team members and to optimise workflows in IT teams at an early stage of planning.<\/p>\n\n\n\n In fact, if we plan more carefully<\/strong>, taking into account this threefold task of team members, delivery times can be better met and the work as a whole will become smoother.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n In addition, another reason for segmenting the different types of projects is the better reporting accuracy<\/strong> we will achieve.<\/p>\n\n\n\n For a company with many projects underway, of different types and trends, work reporting and invoicing can be a daunting task.<\/p>\n\n\n\n A good solution may be to use a work planning system with integrated cost management<\/a><\/strong>, which automatically records the work done by the team, but at the same time allows all incidental expenses to be recorded.<\/p>\n\n\n\n Using a comprehensive platform such as Twproject<\/strong>, the data will be updated automatically<\/strong> and a comparative analysis between estimated and actual work can be carried out.<\/p>\n\n\n\n Unlike many other project management software, Twproject <\/strong>offers timely and accurate work tracking<\/strong>, allowing you to stay up-to-date on internal costs, resource work and margins, providing transparency internally and to the customer.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n Moving on to issues concerning project execution, we identified as a second problem the lack of focus on the sequencing of work phases<\/strong>.<\/p>\n\n\n\n As we have seen, a non-fluent work organisation can lead to the bottleneck phenomenon<\/strong>.<\/p>\n\n\n\n This is an annoying slippage in the time schedule for project execution. Causes of interruptions in the execution process on planned projects can be tickets to be processed, a technical urgency to be handled, and so on.<\/p>\n\n\n\n It is often difficult to pinpoint the exact point in the workflow where this blockage occurs<\/strong>; it may therefore make sense to equip oneself with tools that visually show the process steps and thus highlight the critical points.<\/p>\n\n\n\n The best example of these tools is the Gantt chart<\/a><\/strong>.<\/p>\n\n\n\n Once used as a simple initial planning schedule, today this tool has become much more dynamic <\/strong>and follows us for the entire project duration.<\/p>\n\n\n\n It is because of this interactivity that the Gantt diagram is now a recommended tool for all project teams, even the most agile<\/a><\/strong> ones such as IT teams.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n A good Gantt chart<\/strong> allows us to link the different project phases together and set up their different types of dependencies<\/a><\/strong>.<\/p>\n\n\n\n First of all, we have to list the project activities and set up our WBS <\/strong>(Work Breakdown Structure<\/strong>), which as the name implies divides the project into hierarchically ordered work blocks.<\/p>\n\n\n\n Subsequently, our WBS can be visualised as a Gantt chart that will allow us to easily link activities together.<\/p>\n\n\n\n The more accurate and realistic the correlation between the phases and sub-phases<\/strong>, the more we will be able to identify problems causing delays, blockages or overruns.<\/p>\n\n\n\n If we use project management software such as Twproject<\/strong>, the Gantt chart can be created in just a few minutes: thanks to it, it is easy to realise how the work is organised and to easily assign tasks to the various assignees.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n When the work starts and it is therefore necessary to monitor and analyse workflows, the Gantt chart is particularly well suited to perform this analysis.<\/p>\n\n\n\n With Twproject, you can use the Project Timeline<\/a><\/strong>, a tool within the Gantt as well as on the statistics page, which allows you to easily identify the causes of project delays.<\/p>\n\n\n\n The Timeline represents the historical memory of the project, which records everything that was initially planned in the start-up phase<\/strong>.<\/p>\n\n\n\n Subsequently, the Timeline keeps track of all project variances<\/a><\/strong> automatically, without the project manager having to explicitly note them down.<\/p>\n\n\n\n If, for example, a delivery date is changed, this shift will be recorded in the timeline and at the end of the project it will be possible to review the exact moment when the timeline changed.<\/p>\n\n\n\n <\/p>\n\n\n\n In the IT world, it is very easy for this to happen, especially due to the coexistence of several ongoing projects, as we have seen.<\/p>\n\n\n\n Knowing the causes of delays is very useful to plan more accurately in the future and helps to avoid the notorious bottlenecks<\/strong> we often run into if not wisely managed.<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n So, after having carefully calculated the workload of operators and planned the work steps accurately, let’s finally see what is the last step to improve workflows in the execution phase<\/strong>.<\/p>\n\n\n\n One of the most difficult tasks during this phase is the optimisation in the distribution of deliveries and tasks<\/strong>, which if not done effectively can negatively affect the productivity of the team.<\/p>\n\n\n\n Often when embarking on a new project, the amount of information that needs to be communicated to the project team may seem overwhelming.<\/p>\n\n\n\n But if you break down all activities into small, precise<\/strong> tasks<\/strong><\/a>, not only do you communicate effectively with the team, but you get a clearer picture for the whole team.<\/p>\n\n\n\n IT teams usually like agile ways of managin workflows<\/strong>, and in this Twproject has several solutions that are highly appreciated by them.<\/p>\n\n\n\n Its ToDo’s<\/a> are very flexible<\/strong> because they can contain a lot of information such as assignee, tag, type, attachments, etc.<\/p>\n\n\n\n <\/p>\n\n\n\n We can add comments to them, mentioning the recipient. We can filter them in multiple ways and organise them by priority. In short, they have everything that can be useful to an agile team that needs an efficient and fast communication tool.<\/p>\n\n\n\n They can also be managed via the Twproject Kanban visual board<\/a><\/strong>, which contains some special functions such as the column sorting method. Not only priority, but also sorting by project, by assignee, by status and type.<\/p>\n\n\n\n ToDo’s are functional for any type of work<\/strong>, be it related to classic projects, maintenance or ticketing.<\/a><\/p>\n\n\n\n <\/a><\/p>\n\n\n\n To sum up, we know that IT companies are those most attentive to new technological developments and those most inclined to adopt software tools<\/a><\/strong> to improve internal processes<\/strong>.<\/p>\n\n\n\n However, it is just as likely that IT companies will decide to make handmade systems, being software producers themselves.<\/p>\n\n\n\n But as we know today there is an increasing segmentation in the software industry<\/a><\/strong> and therefore the choice to internalise the development of business management systems<\/strong> is not always successful and can divert attention away from more profitable projects.<\/p>\n\n\n\n That is why it is best to turn to those who have decades of experience in the field and know how to anticipate and solve the needs of IT companies in project management<\/strong>.<\/p>\n\n\n\n Our customers working in the IT sector have no doubt: Twproject <\/a>has everything they need<\/strong> to simplify IT project management.<\/p>\n\n\n\n <\/p> \tWith Twproject, projects run more smoothly, everyone finds it easier to create timesheets and the system is used\t<\/p><\/div> <\/p>\n\n\n\n In addition to what we have seen so far, Twproject <\/strong>has many other functionalities that can simplify the workflow within an IT team.<\/p>\n\n\n\n From the ability to manage staff, customers and suppliers<\/strong> on a single platform for more effective and immediate communication, to the combined waterfall and agile<\/a><\/strong> mode, and the very high flexibility and customisation of the system.<\/p>\n\n\n\nForeword: the most relevant requirements for the IT sector<\/h2>\n\n\n\n
The different instances of workflow management in IT teams<\/h2>\n\n\n\n
<\/figure>\n\n\n\n1. Co-existence of projects with different course and type<\/h2>\n\n\n\n
<\/li>
<\/li>1.1. Operator load calculation<\/h3>\n\n\n\n
<\/figure>\n\n\n\n1.2. Integration with cost management<\/h3>\n\n\n\n
2. Managing workflows and bottlenecks<\/h2>\n\n\n\n
2.1. Dependencies<\/h3>\n\n\n\n
2.2. The timeline<\/h3>\n\n\n\n
<\/figure>\n\n\n\nAgility in workflow management thanks to ToDo’s<\/h2>\n\n\n\n
<\/figure>\n\n\n\nTwproject: the ideal tool for optimising workflows in IT teams<\/h2>\n\n\n\n
<\/a><\/div> <\/div>\n\n\n\n