The Most Effective Strategy to Estimate Projects

Estimate projects correctly is a difficult task that every project manager has to face. It doesn’t matter if you estimate in order to evaluate resource work load (time/effort estimation) or just to create customers’ offer (cost estimation), the problem is just the same.

How can I predict exceptions, delay, bottle necks and create an estimate that is as close to reality as possible?

The answer is quite simple, you can, if you count on your team.

Identify the problem:

Estimate projects is difficult, in particular when you came to big ones that last months, maybe years. In these specific cases estimation could be just a guess. An incorrect estimation can generate several problems, for your team and your company in general:

  • Underestimated projects: this is what happens the most, particularly when project managers have direct contact with customers, if you want read more about why underestimation is so common you should read this article.
    Robert works for a small company where he is a project manager and also the commercial director. He knows that his team is doing its best but he doesn’t want to lose any new customers opportunity. For this reason he underestimates his projects, trying to convince the team that every new customer can make the difference for a small company like theirs. Doing this, the quality of the product decreases, the team is overloaded and the project manager completely loses the correct perception of the project cost. Robert knows that his company will suffer of high turn over.
  • Overestimated projects: Project managers more connected with the team tend instead to a pessimistic estimation of the project.
    John is a project manager and lead architect of a young software house. Every time a new projects begin he speaks to his team to make the correct estimation of tasks. Being near to his colleagues he knows how many problem they face and he prefers to overestimate his projects. Resources look over planned and the commercial department can lose opportunities for this lack of communication. At the end of the year John knows that his team could have released more products with a correct estimation.

Being a project manager with estimating problem you have probably found yourself in one of the two described above, maybe with different circumstances but probably with the same outcome.

Of course a correct project estimation can fix all these problems, correct schedulingresources’ workload. So, how can we improve it?

Find the solution:

Being a project manager, maybe a senior one, your management skills are probably very refined, you know the effort for managing a team conflict, you probably know how to calculate the revenue of your task, but what about developing that specific product requirements? The project manager is able to identify all the phases of the project structure, but who better knows how does it take to accomplish a specific phase than the resource working on it?

The key for a correct project estimation is in your team knowledge.

Nicole is a project manager at ACME spa. She works with a smart and diversified team. Every time she is assigned to a new project and she has to estimate it she organizes a meeting with her team to develop the Gantt of the projects. Nicole sets the milestones if she has some and tries to define the end date of the project. She identifies the best resources for the work and then she asks them a refined schedule and estimation of their small portion of work. No one knows better than Giulia how effort it takes to make a perfect email layout. Nicole asks also to her colleague which problems she encounters the most and with which delay. Nicole asks to her team members to become everyone the project manager of his own specific tasks.

The knowledge of the team is very precise and very close to every specific matter, they know most of the possible exceptions, every possible delay, every bottle neck on their specific phase. To have a complete and precise estimation you have to go deeper with your team and analyze with them all the phases, let them estimate their phases like they would be the project managers, delegate. This approach will help you improve your resource management in general.

Also, if you work on projects that can repeat in time you could ask your team to specify every step of the work with its effort.

This to-do lists could be used as a template in time, to avoid loosing time estimating the same things again and again.

Save your team knowledge is the key to estimate projects correctly. It is what you can use to make comparison and learn in time estimating even better.

Conclusion

Using this strategy you could be able to have a better idea of the effort of the project and every possible exception that can occur.

  • Identify your project phases and your goal end date
  • Identify your milestones and discuss them with your team
  • Select the best resources for each phase and delegate the task to them
  • Let the team write down every step of their phase to estimate it.
  • Use the knowledge from the team on every phases to estimate the entire project from bottom up

Using this strategy with a project management software that can help you creating a Gantt chart, assigning your resources, checking their workload could really make the difference, estimate projects will become easier.

If you want to learn more about how to introduce a project management software in you company you can read our article.

Start now estimating your projects correctly

Scrum With Twproject for SEO & Digital Marketing

I recently read a very interesting post about how to use Scrum methodology in a SEO & Digital Marketing Team. The post has been written by Marcus Miller (@marcusbowlerhat) and you can read it here:

