So we are releasing TP 2.3 tomorrow. It was quite hard release for several reasons (we even increased release duration from 5 weeks to 6):

• We’ve started Selenium tests creation and it took time. Sure it will save a lot of time in future, but for this release it was additional burden since we created regression tests for old functionality as well as implemented some automation.
• Performance improvements took a lot of time. We’ve removed Ayende generics (major changes in overall architecture) and dramatically decrease CPU usage on server, so scalability improved greatly and TP can work with 100+ concurrent users without problems. I am really happy that we are using code generation, without it such changes in business layer should take several weeks instead several days.
• Many old bugs have been fixed.

If you take into consideration that new functionality still appeared (Web Services API and People Allocation Management) you will understand why the release was not easy. It is quite large achievement for us and TargetProcess becomes more and more enterprise-ready.

Two major additions in TP 2.3 are Web Services API and People Allocation Management. Both features are must have in any serious project management solution. Integration is a key for many companies and now public API enables almost any required integration. API is powerful and you may even create custom queries based on HQL syntax.

Effective people management in large departments is hard without good tool support. The common practice is to use Excel to control load and people availability. You understand that it is hard to maintain the document in actual state. The typical process is:

1. Ask all PMs about
   1. Who will be free and when
   2. Are there any staffing problem and who they need for the project?
2. Put the data from PMs to the spreadsheet(s).

Top manager usually does not have much time for manual updates and for large department it may take up to 2-3 hours to have complete actual data each week. TargetProcess eliminates this burden. The process is simple:

1. Each PM specify allocation for each person in the team as well as allocation end date
2. Each PM submit allocation requests if he needs more people
3. Top Managers just clicks Allocations link and see all the data on one screen. He may filter data, sort data, see details if required and resolve conflicts right there. Then he may click Allocation Requests link and see all requests for people (prioritized and commented).

So the only mandatory thing for PMs is to set correct allocation % and allocation end date for each team member. Not a hard task that will take just a few minutes.

In general TargetProcess became faster, more scalable, more powerful and open for integration in last release. Hope you will enjoy the results!

We've implemented people allocation. Below some screenshots.

People load at a glance

People load details

Assigned bugs, tasks, stories.

Below is a mock ups of Allocations area in TP 2.3. Any comments appreciated!

People requests management provides answer on quite tough question: "What projects need more people?". Together with Allocations area TargetProcess will provide information for some important decisions: "Could we re-allocate someone from another less important project?", "Should we hire more people?"

Today we had initial discussion about People Management area in TP 2.3 (March). Here are some initial results.

It will be possible to see allocations on all projects by person as well as set allocation end date. Total workload will be visible as well. The view below will answer very important question: who will be available for specific date? For example, new project will be started 10-Apr and it will be possible to see persons who will be free or partially free starting from 10-Apr (or earlier).

Also there may be brief allocation report that will show minimum information: projects/iterations by person, assigned effort, allocation end date and major release milestones (this report is not approved yet, so if you have comments or suggestions please go ahead).