v.2.24: Global search, prioritize restrictions, network diagram

New tp3 features appeared in v.2.24 release. Some accounts are already upgraded, On-Site customers will have an access to the download in 2-3 days.

Global Search

We spent a lot of time creating and really fast search. This new global search usually returns results in a second.

Prioritize Restrictions

Many people complain that it is too easy to change priorities on boards. Indeed, it is true. We've implemented a setting that makes it harder:

Now you can completely disable prioritization or demand a special gesture (pressed Shift key and mouse cursor) to change priority. It will make boards safer and Product Owner will sleep well.

Network Diagram

Relation network diagram shows all dependencies for selected stories, bugs, features and other entities. 

Click Reports tab and find this new report here:

You can filter entities easily to focus on interesting data.

Quick Add in Views

Minor improvement that helps you to add things faster from Views:

Other Improvements

• It is possible to add up to 60 custom fields for every entity in every process now
• REST API gives you an access to state changes history
• Performance improvements
• Better confirmation messages

Quick Add from File via Drag and Drop Mashup

Here is the new mashup that does cool things :)

Better Multi-Teams Support Concept

TargetProcess3 has quite powerful multi-teams concept, but early beta release revealed some limitations. The main limitation is that you can't track functional sub-teams in a single project. That may sound like a waterfallish approach, but it is not in fact. There are many viable cases when this is useful (separate UX phase, separate deployment phase, etc.)

Another case is when several teams with different processes work on a single project. Imagine large projects with two development teams: Scrum and Kanban. Work split between these two teams, but we want to easily track progress on a project level.

The proposed solution will enable both cases above, but with a price of the system complication. 

User Story (Bug, Feature, Task, etc) will have two states: Team State and Project State. Team State and Project State will have mapping to each other. Thus a single Team can work on several Projects with different processes:

On the image below in the center you see typical Project states. Left flow (column) is a Kanban team that does development. Right flow is UX team. You see that Project State is linked to Team State. Thus you can easily track high level progress when creating a board with Project State. And can track Team progress when creating a board with Team State.

Project State - Team State mapping allows some automatic transition. For example, if we change Project State from Open to UX Phase, then UX Team State will be set to New. Team Status is something lightweight, it can be setup easily and mapped to statuses in various projects (thus a team with a defined flow can work in several projects with different flows).

The one restriction is that User Story has a single Team Status. Thus only a single Team can work on a user story in any given state. For example, when UX Team is completed User Story design, this User Story should be moved to Development (Kanban) Team. 

History is preserved, so it is known what teams worked on what user stories. However, history reports are complicated.

We don't expect to implement this solution in the next 4-6 months. Maybe more feedback will get us more ideas to improve multi-teams support. If you see any problems with the solution above, please share them.

v.2.23.17: Reports, Performance, Boards Magic

This release makes targetprocess3 significantly better.

Reports Improvements

Reports menu was changed, Lead and Cycle Time Distribution diagram added, Burn Down Chart added into menu.

Reports Menu

Reports menu was changed to include most interesting and new reports. Old TP2 reports are in Other Reports section.

Lead and Cycle Time Distribution 

Lead and Cycle Time Distribution diagram is very handy to forecast a probability when a user story or bug will be completed:

You can apply various filters and have distribution for various cases. For example, you want to extract all user stories with 8 pts effort. Now if you have new user story with 8 pts estimate, you can use cumulate distribution line to forecast how many days it will take to complete it with desired probability.

Views Improvements

Convert action added, People tab in Project View added. 

Convert action

Now it is possible to convert various assignable entities. New convert action preserves as much information as possible (custom fields, comments, attachments, similar properties, etc). Only ID is changed.

People Tab in Project View

Somehow this tab was missed in the initial tp3 launch. Now you can see all people that have access to a particular project. You can add new people or remove existing people as well:

Board Improvements

Automatic properties setting with Quick Add, Board Access tab.

Automagical set properties based on selected board filters

Let's consider a situation when you have a board that shows just user stories and bugs from the current release. Then you add new user story right on the board and... it disappears. Fear no more! With new release it will be automatically assigned to the current release. 

The algorithm is quite clever and it understand filters like 

?Iteration is Current

?AssignedUser.Where(it is me) and Iteration.IsCurrent == True

?Release is Current

EntityState is 'Open'

?Project.Name is ‘Green planet’

?Feature is ‘Save the whales’

If you mix similar filters with AND condition, several rules will be applied. 