Using agile project management for SEO & digital marketing

This post gives me the idea to write a new one explaining how to use Twproject with Agile methodologies and, following the Miller’s post, how a SEO & Digital Marketing Team can use it.

Scrum: What is it and why with Twproject?

How it is well explained in the post, the Scrum methodology is a project management approach helping small teams, and in particular software development ones, releasing products in an incremental and iterative development.

This approach defines a flexible and cohesive environment where a team can develop a product as a unit, self-organized, with common goals.

A Scrum team usually consists of several people, with specific roles, that, starting from a project with a well defined list of features (“the backlog”) , works together in short time cycles, on prioritized  sub-sets of features (“sprints”).

Team communication is encouraged with daily scrum meetings and a retrospective meeting at the end of each sprint.

Even if Twproject works fine, both with Waterfall and Agile methodologies, the second approach meets perfectly the idea behind our software.

Encouraging team communication, self organization and a more practical approach to what needs to be done, saving time and energy, are just some of the key ideas of Twproject.

Scrum Roles

Product Owner, Scrum Master and Team member, these are the specific scrum roles that you find already loaded in Twproject, and this will be the only roles required for managing your Scrum project, I refer to the post at the top for roles definition and usage.

You can activate these roles from the Twproject admin page ->  New area creation wizard -> Create an area with SCRUM specific roles.

ScreenShot068

 

Once the scrum area has been activated, in the project section, you will find a new “create scrum” button.

Thanks to this functionality you will create your scrum project in minutes, just selecting your team members, the system will create the project assigning the correct resources with the chosen roles.

Agile tools

Once the project is created and all your team is assigned with the correct role you have to insert the backlog. This can be done easily with Twproject using issues.

An issue in Twproject is a task activity, a to-do, a ticket, a backlog item, something that needs to be done in a specific task.

Twproject backlog issues can be prioritized, ordered, and have customizable status (open, in test, working, closed, is up to you), a time estimation and a due date.

ScreenShot070

 

Managing your backlog with Twproject is very practical thanks to the Kanban tool that lets you visualize your items by priority, by status, assignee and so on. Thanks to the Kanban you can see the status of the work, what is assigned to who, checking with a click all the progress your team is making.

ScreenShot072

Once the backlog is created you can create your first sprint.

The sprint creation includes also the set up of an agenda event for all the team members for the stand up meeting.

At this step you will also select the backlog items that you want to move to the new sprint:

ScreenShot071

Once your sprint is created is time to work. The team members will see in their dashboard all their items with priorities. Team members can communicate with a dedicated forum, working together to get things done.

At the end of the sprint, you can create a new agenda event, starting from the project work group to analyze what has been done, what you can improve, and how to go further.

This procedure will be repeated until you finish all the backlog and your project is closed.

Twproject includes also a set of reports that you can use to control your product developments, one of them is the burn down graph, a specific chart showing how the team is performing.

Conclusion

As Marcus Miller pointed out in his post “No matter how efficient we become, the work still has to be done”: no matter how a software can help you managing the project, you still have to do the job, that’s true, but we really hope that our tool can make your life easier.

I think that one of the best features of the Scrum methodology is that it is meant to be improved on the go, you do not actually need to be a master to start organizing your work, you can refine from sprint to sprint.

Using Twproject you can start immediately and without effort using this methodology and test if it works for your company too.

I suggest you to read the post of Marcus Miller that explains in a very intuitive way how this methodology works and how to introduce it in your team.

Using agile project management for SEO & digital marketing

The post is focused also on how to use this methodology in a SEO and digital marketing company, but, as you can imagine this approach can be used in every fields, try it out and contact us if you have questions!

Try Twproject now for managing your SCRUM projects

How to Introduce Project Management Software & Succeed

One of the biggest challenges, a project manager can face in a new team, is to change things for the better and let this changes take effect without the resistance of the team.

One of the most frequent examples is when a project manager decides to introduce a new tool for project management.

This moment of change, even if it is felt like very stressful,  is actually a great opportunity for a company to improve its strategy and organizations.

