Search by tag


4 years ago

The Future of Agile Software Development

Software penetrates every pore of human existence. We look up the weather info over the web, giving up on outdoor thermometers. We’re driving to destinations with GPS navigator (forget paper maps with their G7 sections on page 59). We turn on RunKeeper when riding a bike to calculate the average speed and run and boast in Twitter. We’re using software every single day of our lives. It seems we’re hugging our dear gadgets a lot more than our loved ones.

No one knows the exact how-to of writing great software fast, that’s the problem. Waterfall passed away at the crossing of 2 centuries, whereas new software development methodologies (agile) fail at solving the fundamental problems so far. We’re living in very interesting times. Software development industry grows fast right here, right now, and the foundation for a quantitative leap is building up.

——— Read the full article ———
4 years ago

Inner List Design in new Views

We are designing Views in TargetProcess and this is how Inner Lists look like.

We took the first concept from our last post —!topic/uxtargetprocess/zCiquWLM_N0

I would like to highlight a couple of things.

Quick Add of Tasks and Bugs

Now you can quickly add a bug or task to the User Story without leaving a page.

Drag and drop to prioritize or change state

 You can easily change the priority or state of bugs and tasks using drag and drop.

Inline Edit

Change name or effort on the fly!



People assignments

Assign, reassign and find people quickly.

Effort Control

Time spent/remain indicator shows a relative size of tasks and bugs. You can clearly see what task is the largest and how much time is spent and remains.

All actions

You can use action popup to add time or convert a bug/task.

Collapsing Block

You can hide a large block to access relevant content quickly.

ID Indicator

In the inner list we combined entity-type indicator with the entity ID to use space better. 

We’ve already started the implementation and are going to release it in a month.

4 years ago

UX In Action. Why New Views in TargetProcess are sofa king cool

How does a great design differ from a good or mediocre design? Often the difference is just in the smallest details. These details shape user experience and greatly affect the way we feel about a product. The product may look great, but people remain cold using it. They don’t feel it is designed for them.

Views functionality in TargetProcess is not a rocket science. There are thousands of applications with views. View is such a boring page to work with usually .

New Views in TargetProcess are crafted with great attention to details. Every single detail is thought out. Every single decision was debated. Let’s dig into details. I will show and explain all of them.

Inline Edit

Inline edit (edit-in-place) is a huge thing. It allows you to edit everything very quickly. These two words are important: everything and quickly. In our new View you can indeed edit everything and do that really quick. But this is not all. Watch these two very short videos.

Inline edit in JIRA

Now compare it with inline edit in TargetProcess

The difference is clear. When you are editing something in JIRA, the effort value jumps back and forth. It is somewhat confusing and unpleasant. Effort in TargetProcess stands stone still as you edit it.  This produces a totally different feeling. When everything is still you feel that things are under control.  The jumps, on the contrary, are quite distracting,  and you feel that something is not good (but often can’t say what exactly).

People assignments

People assignments component has all the small details that make it just awesome. Avatars enable quick recognition. You may think that avatars are not important, but with time you’re so used to them that you identify a person in a split second. Humans recognize image patterns much faster than words. With first and last names only you have to read. With avatars you just scan.

Quick filter is the fastest way to find someone  if you have a large development team.

Popular actions are available on the top. Quite often you want to assign work to yourself or un-assign work. It is always a good idea to put popular actions to a visible place.

Moreover, potentially dangerous actions are marked red on mouseover, which secures them from accidental clicks.  Also, the red mark builds up quick memory for actions. For Unassign, you will point mouse cursor and click quickly if the button is red without reading.

Links and Actions

There are two types of links: some links represent actions and some links are usual links. There should be a clear distinction between the  two types of links, thus action links have a different underline style (dotted):

If you can perform an action (like edit), you miss an opportunity to jump to entity. This problem was resolved by adding a tiny icon. The icon is an idiomatic pattern to navigate away from the current page.

When a property is empty, it is not clear if  you can edit it or not. You point cursor to an empty row and think something like “Hmm, is it possible to edit something here?” Then you click, and it appears that it is indeed possible to edit this value. But why make people think? The clear message is shown in an empty row when you move mouse over it:

Hidden Stuff

It is a good idea to show only relevant details. For example, you want to change release or iteration. Releases and iterations have end date, you have many releases and iterations that are already done. Most likely you don’t want to assign a user story to an old release. Thus, old releases are hidden by default.