NOTE: If you use OR condition in the filter, automatic assignment will NOT work (in this case there is ambiguity we can't resolve)

Board Access

There were two levels for board visibility: Public (everyone can see the board) or Private (only you can see the board). We've added Custom visibility level: you can select Teams and Projects which will see the board.

Let's say, you created a board Design Work and gave access to team Designers. Then only people in Designers team will see Design Work board.

Columns Resize

Now you can set and change columns width. Put mouse cursor near the edge of the column and wait till resize control appear. Click on arrows to increase or decrease column width. Note, that only this column will be affected, all other columns will stay as is. Also note that this changes are for you only, other users can tune boards as they wish.

Performance Improvements

We spent significant effort on performance improvements. In general, you should experience less than 3 seconds open time for any board (except boards with many many cards or teams/projects cards). 

The chart below shows Board Open Time day by day. As you see, large boards with many cards loads on average in 4 seconds. Smaller boards usually below 3 seconds. 

We will continue to work on better performance, we believe that subsecond performance is what will make the real difference and make you happy.

What's New in v.2.23.16: Clone Board, Templates, Custom Fields Filters

v.2.23.16 has several major changes in tp3. It will be available for download early next week.

Clone Boards

Sometimes you can't change board settings. Clone board is a good workaround. You will have a new private board with exactly the same settings in a single click

Board Templates

You can quickly create a new board from predefined template. 

If you are not satisfied with the results, just try other templates

Admin can create new templates and delete existing templates. To do that, admin can just create required board configuration and save it as a template:

We believe templates simplify board creation process. With custom templates this can be a company wide repository of useful boards easily searchable and filterable. 

Custom Fields Filters

Now you can filter cards (and swimlanes) on boards by almost any custom fields. Not implemented custom fields filters are: URL, TargetProcess Entity Type.

Release Lane Displays Effort and Quick Burn Down Access

See assigned and completed total effort on every release. Click on small icon to see Release Burn Down Chart. The same icon is displayed for Iteration and Team Iteration lanes as well.

Team Iteration Burn Down Chart 

This report is accessible via TP3 Reports link now and you can select Release, Iteration or Team Iteration.

Process Control Chart: Control Limits

Now you can see lines that shows warning and control limits. Thus you can easily identify stories, bugs, features that had some problems.

Board Access

Board Access management moved into the new tab. Soon it will be extended with per-Team and per-Project access level (we are already working on it).

Some minor changes

• Board colors are changed to improve contrast.
• Quick Add [+] sign moved to the right corner. It partially resolves a problem with cards overlap.
• 6th zoom level expands as much as possible, so it takes all free space now.
• View and Report popups expands to take more space.
• No more than 43 small cards are visible in collapsed cell. This improves data density problem for boards with many rows.
• Performance improved (and we are still working on it).
• Entity View popup: assigned user in active state is highlighted
• Entity View popup: If you put a link into Description field, it will be automatically converted into actual link on save

Design Concept: Customize Cards on Boards

We are finalising cards customization on boards.

On the left you see various zoom levels, so it will be possible to customize cards for all zoom levels. In the center you see card template and a list of all available properties on the right. 

You can quickly search for properties and use drag and drop to customize card. Rearrange properties easily:

Most sizes are fixed, so you can't put more than several properties on small sizes.

However, large sizes are unlimited, so you can put as many properties as you want (but card will be quite large in this case).

Your feedback is welcome!

New Navigation for Boards and Reports

We are working on Custom Graphical Reports concept now and are thinking about navigation changes. The main idea is to allow reports creation very similar to boards creation.

So left menu will break down to 2 sections: Boards and Reports. If you click on a section title, it will open Overview page with all Boards (or Reports) thumbnails. These thumbnails will be actually real snapshots (they can be captured every 30 minutes for example). So Overview will show many boards/reports with almost live content.

In the future we are going to add Dashboards, so there will be 3 sections: Boards, Reports, Dashboards.  

What do you think about this idea?

What's new in v.2.23.15: WIP Limits, Unlimited Assignments, Tags Improvements

Assign as many users as you want to an entity

Now you can assign many developers, many testers, etc. There are no restrictions.

On a board you will see several first asignments:

WIP Limits

WIP Limits are per board. It means each board have its own limits. When you create a board with State lane, you will find Limits tab in Settings area.

When you set limits and there are too many cards in this state, column will be highlighted.

Card Sorting

Now you can sort cards on board:

Clever Past and Future Filter

Limit how many past of future releases or iteration you want to see. For example, if you want to see just 

two future iterations, type a filter

?Iteration is Future(2)

If you want to see 3 past releases:

?Release is Past(3)

Fast Editing of Team and Project Relations

On User Story, Bug, Feature and other views you can quickly set or change Project or Team.

Process Control Chart

This chart shows Cycle or Lead Time distribution. You see when User Stories and Bugs were completed and how long it took to complete them.

Click on entity to open its view.

Tags Autocompletion and Tags Cloud

It was hard to know what tags are there and whats are missing. Now you will see list of matched tags in   add tag field.

Also you can click Tags Cloud and see all popular tags.

Better Rows Titles Formatting for Features and Stories

If you have Features or User Stories in rows, there is more information visible: State, full Name, Project, Effort, Assigned People.

Sparklines on Project View and Team View

When you have many teams working on a project, it is interesting what teams are active and what are not. Project View shows teams activity nicely.

More great things are coming :)

Team/Project Boards

Here is a solution for Team/Project level board access. Access tab is added where Board Owner ca specify visibility. If he selected some Teams, then only people from selected Teams will see the board in left menu.

When you select Private or Public - Teams and Project selection is disabled.

Board Templates

Next week we are starting Boards Templates implementation. When a person clicks Add Board, he will see a list of available templates.

When a person selects a template, board is created. Then templates popup shrinkes and a person can try other templates and see result immediately.

It will be possible to save current board as a template, thus forming templates library.