So,  what if you are that project manager? What if you really want to change things in your company organization with a new project management software?

Fix your expectations:

One of the most important things you need to do, before introducing a new software, is identifying your goals. You have to answer these 2 questions:

  1. Which are the main reasons that bring me to search for a project management tool?
  2. Which are the key features of the tool I chose?

these very simple questions can let you analyze what you are missing in your team now and which are the milestones you want to achieve in the future. Here are some examples:

“I really need to let everyone see what they are working on, stop wasting time with e-mails, pointing out problems and delay. The software I’ve chosen has great dashboards with the list of active assignments by priority.”

“I started searching for a project management software because we really do not know how much our projects cost. We wanted to track time and extract reports with resources costs. We chose the software that lets us manage resource costs easily, together with a time tracking tool”

Once you have your goals in mind be realistic and set some small achievements for your near future. Having realistic expectations is very important, actually it is a key point, if you expect to achieve unrealistic goals  you will immediately face a sense of fail in your team, and this will bring the software to fail.

At the same time, if you do not communicate your expectations, no one will understand how much  helpful will be this change and they will abandon the software.

No one said it was easy….

stereotype metapher leadership or exclusion

stereotype metaphor leadership or exclusion

Team communications, change is for the better..

The other key point about introducing a new software in a company, is to let everyone know, that this will actually help everyone working better, not just the project manager.

This, in some cases, is very difficult.

If you are the project manager of a cohesive team, maybe this will not affect you, but now I’m talking to all those pm, having a big team to manage, maybe a distributed one, with several people working in different ways. So, how to let them feel that changes are for the better?

It is not a software to control who is working and who is not. It seems a bad thing to say, but most of the time, these kind of software are felt like tools to control. They are not and you have to tell them clearly. It doesn’t matter if in the future you will get amazing reports of all worked hours, or if, thanks to the software, you will be able to see who is overloaded. The reason for changing is not to control, or at least it shouldn’t be ;-).

Be your own pm and organize your work better. Once the project manager has created the structure of the task, with dependencies and time frames all the team will be able to check their priorities, organize their to dos and manage their work in autonomy. If you, as pm, are able to let them understand the utility of this new responsibility you will have them on board.

These are just two examples of what you can point out to your team to let them know how helpful can be a project management software, let them know that is a tool for the whole team.

Get the best from the software

Following this easy yet effective strategy to introduce the new software in your company you will get in time amazing results. If your team will use the software, inserting and updating data with no effort, you will get something like:

Inserting estimation and worklog -> team workload and cost tracking

When the software is well introduced you will start inserting projects charts, assigning your resources with estimation and hourly costs. Thanks to this, and having your team inserting worklog you will be able to see your resources workload, control tasks progress and check costs, all data updated in real time.

Managing teams and agenda -> meeting and documents sharing

If you start using a shared agenda, you will be able to share appointments and create meeting easily according to task work-groups. check unavailability and the same connection will be created to easily share documents.

Read more here about managing distributed team agendas.

Using task checklist -> self management and responsibility

When a pm software is introduced, it can give you also the possibility to track to-do lists connected to projects. This is a very useful way for all users to organize, prioritize their work, finally they will stop using notes on the desk and no ideas or messages will be lost.

If you feel that your team needs a more structured way to work, it is probably time to introduce a project management software. Yes, it will be a big change but you can really get results if you follow our strategy. Our software, Twproject, can really give all the results mentioned above, all those features in one software only.

Introduce your team to Twproject.

One try is worth a million words.

How To Manage Distributed Teams – Sharing is Caring

These days, companies has to face an ever growing need for dynamic teams, shared groups of people working together through the internet. This need increases hand by hand with the difficulty of managing team dynamics and project updates.

For this reason, using conventional software like Microsoft project, built for managing projects in their best case scenario with clearly identified teams, could not fit the needs.

Many Projects – Lots of Teams

Big companies, and small ones too, with a high number of projects can see their number of teams increase accordingly, and when I say team I mean people that are actually working on the project.  Even if your company has just seven colleagues like ours, and you have one team working on several different projects,  you can face the same problem: a meeting for a project, a meting for another, uncounted e-mails refer to a projects, many refer to another, what a mess!