Mouse over pattern is everywhere. So, all actions are hidden by default. You need to move a mouse cursor over a comment to edit or delete it. Thus interface is clean and not burdened with repeated buttons. There is one disadvantage in this approach: available actions are invisible by default for new users, and they might not be actually aware that they can edit something. But we consider this a good trade-off. We don’t design for new users,  we mainly design for people who continuously use our product.


How often you do you need to upload several files, one by one? It is intolerable in a modern web application. People should be able to upload all the files at once:


The general layout is pretty straightforward. You have a content area with title, tags, description, attachments and comments on the left, and more details area with miscellaneous information on the right. This separation is logical.

The layout of the area on the right is beautiful. The most important information is on top. For example, status of a user story and its progress. Then you see all assigned people with estimated effort. Everything is lined-up and there are no unclear labels or weird information. Only relevant information is visible. You can also hide information blocks if you want to.

This is it. New views are in beta and more improvements are coming. Stay tuned and give us your feedback. We live by it.

4 years ago

TargetProcess v.2.21.18: Inline Edit in Views (beta)

New beta User Story and Bug views are available in Kanban and Teams Board on double click. Go to Kanban Board and double click on any User Story or Bug.

Add tag, update name, description, effort or change release, iteration? It’s fast and easy now. From just a single view you can update all the fields.

Avatars are used in comments and assignments. It’s a nice way to recognize people fast and there’s no need to read names.

Assign people quickly. Find a person in a team using quick search and avatars.

You can even edit custom fields!

It’s possible to attach multiple attachments at once now. Moreover, you can just drop a file into a browser window as a popup view is open and the attachment will be added automatically.

As this is a beta version, not all actions are available so far. To convert/move entities, add time or attach user stories or bugs to request, use the old view and edit. In beta version ‘Old View’ and ‘Old Edit’ links are put under ‘Actions’ list.

As we continue working on the views, you’re welcome to have your say and send feedback.


We added a system settings check at the end of installation process, so errors are  identified quickly now.

2011-08-19 11:36:43 InstallHelper: PASSED: User BUILTINIIS_IUSRS has ReadAndExecute permissions on TargetProcess folder
2011-08-19 11:36:43 InstallHelper: PASSED: User NT SERVICETrustedInstaller has FullControl permissions on TargetProcess folder
2011-08-19 11:36:43 InstallHelper: PASSED: User BUILTINAdministrators has FullControl permissions on TargetProcess folder
2011-08-19 11:36:43 InstallHelper: PASSED: Application Pool Pipeline Mode is set to 'Classic'
2011-08-19 11:36:44 InstallHelper: PASSED: .NET framework is set to v2.0.50727
2011-08-19 11:36:44 InstallHelper: PASSED: Application Pool Identity is 'NetworkService'
2011-08-19 11:37:04 InstallHelper: PASSED: .aspx handler is present in IIS configuration
2011-08-19 11:37:04 InstallHelper: PASSED: Default document is enabled
2011-08-19 11:37:04 InstallHelper: PASSED: Default.aspx is in default pages list
2011-08-19 11:37:04 InstallHelper: PASSED: .NET framework 3.5 SP1 installed
2011-08-19 11:37:04 InstallHelper: PASSED: MSMQ is installed correctly
2011-08-19 11:37:04 InstallHelper: PASSED: MSMQ service is running
2011-08-19 11:37:04 InstallHelper: PASSED: User NT AUTHORITYNETWORK SERVICE has FullControl permissions on queue Tp.Error
2011-08-19 11:37:04 InstallHelper: PASSED: User NT AUTHORITYSYSTEM has FullControl permissions on queue Tp.Error
2011-08-19 11:37:04 InstallHelper: PASSED: User NT AUTHORITYNETWORK SERVICE has FullControl permissions on queue Tp.PubSubStorage
2011-08-19 11:37:04 InstallHelper: PASSED: User NT AUTHORITYNETWORK SERVICE has FullControl permissions on queue Tp.InputCommand
2011-08-19 11:37:04 InstallHelper: System settings have been checked successfully.

Fixed Bugs

— Disabled TestTrackPro and SourceSafe plugins for OnDemand accounts
— Task is not assigned to the same release, if parent User Story is dragged to a release in Release Plan view
— ‘Open Assignments’ shows closed assignments as well
— Effort could be updated without edit permission
— An “out of memory” exception when attaching images


— Internal Error 500 if request has incomplete credentials for authorisation
— Add Required comment to Entity State

Request a demo
Our product specialists will show you the beauty
and power of Targetprocess 3 and help you to customize
it for your process and business requirements