For this reason we cannot underestimate this trend and we better try to manage it.

Sharing is Caring

Actively work on a project often involves sending  tons of e-mail to keep everyone updated on what is going on, share documents and information about progress and commitment, schedule meeting with customers and colleagues, share the list of to-dos to get the project done.

This continuous flow of information assumes that you have always in mind all those who compose a specific team. How many of you spend more than a minute checking the list of attendees to be sure that everyone has been added? What if someone is forgotten?

Distributed Teams – Somebody Help!

It’s clear now that we need something helping us managing distributed teams. But what if I told you that the solution is at one step distance? Dynamic teams are implicitly defined by your projects. No one knows better, who is involved, than project management software.

people-envolved-2

Node by node, different people could be assigned and different information could be shared. Simply looking at the team from the project’s point of view, you will see the work-group changing.

This simple yet effective idea, let you start from the point of view of your project: when you have an information to share you just need to focus on which is the specific project related, your team is already there!

Just open you projects management software, your changing teams are saved there!

If you have not introduced a project management software in your company you can try Twproject that solves this problem with a suite of functionalities that starts exactly by the work group created on a project.

Finally we will have the distributed teams problem solved and nobody will be forgotten.

If you want to read more about how to introduce a project management software and succeed you can read this post:

https://twproject.com/blog/how-a-project-manager-can-introduce-a-significant-change-and-actually-succeed/

We have the tools, we have the culture.

5 Secrets to Improve Your Meeting

Work meetings can be stressful and often perceived as a waste of time for your whole team. Finding the best moment, coming with a clear idea of the meeting purpose, taking important decisions, define a project’ plan and all designated resources: all these points can decide if your meeting will be a complete failure or a success.

If you are about to schedule one with your team, you’d better pay attention to these 5 secrets to improve your meeting in order to get a happy and effective talk.

Use a project management software with shared agendas Finding the best moment to schedule a meeting is very important. It could be obvious, but it is not just a matter of finding a day when the team is available, it’s about finding a day when none of your colleagues have important deadlines, scheduled appointments or high priority tasks to close. Having a software that lets you check all of these will help you having a focused team.

Before the meeting create an ideas board If you have to manage with important matter, it will be really helpful having an idea of your colleagues’ thoughts before the meeting. You can use this to understand which of your colleagues share your ideas. An ideas board is also very helpful in order to give to all your team the possibility to share their opinion, even to those not so familiar with meetings’ animated discussions.

Listen to all points of view and understand them Having an open mind is really helpful during meetings. You have to be open also to those that will probably tell you that your ideas are not so brilliant, remember that your goal is to finish the meeting with taken decisions and a plan of what to do next.

Use a draft manager software Write down everything said. The draft management is very important to remember all decisions that have been taken and all discussions leading to them. With a draft in your hand you will be able to easily detect which are the key points for your team and why.

Transform decisions to a real plan Once everything is decided you will need to define a project plan, so use some time of your meeting for a recap, read the draft in details and create a to do list, you can use a project management software for this purpose too, assign these to-dos to your team and schedule deadlines.

Effective meeting are difficult to achieve, generally because you are taking away resources from their “real” projects. Organizing it properly, involving all team members in the decision process and transforming discussions in thing to do will incredibly improve your team culture.

Try Twproject to manage your meeting.

One try is worth a million words.

We need to talk: collaboration trends and mistakes to avoid

Companies becoming “liquid”, teams spread over thousands kilometers: workspace has changed, it is wider and faster. This is the reason why you need the right collaboration tools to… make the work work!

Collaboration tools: what is happening right now

It has already happened and it is happening.

Despite being a big, medium or small company, the concepts of colleague, team, meeting are now different.

And, despite being a big, medium or small company, one of the most important trend – and need – is about being everyone on the same page, at the same time.

And, believe it or not, this trend has something ancient within.

Ockham’s razor in today collaboration

William of Ockham was a Middle Ages (c. 1287–1347) Franciscan monk, a philosopher and theologian.

He is still famous for his Ockham’s razor, a principle which reads:

Among competing hypotheses, the one with the fewest assumptions should be selected.

The original use of the principle was in theology, but it is a heuristic technique as well, and it definitely is a principle which should be applied to your collaboration environment.

To have your whole team on the same page, at the same time you need a cloud and a real time communication tool. The cloud allows you to have the whole team working almost literally in the same (yet virtual) place.

A real time communication tool is what you need to break space and time barriers between the team members: it is the way to have everyone knowing everything is needed when it is needed.

So far so good, isn’t it? And everything seems so easy and smooth. But you still have to avoid the dark side of cloud and real time communication: the lack of management of the workflow and communication flow.

This is the reason why cloud and communication tools need a project management tool: a “meta level” of organization, another – wider – virtual place which ties the tools together. And what do you need from your project management tool? To track changes: you need to trace everything that has been done and still needs to be made. A great project management tool has to show you the path to follow helping you getting your projects done.

Murphy’s Law VS Remote Collaboration

Anything that can go wrong, will go wrong. Even when you work remotely. No fear: this post is about how to save the day!

Anything that can go wrong, will go wrong: these are supposed to be the words of Edward Aloysius Murphy Junior (1918 – 1990), words that became an ante – litteram meme and the inspiration for a huge amounts of variants in almost every fields of human activities.

Nevertheless sometimes bad things (we are not going to use the s. word in this post…) happen. And yes: it seems that “bad things” happen always in the worst possible moment.

IT stuff, computers, the internet can’t avoid Murphy’s law, and the collection of Murphy’s Computers Laws is a lot of fun. Well: it is not, actually, while it happens.

If you are involved in remote collaboration, if your teammates are peppered across the world, your Achilles heel is, of course, the internet connection.

And, according to the Murphy’s law view of the world, probably you are going to experience a problem when a deadline is close, or when there is something very urgent to do.

First things first: no panic.

It is very likely that the problem you are experiencing is local, or maybe only your service provider is involved. Then try to contact the service provider’s customer care. You will know immediately If it is really that bad, because it won’t answer…

You must not waste your time, so just pick up your smartphone, tablet and laptop and… Run! What for?

To find a wi-fi connection of course. Because, it is the only thing you really need.

Good remote collaboration tools such as Twproject don’t even need a computer: you can check the workstream just via the smartphone app, and a tablet is more than enough to do everything else, to interact with the team just like nothing had happened. So, just look for libraries or coffeehouses – in some cities even public transports have a good wifi connection, in that case: jump on a bus! – and everything will be OK.

From an Italian point of view, one for which coffee, il caffè, is quite an important thing, you could tell that some coffeehouse companies actually sell wifi connection, because that is not real coffee… 😉

So just give Twproject a try!

Work environment and Papuasian tribes: how to solve team conflicts

You can think of open space offices and flame mails, but team conflicts are a little bit older than that: Cain and Abel, you know..? Since that time we learned the lesson: conflicts can destroy a team.

At the present time the concept of team is reshaping itself: open space offices are not for everybody (and, if they are not your cup of tea, they can also affect your performance: good insight about this issue in Quiet: The Power of Introverts in a World That Can’t Stop Talking by Susan Cain); tons of emails are not for everybody; almost – digital – only relationships (I am currently working also for people that I have never met in person, did it never happen to you too yet?) are not for everybody as well.

Nevertheless we are still speaking of teams, and a team is supposed to be a group of players forming one side in a competitive game or sport. And business is the most competitive sport on this planet. If you don’t find a way to make out a team from a bunch of people, you are going to lose the match.

 

A team is a system of relationships and different personal needs.

Without a way to bring together that relationships and needs, the system fall apart: it is the concept of Schismogenesis, ”the generation of opposition” a concept developed by the anthropologist Gregory Bateson in the 1930s while studying the Papua New Guinea Iatmul culture.

Your team and an Iatmul village are a system. There are two different ways to destroy it: the Complementary schismogenesis (dominant-submissive behavioural pattern) and Symmetrical schismogenesis (same behavioural pattern, as in the arms race).

In the passage rite named Naven, Iatmul people create a context in which the usual roles are “played” in the opposite way: male becomes (disguising) female. The key of the Naven rite is to allow men and women to experience – in the context – the emotional lives of each other, achieving a psychological integration.

Finding a way to bring this kind of experience to your team is a good way to keep it not alive, but lively! Programmers and creative designers (but it can be sales and buyers, or sales and logistics, HR and administration…): these are probably the men and women of your “village”.

All of us are under pressure. But finding an opportunity to experience a different pressure, the pressure that “the other guys” are experiencing, is a great way to improve the team manager: we have the tools, we have the culture, we just have to build up the opportunities. Because a lot of what makes the difference between success and failure in teams is a matter of empathy.

Think about it next time you are going to share a pizza with a guy of a different department… Meanwhile, a tool that helps team – working is a good way to keep low the schismogetetic fibrillation level…

tour-operator-load

 

Easing work relationships on a project-by-project basis

Twproject is a project management tool, and as such it represents work relationships in form of projects, assignments and roles.

But what it can do better with respect to classical hierarchical and role based modeling is that organizations can be projects – related: the same user can be project manager, worker, stakeholder and tester at the same time on different projects. You can get suggestions in a project you lead, and make suggestions in a project you follow.

And indeed you can set up projects where the manager / execution roles are exactly specular, so that users can compare the two experiences. It is not by chance that Twproject is used as a didactical tool in so many universities.

User and projects can spawn different areas, and you can involve resources from other departments in cross area projects: just in the “Naven” ritual, it’s a matter of point of view!

This contextual role playing can be a way to experiment and understand problems relative to your position in a project in different cases, just like in the rites above.

 

We have the tools, we have the culture.

Teamwork 4.5 released: a major free upgrade

We are really happy to announce this major release update. As you may guess from the length of this announcement, this update will improve your Teamwork in almost every section, providing more modeling tools and functions. The web browsers’ enhanced capacities (in particular those of Firefox, Safari and Chrome) are used in depth to give users a better experience.

This is a free upgrade for all users of version 4. Get the installer / upgrader here: http://www.twproject.com/download.page

The main features of this release are:

– Issue managing by dragging – “kanban” like.

– History of issue assignee, status and task change (better help desk and issue scaling support).

– Customizable issue statuses.

– Better graph and agile / scrum handling.

– Cross links between tasks / issues / resources / agenda events / meetings / boards.

– In-place popup editors.

– Operator load computation has become much smarter.

– Greatly extended user guide with real case work “mappings” to Teamwork, and a new section on performance optimization.

Layout changes

Several pages that up to now were popup windows are now windows in place, which improves their usability: issue editor, custom forms, workgroup selector.

Several text areas now support internal links (e.g. T#MYCODE#), web links (http://www.twproject.com), smiley’s, absolute URLs to images.

New features

Issues.

Issue statuses – customizable. New issues statuses can be created. There is a page for managing issue statuses (which before version 4.5 were fixed):

clip_image002

And for every status not only its color, but most importantly its business logic behavior is determined from this editor:

clip_image004

Whether it should “behave” when asking user feedback as an open status, as close, whether it should ask for comments and / worklog when entering a status.

So typically if your status is something in which the issue enters at “end of life”, it should be marked “as close” and “ask for worklog” too should be enabled.

clip_image006

Issue change history. When changing a status, task or assignee on an issue, the editor will ask for a reason, and the change will be recorded on the issue. And in fact there is an additional tab on the issue editor, “history”.

Issue organizer “Kanban”. Issues can be now be organized in a completely visual way by dragging and dropping them: filter the issues in which you are interested in, and then select the “organizer” button.

clip_image008

clip_image010 Now you can also enable use of external codes on issues (admin -> default for projects).

Dashboards.

The usability of the “customize this page” function has been improved: all portlets are always visible:

clip_image012

And it’s easier to drag them in the dashboard. Moreover it is easier to access the general page / portlet disposition page: just click “all users”. clip_image014

There is a new additional starting page: help desk support.

Operator load and planning. This was the user request:

“refine the operator load showing the effective load taking in consideration worklog done. E.g: 100h estimated on 20 days, done 10h in 10 days the resting 10 day must have a load of 90h not 50h like now”

Also take care of unavailability.

Use the new operator load on plan, load by day, end wherever it is meaningful

Operator load textual: put worklog with totals and pink holydays. Use striped background

Advanced users

– The examples in the distribution and the documentation now cover also “custom wizards”: see section 14.4 Custom wizards of the user guide.

Minor improvements

– More kinds of documents are now full-text indexed; these are the extensions now supported:

“.txt”, “.rtf”, ”.log” “.pdf”. “.htm”, “.html”, “.zip”, “.war”, “.jar”, “.xls”, “.xlsx”, “.xltx”, “.xlsEmb”, “.doc”, “.docx”, “.dotx”, “.docEmb”, “.ppt”, “.pptx”, “mpp”, “mpx”, “.msg”, “.msgEmb”, “.vsd”, “.pub”.

Also custom fields are full-text indexed.

Here are several user requests fulfilled:

– “Add worklog approval monthly screen” -> We will add bulk status change in worklog search / analysis

– Expose issue id in editor and list.

– LDAP authentication cascades to system one.

– Develop a resource snapshot.

– Sort File Storage Document Listing.

– Make “add document content” in a rich text editor.

– Please put a link to a task on the agenda event : we actually did much more by having full internal links.

– Need to add subscription event for when a new version of a document is uploaded.

– Display agenda items in planByResource like in worklogWeek.

– Search for specific custom fields.

– You can have a customized help message in the “help” page, just add in the labels CUSTOMIZED_HELP_CONTACT.

clip_image016

– Notes on issues are on the main tab and self-resize.

– Issue assignee selector got simplified.

– Now you can create subtasks as sub-fluxes.

– Counters can now be reset and deleted.

– When changing a task on an issue, notify the new assignees.

– Since version 4.5 custom fields support also “typing” of data. E.g. “cost,20,java.lang.Double” will add a custom field of length 20 and type “double” (a floating point number).

– Holiday settings: now you have year-specific settings.

– In issue list you can now filter by task type.

– Resource print includes my assignments.

Bug fixes

– Check why in the assignment notification we add a link to the task even if the resource has not the rights to read task … .

– Meetings are not full-indexed.

– Index custom forms data.

– Create issue from task editor menu does not launch creation nor filters???

– Issue multi edit: bulk change gravity do not close actions clicking “close”.

– Fixed MIME for teamworkMenuPlusCss.jsp,

– Issue cloning did not raise events,

– Fixed various combo positions in bulk update screens in case of scroll.

– Summa is not saved on document link and file storage on tasks and resources.

– A fix for Oracle on Resources with no surname.

– An operator may change his own password even if cookies are enabled.

– Do not notify disabled users.

 

Technical points

– In order to optimize memory usage,

clip_image020

If you log as administrator and go to the label management section, open the “label rules” container (it is closed by default), and say if you want to have only English as language, type EN in the enabled languages field and select SAVE.

clip_image022

– Teamwork 4.5 is no more on quirks mode – we dropped support for Internet Explorer 6 – and pages are in HTML 5

Important for upgrades. Several JARS have been updated, added and removed. If they are present these JARs should be deleted by hand from WEB-INF/lib:

o commons-collections-2.1.1.jar

o commons-logging-1.0.4.jar

o poi-3.0.1-FINAL-20070705.jar

o jcaptcha-all-1.0-RC3.jar

– Added -server configuration to the Java JVM distributed.

– If using HsqlDB you can make a dump of the current log by hand from system check instead of having to wait Teamwork restart:

clip_image024

Notes for updating to 4.5:

Any custom filter on issues will need to be redone as the issue statuses are a lookup field.

Unfortunately all document list attached to discussion points of meetings will be reset.

P.S. We’re building the beta of a new online service – called Licorize – a cocktail of Delicious bookmarking and light to-do management. If you’d like to beta-test it,  just send an e-mail to info@twproject.com with “Licorize” in the subject or body – we will soon give you access and also a year of free usage to your entire group.